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 reaches working state but data is not synchronized #54

Closed
Synex-wh opened this issue Sep 19, 2019 · 0 comments
Closed

Dataserver reaches working state but data is not synchronized #54

Synex-wh opened this issue Sep 19, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@Synex-wh
Copy link
Contributor

Describe the bug

  • Expanding new data nodes to achieve working state but the data is not fully synchronized, resulting in new node data holdings not meeting expectations

Analytical solution

  • The data synchronization of the new expansion node depends on the notification of other nodes. After receiving the notification, it starts to pull the corresponding version data, and knows that the data is synchronized before the status update of the data node is obtained. The code is as follows:

image

  • The actual situation has received the data pull notification, and there is no older version of the situation, but the data is really missing, only the pull data request is not initiated, the specific code modification point is as follows

image

@Synex-wh Synex-wh added the bug Something isn't working label Sep 26, 2019
@dzdx dzdx closed this as completed Mar 16, 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