[ML] Fixing inference stats race condition#55163
Merged
benwtrent merged 21 commits intoelastic:masterfrom Apr 20, 2020
Merged
Conversation
Collaborator
|
Pinging @elastic/ml-core (:ml) |
...ore/src/main/java/org/elasticsearch/xpack/core/ml/inference/trainedmodel/InferenceStats.java
Outdated
Show resolved
Hide resolved
...ore/src/main/java/org/elasticsearch/xpack/core/ml/inference/trainedmodel/InferenceStats.java
Outdated
Show resolved
Hide resolved
Member
Author
|
run elasticsearch-ci/2 |
3 similar comments
Member
Author
|
run elasticsearch-ci/2 |
Member
Author
|
run elasticsearch-ci/2 |
Member
Author
|
run elasticsearch-ci/2 |
davidkyle
reviewed
Apr 17, 2020
...ore/src/main/java/org/elasticsearch/xpack/core/ml/inference/trainedmodel/InferenceStats.java
Show resolved
Hide resolved
...multi-node-tests/src/test/java/org/elasticsearch/xpack/ml/integration/InferenceIngestIT.java
Show resolved
Hide resolved
...n/ml/src/main/java/org/elasticsearch/xpack/ml/dataframe/process/AnalyticsProcessManager.java
Outdated
Show resolved
Hide resolved
...k/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/inference/TrainedModelStatsService.java
Outdated
Show resolved
Hide resolved
...k/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/inference/TrainedModelStatsService.java
Outdated
Show resolved
Hide resolved
...in/ml/src/test/java/org/elasticsearch/xpack/ml/inference/loadingservice/LocalModelTests.java
Outdated
Show resolved
Hide resolved
...multi-node-tests/src/test/java/org/elasticsearch/xpack/ml/integration/InferenceIngestIT.java
Outdated
Show resolved
Hide resolved
...k/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/inference/TrainedModelStatsService.java
Outdated
Show resolved
Hide resolved
Member
Author
|
run elasticsearch-ci/2 |
| statsResponse = client().performRequest(new Request("GET", "_ml/inference/" + regressionModelId + "/_stats")); | ||
| assertThat(EntityUtils.toString(statsResponse.getEntity()), containsString("\"inference_count\":10")); | ||
| } catch (ResponseException ex) { | ||
| //this could just mean shard failures. |
There was a problem hiding this comment.
Shouldn't this "catch" clause call "Assert.fail()"?
If it doesn't I think the whole block won't be retried when the ResponseException happens...
Member
Author
|
@elasticmachine update branch |
Member
Author
|
@elasticmachine update branch |
Member
Author
|
run elasticsearch-ci/1 |
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this pull request
Apr 20, 2020
`updateAndGet` could actually call the internal method more than once on contention. If I read the JavaDocs, it says: ```* @param updateFunction a side-effect-free function``` So, it could be getting multiple updates on contention, thus having a race condition where stats are double counted. To fix, I am going to use a `ReadWriteLock`. The `LongAdder` objects allows fast thread safe writes in high contention environments. These can be protected by the `ReadWriteLock::readLock`. When stats are persisted, I need to call reset on all these adders. This is NOT thread safe if additions are taking place concurrently. So, I am going to protect with `ReadWriteLock::writeLock`. This should prevent race conditions while allowing high (ish) throughput in the highly contention paths in inference. I did some simple throughput tests and this change is not significantly slower and is simpler to grok (IMO). closes elastic#54786
benwtrent
added a commit
that referenced
this pull request
Apr 20, 2020
`updateAndGet` could actually call the internal method more than once on contention. If I read the JavaDocs, it says: ```* @param updateFunction a side-effect-free function``` So, it could be getting multiple updates on contention, thus having a race condition where stats are double counted. To fix, I am going to use a `ReadWriteLock`. The `LongAdder` objects allows fast thread safe writes in high contention environments. These can be protected by the `ReadWriteLock::readLock`. When stats are persisted, I need to call reset on all these adders. This is NOT thread safe if additions are taking place concurrently. So, I am going to protect with `ReadWriteLock::writeLock`. This should prevent race conditions while allowing high (ish) throughput in the highly contention paths in inference. I did some simple throughput tests and this change is not significantly slower and is simpler to grok (IMO). closes #54786
This file contains hidden or 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
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.
updateAndGetcould actually call the internal method more than once on contention.If I read the JavaDocs, it says:
* @param updateFunction a side-effect-free functionSo, it could be getting multiple updates on contention, thus having a race condition where stats are double counted.
To fix, I am going to use a
ReadWriteLock. TheLongAdderobjects allows fast thread safe writes in high contention environments. These can be protected by theReadWriteLock::readLock.When stats are persisted, I need to call reset on all these adders. This is NOT thread safe if additions are taking place concurrently. So, I am going to protect with
ReadWriteLock::writeLock.This should prevent race conditions while allowing high (ish) throughput in the highly contention paths in inference.
I did some simple throughput tests and this change is not significantly slower and is simpler to grok (IMO).
closes #54786