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

Use a prog arg for the hour of the restart to avoid the risk that #4444

Closed

Conversation

chimp1984
Copy link
Contributor

multiple seeds restart around the same time which can cause loss of
data.

The option --seedNodeRestartTime=[0-23] is used to determine the hour
when the node restarts. GMT-0 is used. All nodes need to have a synced
clock (timezone does not matter).

A coordinator need to define which seed uses which hour for the restart.

multiple seeds restart around the same time which can cause loss of
data.

The option --seedNodeRestartTime=[0-23] is used to determine the hour
when the node restarts. GMT-0 is used. All nodes need to have a synced
clock (timezone does not matter).

A coordinator need to define which seed uses which hour for the restart.
@chimp1984
Copy link
Contributor Author

Superseeded by #4445

@chimp1984 chimp1984 closed this Aug 28, 2020
@chimp1984 chimp1984 deleted the restart-seeds-deterministically branch August 29, 2020 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant