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

GitHub user DImuthuUpe opened a pull request: https://github.com/apache/helix/pull/179 Unique thread id for the threads that execute Tasks Currently when we run a workflow, participant prints 'TaskStateModelFactory-task_thread' as the thread id that runs a particular

[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 DImuthuUpe commented on the issue: https://github.com/apache/helix/pull/179 @zhan849 In the code, we are setting the core pool size as 40. Java doc says "corePoolSize - the number of threads to keep in the pool, even if they are idle, unless allowCoreThreadTimeOut i

[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 DImuthuUpe commented on the issue: https://github.com/apache/helix/pull/179 Awesome ---