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 2022/08/09 13:23:33 UTC

[GitHub] [shardingsphere] azexcy opened a new issue, #20035: Use OneOffJobBootstrap some sharding task may not triggered sometimes

azexcy opened a new issue, #20035:
URL: https://github.com/apache/shardingsphere/issues/20035

   ## Bug Report
   
   Use 1 ShardingSphere-Proxy  and the sharding item is 2.
   
   Relation ci url
   ```
   https://github.com/apache/shardingsphere/runs/7745031071?check_suite_focus=true
   https://github.com/apache/shardingsphere/runs/7745031071?check_suite_focus=true
   https://github.com/apache/shardingsphere/runs/7737878020?check_suite_focus=true
   ```
   
   Relation code at PipelineJobExecutor
   
   ```
       private void execute(final JobConfigurationPOJO jobConfigPOJO) {
           RuleAlteredJob job = new RuleAlteredJob();
           PipelineJobCenter.addJob(jobConfigPOJO.getJobName(), job);
           OneOffJobBootstrap oneOffJobBootstrap = new OneOffJobBootstrap(PipelineAPIFactory.getRegistryCenter(), job, jobConfigPOJO.toJobConfiguration());
           oneOffJobBootstrap.execute();
           job.setOneOffJobBootstrap(oneOffJobBootstrap);
       }
   ```
   
   and I captured data from zookeeper when the problem occurred
   > https://github.com/azexcy/shardingsphere/runs/7745731331?check_suite_focus=true
   
   ```
   /scaling/0130317c30317c3054317c7368617264696e675f6462=org.apache.shardingsphere.data.pipeline.scenario.rulealtered.RuleAlteredJob, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/trigger=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/sharding=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/sharding/1=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/sharding/1/instance=172.19.0.4@-@11, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/sharding/0=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/sharding/0/instance=172.19.0.4@-@11, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/servers=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/servers/172.19.0.4=ENABLED, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/offset=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/offset/1=incremental:
   ...
   /scaling/0130317c30317c3054317c7368617264696e675f6462/leader=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/leader/sharding=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/leader/election=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/leader/election/latch=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/leader/election/instance=172.19.0.4@-@11, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/instances=, 
   /scaling/0130317c30317c3054317c7368617264696e675f6462/instances/172.19.0.4@-@11=jobInstanceId: 172.19.0.4@-@11
   
   ```
   
   seems only one item had data, it appears that only one item has data
   
   ### Which version of ShardingSphere did you use?
   
   master  97a54388f80c2aa408496b4f520e9df0beb02cb4
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   ShardingSphere-Proxy
   
   ### Expected behavior
   
   all sharding item will be triggered.
   
   ### Actual behavior
   
   sometimes, only one of them will triggered.
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   
   the problem not occur every time, it is difficult to reproduce it locally
   
   ### 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.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] soulasuna closed issue #20035: LockContext.tryLock may occur exception and convert to warn log

Posted by GitBox <gi...@apache.org>.
soulasuna closed issue #20035: LockContext.tryLock may occur exception and convert to warn log
URL: https://github.com/apache/shardingsphere/issues/20035


-- 
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] soulasuna commented on issue #20035: LockContext.tryLock may occur exception and convert to warn log

Posted by GitBox <gi...@apache.org>.
soulasuna commented on issue #20035:
URL: https://github.com/apache/shardingsphere/issues/20035#issuecomment-1238925321

   Fixed


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