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/05/10 09:06:41 UTC
[GitHub] [shardingsphere] sandynz opened a new issue, #17518: Start scaling job might fail since tryLock failure after stopping scaling job
sandynz opened a new issue, #17518:
URL: https://github.com/apache/shardingsphere/issues/17518
## Bug Report
### Which version of ShardingSphere did you use?
master branch
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
Proxy, scaling enabled
### Expected behavior
stop scaling and start scaling could be executed repeated, without tryLock failure.
### Actual behavior
Start scaling failed:
```
[INFO ] 2022-05-10 17:02:22.637 [Connection-2-ThreadExecutor] o.a.s.d.p.c.a.i.AbstractPipelineJobAPIImpl - Start disabled pipeline job 0130317c30317c3054317c7363616c696e675f6462
[INFO ] 2022-05-10 17:02:22.647 [Curator-SafeNotifyService-0] o.a.s.d.p.c.e.PipelineJobExecutor - UPDATED job config: /scaling/0130317c30317c3054317c7363616c696e675f6462/config
[INFO ] 2022-05-10 17:02:22.665 [Curator-SafeNotifyService-0] o.a.s.d.p.c.lock.PipelineSimpleLock - tryLock, lockName=scaling_db, timeoutMills=1000, result=false
[INFO ] 2022-05-10 17:02:22.665 [Curator-SafeNotifyService-0] o.a.s.d.p.c.e.PipelineJobExecutor - tryLock failed, databaseName=scaling_db
```
### Reason analyze (If you can)
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
1. Stop scaling {jobId};
2. Start scaling {jobId};
### 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] sandynz closed issue #17518: Start scaling job might fail since tryLock failure after stopping scaling job
Posted by GitBox <gi...@apache.org>.
sandynz closed issue #17518: Start scaling job might fail since tryLock failure after stopping scaling job
URL: https://github.com/apache/shardingsphere/issues/17518
--
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] sandynz commented on issue #17518: Start scaling job might fail since tryLock failure after stopping scaling job
Posted by GitBox <gi...@apache.org>.
sandynz commented on issue #17518:
URL: https://github.com/apache/shardingsphere/issues/17518#issuecomment-1122169784
Hi @soulasuna , could you help to have a look at this issue?
--
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 #17518: Start scaling job might fail since tryLock failure after stopping scaling job
Posted by GitBox <gi...@apache.org>.
soulasuna commented on issue #17518:
URL: https://github.com/apache/shardingsphere/issues/17518#issuecomment-1122171300
@sandynz Assigne to me
--
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