Fix stats in slow logs to be a escaped JSON #44642
Merged
Conversation
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
At the moment fields in JSON logs are escaped by default. therefore inside that field should be en escaped string.
|
Pinging @elastic/es-core-infra |
pgomulka
changed the title
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this pull request
Jul 22, 2019
Fields in JSON logs should be an escaped JSON fields. It is a broken json value at the moment "stats": "["group1", "group2"]", -> "stats": "[\"group1\", \"group2\"]", This should later be refactored into a JSON array of strings (the same as types in 7.x)
pgomulka
added a commit
that referenced
this pull request
Jul 22, 2019
Fields in JSON logs should be an escaped JSON fields. It is a broken json value at the moment "stats": "["group1", "group2"]", -> "stats": "[\"group1\", \"group2\"]", This should later be refactored into a JSON array of strings (the same as types in 7.x)
jimczi
added a commit
to jimczi/elasticsearch
that referenced
this pull request
Oct 22, 2019
This commit fixes the usage of JsonStringEncoder#quoteAsUTF8 in the SearchSlowLog. JsonStringEncoder#getInstance should always be called to get a thread local object but this assumption was broken by elastic#44642. This means that any slow log can throw an AIOOBE since it uses the same byte array concurrently. Closes elastic#48358
jimczi
added a commit
that referenced
this pull request
Oct 23, 2019
This commit fixes the usage of JsonStringEncoder#quoteAsUTF8 in the SearchSlowLog. JsonStringEncoder#getInstance should always be called to get a thread local object but this assumption was broken by #44642. This means that any slow log can throw an AIOOBE since it uses the same byte array concurrently. Closes #48358
jimczi
added a commit
that referenced
this pull request
Oct 23, 2019
This commit fixes the usage of JsonStringEncoder#quoteAsUTF8 in the SearchSlowLog. JsonStringEncoder#getInstance should always be called to get a thread local object but this assumption was broken by #44642. This means that any slow log can throw an AIOOBE since it uses the same byte array concurrently. Closes #48358
jimczi
added a commit
that referenced
this pull request
Oct 23, 2019
This commit fixes the usage of JsonStringEncoder#quoteAsUTF8 in the SearchSlowLog. JsonStringEncoder#getInstance should always be called to get a thread local object but this assumption was broken by #44642. This means that any slow log can throw an AIOOBE since it uses the same byte array concurrently. Closes #48358
jimczi
added a commit
that referenced
this pull request
Oct 28, 2019
This commit fixes the usage of JsonStringEncoder#quoteAsUTF8 in the SearchSlowLog. JsonStringEncoder#getInstance should always be called to get a thread local object but this assumption was broken by #44642. This means that any slow log can throw an AIOOBE since it uses the same byte array concurrently. Closes #48358
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.
Fields in JSON logs should be an escaped JSON fields. It is a broken json value at the moment
"stats": "["group1", "group2"]",->"stats": "[\"group1\", \"group2\"]",This should later be refactored into a JSON array of strings (the same as types in 7.x)