Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71436

Range deleter must not aggressively spam the log when shard key index not found

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.19, 5.0.15, 6.0.4, 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.2, v6.1, v6.0, v5.0, v4.4
    • Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12

      The range-deleter is deleting orphaned documents by scanning an index compatible with the shard key.

      When no index on the shard key is found on a shard trying to perform orphans deletion, the range-deleter starts to spam the logs aggressively and indefinitely with the "Unable to find shard key index" error; this results in a relevant increase on the log file size up to some GBs per hour.

      Purpose of this ticket is to:

      • Throttle the logging of the problem (e.g. by simply introducing a sleep of X seconds in case the shard key index is not found)
      • Change the returned error code from InternalError to the more meaningful IndexNotFound code.

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            0 Vote for this issue
            4 Start watching this issue