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/03/24 09:18:23 UTC
[GitHub] [shardingsphere-elasticjob] YANGJINJUE opened a new issue #1857: 对集群进行故障演练，有时会导致job自杀
YANGJINJUE opened a new issue #1857:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1857
### use 3.0.0-alpha
### project: ElasticJob-Lite
### Expected behavior
the job will recovery when the zookeeper cluster recovery
### Actual behavior
there is a job shutdown by self when the zookeeper cluster recovery
### Reason analyze (If you can)
I guess the class ShutdownListenerManager have a bug at line 57
`protected void dataChanged(final String path, final Type eventType, final String data) {
if (!JobRegistry.getInstance().isShutdown(jobName) && !JobRegistry.getInstance().getJobScheduleController(jobName).isPaused()
&& isRemoveInstance(path, eventType) && !isReconnectedRegistryCenter()) {
schedulerFacade.shutdownInstance();
}
}`
### Steps to reproduce the behavior.
multiple kill the zookeeper cluster and recovery
### Example codes for reproduce this issue (such as a github link).
--
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] 15168326318 commented on issue #1857: zookeeper cluster killed and recovery，the job shutdown by self
Posted by GitBox <gi...@apache.org>.
15168326318 commented on issue #1857:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1857#issuecomment-1081419574
> the code schedulerFacade.shutdownInstance() may execute when zookeeper cluster session expire
@YANGJINJUE @zewade @TeslaCN Has this problem been solved?We also have the same problem.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1857: zookeeper cluster killed and recovery，the job shutdown by self
Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1857:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1857#issuecomment-806384424
What's your ZookeeperConfiguration?
We set the retry policy `org.apache.curator.retry.ExponentialBackoffRetry` when initializing the Curator client. If retry times exceeded, the instance will not recover.
--
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] zewade commented on issue #1857: zookeeper cluster killed and recovery，the job shutdown by self
Posted by GitBox <gi...@apache.org>.
zewade commented on issue #1857:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1857#issuecomment-839442884
We also have the same problem，when zookeeper connect is not stable，some of the elastic job might be shutdown by self.
--
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] zewade edited a comment on issue #1857: zookeeper cluster killed and recovery，the job shutdown by self
Posted by GitBox <gi...@apache.org>.
zewade edited a comment on issue #1857:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1857#issuecomment-839442884
We also have the same problem，when zookeeper connect is not stable，some of the elastic jobs might be shutdown by self.
2021-05-12 11:07:12,276 INFO [userdemo-infra] [main] [org.quartz.core.QuartzScheduler:666] - trace[] Scheduler quartzScheduler_$_NON_CLUSTERED shutting down.
2021-05-12 11:07:12,276 INFO [userdemo-infra] [main] [org.quartz.core.QuartzScheduler:585] - trace[] Scheduler quartzScheduler_$_NON_CLUSTERED paused.
2021-05-12 11:07:12,280 INFO [userdemo-infra] [main] [org.quartz.core.QuartzScheduler:740] - trace[] Scheduler quartzScheduler_$_NON_CLUSTERED shutdown complete.
--
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] YANGJINJUE commented on issue #1857: zookeeper cluster killed and recovery，the job shutdown by self
Posted by GitBox <gi...@apache.org>.
YANGJINJUE commented on issue #1857:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1857#issuecomment-806399116
> What's your ZookeeperConfiguration?
> We set the retry policy `org.apache.curator.retry.ExponentialBackoffRetry` when initializing the Curator client. If retry times exceeded, the instance will not recover
the code schedulerFacade.shutdownInstance() may execute when zookeeper cluster session expire
--
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