klsince opened a new issue, #2315: URL: https://github.com/apache/helix/issues/2315
**Is your feature request related to a problem? Please describe.** The size of thread pool to handle state transitions is [hard coded 40](https://github.com/apache/helix/blob/master/helix-core/src/main/java/org/apache/helix/messaging/DefaultMessagingService.java#L269). To be specific, there seems no way to customize the thread pool when calling registerMessageHandlerFactory() to register the message handler. This became a bottleneck when service did intensive I/O during states transitions, particularly during service startup time. **Describe the solution you'd like** Please lemme know if there is already ways to customize that pool size. Otherwise, it may help to add a new [registerMessageHandlerFactory()](https://github.com/apache/helix/blob/master/helix-core/src/main/java/org/apache/helix/ClusterMessagingService.java#L124) that accepts threadPoolSize to customize thread pool size. **Additional context** We noticed the threads handling state transitions were capped at 40, and found that this seems hard coded and no way to customize it currently. ``` [HelixTaskExecutor-message_handle_thread_35] ``` -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
