Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataServer does not work after startup, receives client off request processing error #23

Closed
Synex-wh opened this issue May 20, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@Synex-wh
Copy link
Contributor

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.

image
2.
image

  • SOFARegistry version:
  • JVM version (e.g. java -version):
  • OS version (e.g. uname -a):
  • Maven version:
  • IDE version:
@Synex-wh Synex-wh added the bug Something isn't working label May 29, 2019
@dzdx dzdx closed this as completed Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants