You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "peilinqian (via GitHub)" <gi...@apache.org> on 2023/11/06 10:42:15 UTC
[I] Executing 'drop streaming jobId' returned success, but the actual physical datasource replication slot was not deleted. [shardingsphere]
peilinqian opened a new issue, #28960:
URL: https://github.com/apache/shardingsphere/issues/28960
## Bug Report
**For English only**, other languages will not accept.
Before report a bug, make sure you have:
- Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues).
- Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview).
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will **close it**.
Please answer these questions before submitting your issue. Thanks!
### Which version of ShardingSphere did you use?
```
/usr/bin/java
we find java version: java8, full_version=1.8.0_242, full_path=/usr/bin/java
ShardingSphere-5.4.1-SNAPSHOT
Commit ID: dirty-e406a153c595a315fcf9cd0950a7eb1e206eaa7c
Commit Message: Support load unique key for H2 #28035 (#28154)
Branch: hw-cdc
Build time: 2022-12-12T03:18:10+0800
```
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
Executing 'drop streaming jobId' returned success, and the actual physical datasource replication slot was deleted.
### Actual behavior
Executing 'drop streaming jobId' returned success, but the actual physical datasource replication slot was not deleted.
### Reason analyze (If you can)
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
drop streaming 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
Re: [I] Executing 'drop streaming jobId' returned success, but the actual physical datasource replication slot was not deleted. [shardingsphere]
Posted by "azexcy (via GitHub)" <gi...@apache.org>.
azexcy commented on issue #28960:
URL: https://github.com/apache/shardingsphere/issues/28960#issuecomment-1798198344
It's already fixed at #28890. Thank you for your feedback.
--
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
Re: [I] Executing 'drop streaming jobId' returned success, but the actual physical datasource replication slot was not deleted. [shardingsphere]
Posted by "azexcy (via GitHub)" <gi...@apache.org>.
azexcy closed issue #28960: Executing 'drop streaming jobId' returned success, but the actual physical datasource replication slot was not deleted.
URL: https://github.com/apache/shardingsphere/issues/28960
--
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