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

Only aggregate heaviest fork at the coordinator. #3115

Conversation

wen-coding
Copy link

  • Only aggregate heaviest fork from the coordinator
  • Remove the "80% sees 80%" exit condition
  • Only exit if stopped

@wen-coding wen-coding self-assigned this Oct 9, 2024
@@ -1005,6 +867,15 @@ pub fn wait_for_wen_restart(config: WenRestartConfig) -> Result<()> {
--no-snapshot-fetch",
slot, hash, shred_version,
);
if config.cluster_info.id() == config.wen_restart_coordinator {
aggregate_restart_heaviest_fork(
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need to aggregate on completion here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was your suggestion: make the coordinator aggregate heaviest fork at the end, so we know the status of the cluster from watching the coordinator

carllin
carllin previously approved these changes Oct 16, 2024
@wen-coding wen-coding merged commit 2bde0fc into anza-xyz:master Oct 17, 2024
40 checks passed
@wen-coding wen-coding deleted the wen_restart_modify_heaviest_fork_aggregate branch October 17, 2024 23:32
ray-kast pushed a commit to abklabs/agave that referenced this pull request Nov 27, 2024
* Only aggregate heaviest fork for the coordinator, do not exit until asked.

* Fix a bad merge.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants