mongos logs incorrect nShards value

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.2.17
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      An upsert operation that successfully inserted a document was logged in mongos.log with nShards:0, when a similar test was repeated later nShards:1 was correctly reported. 

            Assignee:
            Unassigned
            Reporter:
            Peter Williamson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: