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

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/01/20 07:15:29 UTC

[GitHub] [shardingsphere-elasticjob] lixiongliang edited a comment on issue #1813: Expansion of tasks, how to solve them, how to optimize system resources and quick start

lixiongliang edited a comment on issue #1813:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1813#issuecomment-763380806


   Our framework package elastic-job-core needs to be upgraded to 2.x. Currently we are 1.1. I feel that the changes are quite big, and there will be classes that cannot be found.
   
   Dividing tasks into different machines is one way to deploy. The current 2.x custom thread pool DefaultExecutorServiceHandler is also configured for a single task, not a thread pool that applies global tasks.
   
   > Consider separate your tasks into different clusters.
   > You may configure the parameter `executor-service-handler` to specify thread count.
   > 
   > Ref: https://shardingsphere.apache.org/elasticjob/legacy/lite-2.x/02-guide/config-manual/
   
   


----------------------------------------------------------------
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