Bug 1693445
Summary: | rgw-multisite sync stuck recovering shard in already deleted versioned bucket | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
Component: | RGW-Multisite | Assignee: | Casey Bodley <cbodley> |
Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
Severity: | medium | Docs Contact: | Aron Gunn <agunn> |
Priority: | medium | ||
Version: | 3.2 | CC: | agunn, anharris, cbodley, ceph-eng-bugs, ceph-qe-bugs, hklein, jbrier, mbenjamin, tserlin, vimishra |
Target Milestone: | z2 | Keywords: | CodeChange |
Target Release: | 3.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-12.2.8-113.el7cp Ubuntu: ceph_12.2.8-96redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.Synchronizing a multi-site Ceph Object Gateway was getting stuck
When recovering versioned objects, other operations were unable to finish. These stuck operations were caused by the removing of expired `user.rgw.olh.pending` extended attributes (xattrs) all at once on those versioned objects. Another link:https://bugzilla.redhat.com/show_bug.cgi?id=1663570[bug] was causing too many of the `user.rgw.olh.pending` xattrs to be written to those recovering versioned objects. With this release, batches of expired xattrs are removed instead of all at once. This results in versioned objects recovering correctly so other operations can proceed normally.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-04-30 15:57:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1629656 |
Description
Vikhyat Umrao
2019-03-27 20:42:52 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0911 |