Do not log range deletion task registration on shard secondaries

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0, 7.0.0-rc3
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v7.0
    • Sharding EMEA 2023-05-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Since the range deleter observer runs on any node of a shard, also secondaries may try to register tasks on the range deleter service. This is fine because the registration on secondaries will fail and be gracefully handled by the observer.

      Purpose of this ticket is to move this log line after the acquisition of the mutex (only successful on the primary) in order not to log it on secondaries.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: