Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[license check] await green elasticsearch plugin #33584

Closed
wants to merge 6 commits into from

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Mar 20, 2019

The license check currently polls every 30 seconds regardless of elasticsearch status. This awaits a green elasticsearch plugin before sending a new request.

@jbudz jbudz added review Team:Operations Team label for Operations Team labels Mar 20, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

Copy link
Member

@mistic mistic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@jbudz jbudz added the non-issue Indicates to automation that a pull request should not appear in the release notes label Mar 27, 2019
@tylersmalley
Copy link
Contributor

Not sure if the failures were due to this PR, but could use a merge with upstream

@@ -32,12 +32,6 @@ export function setupXPackMain(server) {
}
};

// trigger an xpack info refresh whenever the elasticsearch plugin status changes
server.plugins.elasticsearch.status.on('change', async () => {
await info.refreshNow();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure one of the reasons this being done is in case you change you license and then restart your cluster, not that it's a good way to cover that scenario. License info comes back in some sort of signature with each request now, right? Is that why we don't need this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can add it back in if we want, I removed it because it overlaps with https://github.com/elastic/kibana/pull/33584/files#diff-577f99d7103576efa3d57d5e26ec3fb5R138 now. It may fire a little quicker if we leave it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not picky either way, just want to make sure that this wasn't the only mechanism we had to refresh our cache when the license is updated in es.

@elasticmachine

This comment has been minimized.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@jbudz jbudz added release_note:fix and removed non-issue Indicates to automation that a pull request should not appear in the release notes labels Jul 2, 2019
@jbudz jbudz closed this Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants