pengdafu opened a new issue, #19422:
URL: https://github.com/apache/shardingsphere/issues/19422
## Bug Report
### Which version of ShardingSphere did you use?
5.1.1
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
Nodes A and B use ETCD as the registry。Show the timeline:
1. A run `create table t1 (id int);`
2. B run `show tables like `'t1'` to get the result
3. A run `drop table t1`, and then run `show tables like `'t1'` the result
shows that t1 does not exist
4. B run `show tables like `'t1'` the result show that t1 exist，but run
`select * from t1` show that t1 doesn't exist。Even weirder is if I create table
t1 show that t1 already exist
5. reboot A and B，all appear normal。
expect B to behave normally when A drop table t1.
### Actual behavior
When A drop table t1, B behaves strangely
### Reason analyze (If you can)
Node B does not watch registry changes. As a result, memory remains after
schema is deleted
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
### 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:
[email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
