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/12/16 09:14:00 UTC

[GitHub] [shardingsphere-elasticjob] Lucas-307 opened a new issue #1781: Trigger ScheduleJob duplicate execute.

Lucas-307 opened a new issue #1781:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1781


   ## Bug Report
   
   ### Which version of ElasticJob did you use?
   3.0.0-beta
   
   ### Which project did you use? ElasticJob-Lite or ElasticJob-Cloud?
   ElasticJob-Lite
   
   ### Process
   Process1: Create a ScheduleJobBootstrap with corn=0 0 0 1 1 ? 2099, shardingTotalCount=2; and JobOperateAPI.trigger it.
   when this two sharding items executing.
   Process2: Create the same job and trigger it again. 
   
   ### Expected behavior
   Process2 do nothing.
   
   ### Actual behavior
   Process2 also execute one of sharding items.
   
   ### Example codes for reproduce this issue (such as a github link).
   
   ```java
   jobConfig = JobConfiguration.newBuilder(jobId, 2).cron("0 0 0 1 1 ? 2099").jobParameter("xxx").build();
   jobBootstrap = new ScheduleJobBootstrap(registryCenter, new ScalingElasticJob(), jobConfig);
   jobBootstrap.schedule();
   jobOperateAPI.trigger(jobId);
   ```
   


----------------------------------------------------------------
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] TeslaCN commented on issue #1781: Trigger ScheduleJob duplicate execute.

Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1781:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1781#issuecomment-747125904


   I've tested 2 cases and cannot reproduce your problem: 
   1. Start Process2 while Process1 executing 2 shards. The Process2 got stuck because of waiting other shards comlete.
   2. Start Process2 after Process1 finished. Reshard happened and each process got a shard. Then Process1 executed shard 1 and Process2 executed shard 2.


----------------------------------------------------------------
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] Lucas-307 closed issue #1781: Trigger ScheduleJob duplicate execute.

Posted by GitBox <gi...@apache.org>.
Lucas-307 closed issue #1781:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1781


   


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