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 2020/07/05 03:51:20 UTC

[GitHub] [shardingsphere-elasticjob-lite] terrymanu opened a new issue #946: Disable job in startup is not in effect sometimes

terrymanu opened a new issue #946:
URL: https://github.com/apache/shardingsphere-elasticjob-lite/issues/946


   The reason is curator save disable status async, and sometimes not persist to ZooKeeper in time before return. 
   It will cause Elastic Job judge the server as enabled server.
   
   We should load server status after make sure the server status persist in to ZooKeeper.
   
   - [ ] Add ENABLE status
   - [ ] Judge if the server status is empty sleep and reload again


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

[GitHub] [shardingsphere-elasticjob-lite] terrymanu closed issue #946: Disable job in startup is not in effect sometimes

Posted by GitBox <gi...@apache.org>.

terrymanu closed issue #946:
URL: https://github.com/apache/shardingsphere-elasticjob-lite/issues/946


   


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