Bug 1655705 - rgw: improve reshard config options
Summary: rgw: improve reshard config options
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW
Version: 3.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: 3.2
Assignee: J. Eric Ivancich
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-03 18:08 UTC by J. Eric Ivancich
Modified: 2019-01-03 19:02 UTC (History)
9 users (show)

Fixed In Version: RHEL: ceph-12.2.8-49.el7cp Ubuntu: ceph_12.2.8-44redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-03 19:02:28 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0020 None None None 2019-01-03 19:02:36 UTC

Description J. Eric Ivancich 2018-12-03 18:08:04 UTC
This BZ is to enhance rgw resharding in a number of ways by backporting the commits in the following PRs:

    https://github.com/ceph/ceph/pull/25003
    https://github.com/ceph/ceph/pull/25356

Enhancements include:

* set a more reasonable default for the lock duration for bucket resharding
* provide two more ADVANCED config options -- rgw_reshard_batch_size and rgw_reshard_max_aio
* improve documentation for bucket resharding config options
* convert all bucket resharding config options to use "modern" config options rather than legacy config options

Comment 3 J. Eric Ivancich 2018-12-03 18:11:26 UTC
Matt, please evaluate this for inclusion. I've already done the backport (relatively trivial). If you're onboard, assign to me and I'll get the commits on ceph-3.2-rhel-patches quickly.

Comment 10 errata-xmlrpc 2019-01-03 19:02:28 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:0020


Note You need to log in before you can comment on or make changes to this bug.