Description of problem: Support an optional configuration setting for the maximum number of object sets a journal client can be behind before it is automatically unregistered. This will protect the journal from growing to an infinite size.
Upstream, master branch PR: https://github.com/ceph/ceph/pull/10378
(In reply to Jason Dillaman from comment #0) > Description of problem: > Support an optional configuration setting for the maximum number of object > sets a journal client can be behind before it is automatically unregistered. 1) Where and how this value is set? 2) Is the value persistent across reboot/restarts? 3) Is there a default value? 4) What is the range (lower and upper limit)? 5) how to induce the condition in which a journal client is 'laggy'
1) This is controlled by the config option "rbd_journal_max_concurrent_object_sets". By default, it is set to zero (disabled). This indicates how many journal object sets (each object set is comprised of splay width number of journal data objects) can exist before the laggy rbd-mirror client is disconnected (and the object sets are pruned). 2) It's a config option, so yes. 3) Yes, zero (disabled) 4) Zero to max uint64_t (effectively infinity) 6) Mirror and image to a secondary cluster, disable its rbd-mirror daemon so that journal events aren't being consumed. Inject enough IO data into the primary image to overflow the "concurrent object set" limit. You can use "rbd journal status --image <image name>" to see the active and minimum object set number. After overflow, it should lazily start trimming old object sets and the minimum object set number will start to converge with the active.
Upstream test case: https://github.com/ceph/ceph/blob/master/qa/workunits/rbd/rbd_mirror.sh#L298
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://rhn.redhat.com/errata/RHSA-2016-2815.html