Retryable reads attempts use different implicit sessions

XMLWordPrintableJSON

    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      When executing a retryable read with an implicit session, pymongo uses one implicit session for the initial attempt and another implicit session for the retry.

      This is a bug as the spec says:

      The minimum server version is 3.6 because

      • It gives us version parity with retryable writes.
      • It forces the *retry attempt to use the same implicit session, which would make it it easier to track operations and kill any errant longer running operation*.
        ...

      This was uncovered by the tests added in PYTHON-2075.

            Assignee:
            Noah Stapp
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: