You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test verifies the data synchronization process between dataServers. When the link is normal, the data backup notification information in the cluster is reported. The ip error of the link cannot be found.
connect log eg:
The above logs are the link log and the broken link log printed at the time of the link event of the bolt. Note: The link triggered by the link 43:44066 is triggered before the link 43:55174 chain break event, and the last link status 43:44066 is on the successful link
However, the current dataserver stores the client dataserver link stored by the server as the Map, so if the storage relationship of the key is determined only by ip in the above process, the previously broken link event is triggered after the new connection is established (the above is). In this way, the event of the broken link is deleted by the same deletion logic of ip, and the link is actually connected but the storage relationship cannot be found. code show as below
Data synchronization logic and error exceptions are as follows
SOFARegistry version:
JVM version (e.g. java -version):
OS version (e.g. uname -a):
Maven version:
IDE version:
The text was updated successfully, but these errors were encountered:
Describe the bug
The test verifies the data synchronization process between dataServers. When the link is normal, the data backup notification information in the cluster is reported. The ip error of the link cannot be found.
connect log eg:
![image](https://user-images.githubusercontent.com/8018119/58011620-3550b980-7b25-11e9-9318-35e04e67571a.png)
![image](https://user-images.githubusercontent.com/8018119/58011684-6204d100-7b25-11e9-8ff8-e84fb24eeac2.png)
![image](https://user-images.githubusercontent.com/8018119/58011734-7e087280-7b25-11e9-84f9-035585a6035f.png)
The above logs are the link log and the broken link log printed at the time of the link event of the bolt. Note: The link triggered by the link 43:44066 is triggered before the link 43:55174 chain break event, and the last link status 43:44066 is on the successful link
However, the current dataserver stores the client dataserver link stored by the server as the Map, so if the storage relationship of the key is determined only by ip in the above process, the previously broken link event is triggered after the new connection is established (the above is). In this way, the event of the broken link is deleted by the same deletion logic of ip, and the link is actually connected but the storage relationship cannot be found. code show as below
![image](https://user-images.githubusercontent.com/8018119/58011938-e9524480-7b25-11e9-9bbc-e8636ca2e318.png)
Data synchronization logic and error exceptions are as follows
![image](https://user-images.githubusercontent.com/8018119/58011982-ff600500-7b25-11e9-8f1f-86224de33353.png)
SOFARegistry version:
JVM version (e.g.
java -version
):OS version (e.g.
uname -a
):Maven version:
IDE version:
The text was updated successfully, but these errors were encountered: