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

Fix hang at end of distributed warp with influxdb #340

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

jasoncwik
Copy link
Contributor

When running distributed warp with --influxdb, the app would always hang at the end of each run. After investigation, it appears this is because the channel used to send operations to Influx isn't used on the master process and thus, never gets closed. The app then hangs on the global wait group waiting for the influx goroutine to complete.

As a fix, I closed the ExtraOut channels after the runServerBenchmark completes. Alternatively, you could not start the influx channel on the master node.

When running distributed warp with influxdb, the app would always
hang at the end of each run. This is because the channel used
to send operations to Influx isn't used on the initiator process
and thus, never gets closed. The app then hangs on the global
wait group for the influx goroutine to complete.
Copy link
Collaborator

@klauspost klauspost left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for the contribution!

@klauspost klauspost merged commit d0b3d3a into minio:master Oct 16, 2024
9 checks passed
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.

2 participants