You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@helix.apache.org by GitBox <gi...@apache.org> on 2019/07/23 23:32:02 UTC

[GitHub] [helix] i3wangyi opened a new pull request #359: Dynamically change the processor thread name when consuming event

i3wangyi opened a new pull request #359: Dynamically change the processor thread name when consuming event
URL: https://github.com/apache/helix/pull/359
 
 
   **Why is it necessary?**
   
   It helps the manual process of grepping the server logs of a continuous cluster event processing throughout the entire pipeline.
   
   The event id is at the postfix after the "_" character.
   
   Example:
   `Enqueue : 5f1e26a8_DEFAULT
   Enqueue : 5f1e26a8_TASK
   Enqueue : 3ddd0a91_DEFAULT
   Enqueue : 3ddd0a91_TASK
   Current thread name: HelixController-pipeline-default-TestCluster_5f1e26a8_DEFAULT
   Current thread name: HelixController-pipeline-task-TestCluster_5f1e26a8_TASK
   Current thread name: HelixController-pipeline-default-TestCluster_3ddd0a91_DEFAULT
   Current thread name: HelixController-pipeline-task-TestCluster_3ddd0a91_TASK`

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services