-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Skip listing MPUs if TTL set to -1 #127166
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
Skip listing MPUs if TTL set to -1 #127166
Conversation
Recent versions of MinIO will sometimes leak multi-part uploads under concurrent load, leaving them in the `ListMultipartUploads` output even though they cannot be aborted. Today this causes repository analysis to fail since compare-and-exchange operations will not even start if there are any pre-existing uploads. This commit makes it possible to skip this pre-flight check (and accept the performance consequences) by adjusting the relevant settings. Workaround for minio/minio#21189 Closes elastic#122670
|
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
| .setting("s3.client." + CLIENT + ".endpoint", minioFixture::getAddress) | ||
| // Skip listing of pre-existing uploads during a CAS because MinIO sometimes leaks them; also reduce the delay before proceeding | ||
| // TODO do not set these if running a MinIO version in which https://github.com/minio/minio/issues/21189 is fixed | ||
| .setting(REPOSITORY_S3_CAS_TTL_SETTING.getKey(), "-1") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting this to -1 (or 0) even without the production code changes would have had pretty much the desired effect anyway because it would make ES consider all the existing uploads as stale, letting it proceed with the CAS. The production code changes just make this behaviour a little more precise, avoiding questions of clock skew and suppressing warnings about the stale uploads etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Recent versions of MinIO will sometimes leak multi-part uploads under concurrent load, leaving them in the `ListMultipartUploads` output even though they cannot be aborted. Today this causes repository analysis to fail since compare-and-exchange operations will not even start if there are any pre-existing uploads. This commit makes it possible to skip this pre-flight check (and accept the performance consequences) by adjusting the relevant settings. Workaround for minio/minio#21189 Closes elastic#122670
Recent versions of MinIO will sometimes leak multi-part uploads under concurrent load, leaving them in the `ListMultipartUploads` output even though they cannot be aborted. Today this causes repository analysis to fail since compare-and-exchange operations will not even start if there are any pre-existing uploads. This commit makes it possible to skip this pre-flight check (and accept the performance consequences) by adjusting the relevant settings. Workaround for minio/minio#21189 Closes elastic#122670
Recent versions of MinIO will sometimes leak multi-part uploads under concurrent load, leaving them in the `ListMultipartUploads` output even though they cannot be aborted. Today this causes repository analysis to fail since compare-and-exchange operations will not even start if there are any pre-existing uploads. This commit makes it possible to skip this pre-flight check (and accept the performance consequences) by adjusting the relevant settings. Workaround for minio/minio#21189 Closes #122670
Recent versions of MinIO will sometimes leak multi-part uploads under concurrent load, leaving them in the `ListMultipartUploads` output even though they cannot be aborted. Today this causes repository analysis to fail since compare-and-exchange operations will not even start if there are any pre-existing uploads. This commit makes it possible to skip this pre-flight check (and accept the performance consequences) by adjusting the relevant settings. Workaround for minio/minio#21189 Closes #122670
Earlier versions of MinIO had a bug which can cause repository analysis failures. This commit upgrades the MinIO test container version to pick up the bug fix, and reverts the workaround implemented in elastic#127166. Relates minio/minio#21189
Earlier versions of MinIO had a bug which can cause repository analysis failures. This commit upgrades the MinIO test container version to pick up the bug fix, and reverts the workaround implemented in #127166. Relates minio/minio#21189
Earlier versions of MinIO had a bug which can cause repository analysis failures. This commit upgrades the MinIO test container version to pick up the bug fix, and reverts the workaround implemented in elastic#127166. Relates minio/minio#21189
Earlier versions of MinIO had a bug which can cause repository analysis failures. This commit upgrades the MinIO test container version to pick up the bug fix, and reverts the workaround implemented in #127166. Relates minio/minio#21189
Recent versions of MinIO will sometimes leak multi-part uploads under
concurrent load, leaving them in the
ListMultipartUploadsoutput eventhough they cannot be aborted. Today this causes repository analysis to
fail since compare-and-exchange operations will not even start if there
are any pre-existing uploads. This commit makes it possible to skip this
pre-flight check (and accept the performance consequences) by adjusting
the relevant settings.
Workaround for minio/minio#21189
Closes #122670