Add configureBenchmarkLogging calls across the various benchmarks#143185
Merged
joegallo merged 8 commits intoelastic:mainfrom Feb 27, 2026
Merged
Add configureBenchmarkLogging calls across the various benchmarks#143185joegallo merged 8 commits intoelastic:mainfrom
joegallo merged 8 commits intoelastic:mainfrom
Conversation
which prevents nasty stacktrace from being logged
Collaborator
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Contributor
Author
|
I updated this to account for the changes from #143056. |
ldematte
approved these changes
Feb 27, 2026
Contributor
ldematte
left a comment
There was a problem hiding this comment.
LGTM if CI passes.
We can handle NodeNamePatternConverter.setGlobalNodeName vs LogConfigurator.setNodeName separately if we need to.
Contributor
Author
I fussed with it slightly in 3e981b9, and it seems to work fine. But indeed, yeah, we can revisit this next week if it turns out to be sub-optimal for whatever reason. |
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Feb 27, 2026
…cations * upstream/main: Warn on API key version mismatch (elastic#143127) Fixed wrong malformed value ordering in synthetic source tests (elastic#143187) [ML] Fix: required_native_memory_bytes Calculated with Wrong Allocation Count (elastic#143077) Add configureBenchmarkLogging calls across the various benchmarks (elastic#143185) Mute org.elasticsearch.xpack.esql.CsvIT test {csv-spec:k8s-timeseries-avg-over-time.Avg_over_time_aggregate_metric_double_implicit_casting} elastic#143292 Give system role permission to invoke shard refresh (elastic#143190) Mute testSyntheticSourceWithTranslogSnapshot (elastic#143260) Adds ResumeInfo Tests (elastic#142769) Use a static method to configure benchmark logging (elastic#143056) add connectors release notes (elastic#142884) Add CI triage guidance for AI agents (elastic#142994) ESQL: Data sources: ZSTD, BZIP2 (elastic#143228) [ES|QL] Channels issue when an agg is called with the same field (elastic#142180) (elastic#142269) Add support for project routing in reindex requests (elastic#142240)
tballison
pushed a commit
to tballison/elasticsearch
that referenced
this pull request
Mar 3, 2026
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.
I've been doing some work in the benchmarks, and while I was here I ran this command from the README:
And that spit out a big stacktrace, like this:
So I thought I'd investigate why that was and fix it.
And it turns out this seems pretty related to #143041, so I'm pinging @thecoop for a review. (For the same reason, I'm going with
:Search Relevance/Vectorseven though this isn't really related to that subject.)