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

distributed lock needs to be checked periodically

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • None
    • 1.9.0
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      If processes using the distributed lock take longer than a few minutes to complete, it is possible that the config servers could go unresponsive during the process, come back up, and be queried by other processes before the still-running process has a chance to ping again, leading to an incorrect forcing. Think the easiest way to avoid this is to re-acquire the distributed lock every 5-7 mins or so in long-running processes (1/2 the timeout time)?

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: