[GitHub] [shardingsphere] natehuangting opened a new issue, #18943: After switchover, databaseDiscovery cannot discover new master

[GitBox]

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

   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   master
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Actual behavior
   Two nodes ds_0, ds_1, originally ds_0 is the host, after the switch ds_1 is 
the host. But the Proxy cannot find that ds_1 is the master.
   
   ### Reason analyze (If you can)
   When switching, the replication status of ds_1 is cleared, the show slave 
status is empty, and the proxy adds ds_1 to disableDatasourceNames. Since the 
disabled node does not participate in the logic of judging whether it is the 
master, and the show slave status is always empty, the state cannot be changed 
to enable.
   
   <img width="1268" alt="企业微信截图_aa59b243-52b8-4979-bdce-47e6f3f304a3" 
src="https://user-images.githubusercontent.com/26433395/177788903-266d58f6-cff2-4b17-983d-013f56d310a4.png";>
   <img width="1141" alt="企业微信截图_349ac266-ff9e-49cd-bed9-db8a21483e3d" 
src="https://user-images.githubusercontent.com/26433395/177789179-10fe0d52-d3ee-4ba8-968c-b67701ba1d82.png";>
   


-- 
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-unsubscr...@shardingsphere.apache.org.apache.org

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