Not master error when using node js driver

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: MongoDB 3.4
    • Environment:
      containerOS, docker.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Using a replica set on kubernetes. Read preference being used is nearest and all the read operations work fine. Not master error occurs on writes. code:10107. The problem does not occur in the shell only when using the driver. one of the members is acting as primary. I cannot figure out why the driver is unable to connect to the primary.

            Assignee:
            Unassigned
            Reporter:
            haseeb naseem
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: