Skip range deletion of chunks containing MaxKey docs

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a follow up work after SERVER-121533.

      Add a server parameter that stays off by default. The server checks this param and then checks if there are any MaxKey documents orphaned on any shard. Whenever it is on it will skip deleting orphan documents belonging to that final chunk and log a message. This continues until the server param is disabled or MaxKey orphans are not present. This log is ingested in Atlas logging for alerts.

       

      We can perform the check on startup and log message to alerge first to avoid long time to reach the last chunk range deletion task if it exists.

            Assignee:
            Abdul Qadeer
            Reporter:
            Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: