[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

Github user DImuthuUpe commented on the issue: https://github.com/apache/helix/pull/179 Awesome ---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

Github user lei-xia commented on the issue: https://github.com/apache/helix/pull/179 merged, thanks! ---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

Github user DImuthuUpe commented on the issue: https://github.com/apache/helix/pull/179 @lei-xia Did the rebasing ---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

Github user lei-xia commented on the issue: https://github.com/apache/helix/pull/179 Could you please rebase to the current HEAD of master branch? Thanks ---

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

Github user DImuthuUpe commented on the issue: https://github.com/apache/helix/pull/179 @lei-xia : Thanks for the feedback. It is possible. If the thread pool size is 40, there should be threads named from TaskStateModelFactory-task_thread-0 to ... 39. In the logs it should print

[GitHub] helix issue #179: Unique thread id for the threads that execute Tasks

Github user lei-xia commented on the issue: https://github.com/apache/helix/pull/179 With this incremented id, you can not tell which thread runs which task either, right? ---