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

Fix deployment watcher index usage #4709

Merged
merged 3 commits into from Sep 24, 2018
Merged

Fix deployment watcher index usage #4709

merged 3 commits into from Sep 24, 2018

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Sep 21, 2018

Fixes three issues:

  1. Retrieving the latest evaluation index was not properly selecting the
    greatest index. This would undermine checks we had to reduce the number
    of evaluations created when the latest eval index was greater than any
    alloc change
  2. Fix an issue where the blocking query code was using the incorrect
    index such that the index was higher than necassary.
  3. Special case handling of blocked evaluation since the create/snapshot
    index is no particularly useful since they can be reblocked.

Fixes three issues:
1. Retrieving the latest evaluation index was not properly selecting the
greatest index. This would undermine checks we had to reduce the number
of evaluations created when the latest eval index was greater than any
alloc change
2. Fix an issue where the blocking query code was using the incorrect
index such that the index was higher than necassary.
3. Special case handling of blocked evaluation since the create/snapshot
index is no particularly useful since they can be reblocked.
@dadgar dadgar changed the base branch from master to b-jet-fixes September 21, 2018 21:11
@dadgar dadgar changed the title Fix deployment watcher index usage WIP: Fix deployment watcher index usage Sep 21, 2018
@dadgar dadgar changed the title WIP: Fix deployment watcher index usage Fix deployment watcher index usage Sep 24, 2018
@dadgar dadgar merged commit b8ec297 into b-jet-fixes Sep 24, 2018
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants