fix(s3api): improve PutBucketHandler comment for orphaned collection recovery
Clarify the comment and log message for the case where a collection exists but the bucket directory is missing, explaining the root cause (partial deletion) more precisely.
This commit is contained in:
@@ -251,11 +251,12 @@ func (s3a *S3ApiServer) PutBucketHandler(w http.ResponseWriter, r *http.Request)
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
// If collection exists but bucket directory doesn't, this is an orphaned state
|
// If collection exists but bucket directory doesn't, this is an inconsistent state
|
||||||
// from a previous bucket deletion where volumes haven't been fully cleaned up yet.
|
// that can occur when a previous bucket deletion partially completed (collection
|
||||||
// Allow the bucket to be recreated by proceeding with directory creation.
|
// deletion failed but directory deletion succeeded, or volumes were recreated).
|
||||||
|
// Recover by proceeding to create the missing bucket directory.
|
||||||
if collectionExists {
|
if collectionExists {
|
||||||
glog.Warningf("PutBucketHandler: collection exists but bucket directory missing for %s, recreating bucket directory", bucket)
|
glog.Warningf("PutBucketHandler: collection exists but bucket directory missing for %s, recovering by creating bucket directory", bucket)
|
||||||
}
|
}
|
||||||
|
|
||||||
// Check for x-amz-bucket-object-lock-enabled header BEFORE creating bucket
|
// Check for x-amz-bucket-object-lock-enabled header BEFORE creating bucket
|
||||||
|
|||||||
Reference in New Issue
Block a user