With a large number of deletes in a client workload, this can easily saturate a disk and cause very high latency, since it does not go through the op queue or do any batching. To fix this, make recovery handle these deletes instead of performing them during peering.
verified on 12.2.1-39.el7cp
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-2017:3387