Bug 1662353

Summary: data_log shards causing a lot of big omap objects
Product: Red Hat Ceph Storage Reporter: Vikhyat Umrao <vumrao>
Component: RGW-MultisiteAssignee: Casey Bodley <cbodley>
Status: CLOSED ERRATA QA Contact: Tejas <tchandra>
Severity: high Docs Contact: Bara Ancincova <bancinco>
Priority: high    
Version: 3.1CC: cbodley, ceph-eng-bugs, ceph-qe-bugs, edonnell, jdurgin, kdreyer, mbenjamin, pasik, roemerso, tchandra, tserlin, vimishra, vumrao
Target Milestone: z1   
Target Release: 3.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.8-84.el7cp Ubuntu: ceph_12.2.8-70redhat1xenial Doc Type: Bug Fix
Doc Text:
.Datalogs are now trimmed regularly as expected Due to a regression in decoding of the JSON format of data sync status objects, automated datalog trimming logic was unable to query the sync status of its peer zones. Consequently, the datalog trimming process did not progress. This update fixes the JSON decoding and adds more regression test coverage for log trimming. As a result, datalogs are now trimmed regularly as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-07 15:51:27 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:
Bug Depends On:    
Bug Blocks: 1629656    

Description Vikhyat Umrao 2018-12-27 23:55:27 UTC
Description of problem:
data_log shards causing a lot of big omap objects and causing OSD's to hit full ratio

Version-Release number of selected component (if applicable):
RHCS 3.1 - 12.2.5-59.el7cp.x86_64

How reproducible:
At the customer site always

Comment 55 errata-xmlrpc 2019-03-07 15:51:27 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/RHBA-2019:0475