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

mirror: Stop minio-go bucket listen when watch is cancelled #4053

Merged
merged 1 commit into from
Apr 15, 2022

Conversation

vadmeste
Copy link
Member

When mirror in --watch mode is restarted, the previous minio-go
ListenNotification/ListenBucketNotification call is not properly
canceled. This commit creates a new context for that listen call and
cancels it when client-s3 Watch() is asked to be stopped.

When mirror in --watch mode is restarted, the previous minio-go
ListenNotification/ListenBucketNotification call is not properly
canceled. This commit creates a new context for that listen call and
cancels it when client-s3 Watch() is asked to be stopped.
@harshavardhana
Copy link
Member

IMO we should also fix server-side @vadmeste such that - we should not allow more than X amount of active Listen Notifications.

@harshavardhana harshavardhana merged commit 6a61b28 into minio:master Apr 15, 2022
@vadmeste
Copy link
Member Author

IMO we should also fix server-side @vadmeste such that - we should not allow more than X amount of active Listen Notifications.

Yes, 1024 looks a fair number

@vadmeste
Copy link
Member Author

Yes, 1024 looks a fair number

Maybe we can do 1024 per node instead for bucket notification and 8 per node for tracing.

@harshavardhana
Copy link
Member

Yes, 1024 looks a fair number

Maybe we can do 1024 per node instead for bucket notification and 8 per node for tracing.

Yeah that is an okay value but still high though.

adfost pushed a commit to adfost/mc that referenced this pull request Oct 28, 2022
When mirror in --watch mode is restarted, the previous minio-go
ListenNotification/ListenBucketNotification call is not properly
canceled. This commit creates a new context for that listen call and
cancels it when client-s3 Watch() is asked to be stopped.
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

2 participants