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 dataserver receives the client off request when there is no working time, and the data synchronization and data deletion simultaneously cause the final data to be inconsistent.
Therefore, we must postpone the client off request processing of the current node, and process the client off request after the no working state has to synchronize the other node data. That is, we must prohibit the deletion of data in the no working state.
At the same time, other nodes also receive the same client off request. These requests are executed on other dataservers for data deletion, and the deleted logs are synchronized to the dataserver node without working, which also causes confusion. Therefore, we must postpone the execution of these synchronization logs to the post-working execution, and postpone the execution because the executed logs are idempotent operations, so the number can be completed normally.
2.
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 dataserver receives the client off request when there is no working time, and the data synchronization and data deletion simultaneously cause the final data to be inconsistent.
Therefore, we must postpone the client off request processing of the current node, and process the client off request after the no working state has to synchronize the other node data. That is, we must prohibit the deletion of data in the no working state.
At the same time, other nodes also receive the same client off request. These requests are executed on other dataservers for data deletion, and the deleted logs are synchronized to the dataserver node without working, which also causes confusion. Therefore, we must postpone the execution of these synchronization logs to the post-working execution, and postpone the execution because the executed logs are idempotent operations, so the number can be completed normally.
2.
java -version
):uname -a
):The text was updated successfully, but these errors were encountered: