ListCollections does not use read preference primary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 0.2.0
    • Affects Version/s: 0.1.0
    • Component/s: Command & Dispatch
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The ListCollections database method passes through the database's read selector instead of constructing a new read selector for read preference primary. (Compare to how ListDatabases does it.)

      Because the constructed command adds read preference primary (despite possibly selecting a non-primary server), ListCollections run on a database with secondary read preference will fail with an error: "(NotMasterNoSlaveOk) not master and slaveOk=false".

              Assignee:
              Divjot Arora (Inactive)
              Reporter:
              David Golden
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: