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

Do not acquire the RSTL for idents cleanup

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution
    • 17

    Description

      Currently, dropIdentsOlderThan acquires a global intent lock, which then implicitly acquires RSTL. Slowness in the subsequent for loop of dropping idents could result in delay in replication state transitions because TimestampMonitor is not killable by the RstlKillOpThread. This ticket is to investigate whether idents cleanup needs synchronization with step up and step down. If not, consider dropping RSTL for idents clean.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: