i3wangyi commented on a change in pull request #359: Dynamically change the
processor thread name when consuming event
URL: https://github.com/apache/helix/pull/359#discussion_r309051861
##########
File path:
helix-core/src/main/java/org/apache/helix/controller/GenericHelixController.java
##########
@@ -1165,7 +1163,11 @@ public void run() {
+ _processorName);
while (!isInterrupted()) {
try {
- handleEvent(_eventBlockingQueue.take(), _cache);
+ ClusterEvent newClusterEvent = _eventBlockingQueue.take();
+ String threadName = String.format(
+ "HelixController-pipeline-%s-(%s)", _processorName,
newClusterEvent.getEventId());
Review comment:
`processorName` is actually the cluster name, I don't want to touch the
other places unless necessary. The name convention is aligned with
`super("HelixController-pipeline-" + processorName);` which sets the
ThreadName in the constructor.
----------------------------------------------------------------
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:
[email protected]
With regards,
Apache Git Services
