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

Ticket acquisition should more accurately adjust timeout for maxTimeMS

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Concurrency
    • Labels:

      Description

      Currently, for ticket acquisition, we don't respect the "maxTimeMS". We should do the same thing like we do it for the lock acquisition wait /prepare conflict wait . Though, TicketHolder::waitForTicketUntil() has the default smallest wait interval as 500 ms. If any user sets the command maxTimeMS < 500ms, then it's a problem.-

      EDIT:

      It's not just problem with maxTimeMs <500ms. Basically, ticket acquisition can wait up to maxTimeMs+ 500ms (default semaphore wait interval), Eg. If user sets maxTimeMs = 1005, the cmd wait  for 1500ms to acquire ticket. 

        Attachments

          Activity

            People

            Assignee:
            backlog-server-execution Backlog - Execution Team
            Reporter:
            suganthi.mani Suganthi Mani
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: