Comment 5 for bug 1733588

Reviewed: https://review.openstack.org/524548
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=d8f9045518035cbd1a40d0a94227952a384143ec
Submitter: Zuul
Branch: master

commit d8f9045518035cbd1a40d0a94227952a384143ec
Author: Christopher Bartz <email address hidden>
Date: Fri Dec 1 11:13:10 2017 +0100

    Send correct number of X-Delete-At-* headers

    Send just as many requests with X-Delete-At-* as we do X-Container-* to
    the object server. Furthermore, stop the object server on making an
    update to the expirer queue when it wasn't told to do so and remove the
    log warning which would have been produced.

    Reason:

    It can be the case that the number of object replicas (OR) is larger
    than the number of container replicas (CR) for a given storage policy
    (most likely in case of EC). Before this commit, only CR object servers
    received the x-delete-at-* headers, which means that OR - CR object
    servers did not receive the headers. The servers missing the header
    would produce a log warning and create the x-delete-at-container header
    and async update on their own, which could lead to a bug, if the
    expiring_objects_container_divisor option was misconfigured.

    Change-Id: I20fc2f42f590fda995814a2fa7ba86019f9fddc1
    Closes-Bug: #1733588