replica set resilience on election time after primary is down

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: 3.6.4
    • Component/s: Operations Layer
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Problem

      Under high load on database, connection errors when primary changes.

      Some examples with three nodes replica set:

      1) Switch off the primary node of three nodes.

      2) with one node down, and two up, a primary and a secondary, switch on again the node. When primary changes, the program is not able to keep working on mongo as it lose the connection

      Configuration to reproduce:

      mongodb driver version 3.6.4

      node 12

      Steps to reproduce

      https://github.com/RadW2020/mongoEnot/tree/insert-remove

      NOTE: This ticket is related to https://jira.mongodb.org/browse/NODE-3112 but having in consideration only the insertOne 

      https://github.com/RadW2020/mongoEnot/tree/insert-remove

              Assignee:
              Unassigned
              Reporter:
              Raúl Jiménez
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: