[Backport 7.x] Add optional content checking to ResourceWatcher #79532
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some cloud environments, there may be frequent synchronization of configuration files from the orchestration layer to the ES container. This can trigger frequent, unnecessary reloading of files. Previously, code that used the ResourceWatcherService / FileWatcher would need to detect "no-op" file changes itself. With the addition of this content checking support, it can be handled efficiently by the Resource Watcher Service. Backport of: elastic#79423
tvernum
added
backport
auto-merge-without-approval
JDK only returns lastModified FileType at seconds granularity
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Oct 20, 2021
tvernum
added a commit
that referenced
this pull request
Oct 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cloud environments, there may be frequent synchronization of
configuration files from the orchestration layer to the ES container.
This can trigger frequent, unnecessary reloading of files.
Previously, code that used the ResourceWatcherService / FileWatcher
would need to detect "no-op" file changes itself. With the addition of
this content checking support, it can be handled efficiently by the
Resource Watcher Service.
Backport of: #79423