We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently all filter/output worker threads appear with name [#{pipeline_id}]-pipeline-manager.
[#{pipeline_id}]-pipeline-manager
(This is longer than the 15chars normally visible in OS.)
This behaviour contradicts the documentation and pipeline workers show up as [base]>workerN, where N is an integer.
and pipeline workers show up as [base]>workerN, where N is an integer.
I believe the fix is simple and you just need to use Util.set_thread_name in start_workers in java_pipeline.rb and pipeline.rb
Util.set_thread_name
start_workers
The text was updated successfully, but these errors were encountered:
make worker thread names visbile to OS, fixes elastic#9968
9936eb0
make worker thread names visbile to OS, fixes #9968
ab56c8c
Fixes #9973
a30d254
234add0
No branches or pull requests
Currently all filter/output worker threads appear with name
[#{pipeline_id}]-pipeline-manager
.(This is longer than the 15chars normally visible in OS.)
This behaviour contradicts the documentation
and pipeline workers show up as [base]>workerN, where N is an integer.
I believe the fix is simple and you just need to use
Util.set_thread_name
instart_workers
in java_pipeline.rb and pipeline.rbThe text was updated successfully, but these errors were encountered: