mongos shouldn't log the warning in the log when config server order isn't matching the configuration

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Works as Designed
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Logging, Sharding
    • None
    • Sharding 2017-10-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, if the config server's order in the mongos configuration doesn't match the configuration, the following warning message is logged:

      W NETWORK  [connXYZ] db exception when initializing on config, current connection state is { state: { conn: "CSRS_ReplicaSet/host1:port1,host2:port2,host3:port3", vinfo: "config:CSRS_ReplicaSet/host3:port3,host1:port1,host2:port2", cursor: "(empty)", count: 0, done: false }, retryNext: false, init: false, finish: false, errored: false } :: caused by :: 70 Shard not found for server: CSRS_ReplicaSet/host1:port1,host2:port2,host3:port3

      Since the order of config servers insn't important for CSRS, the warning shouldn't be logged.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Andrey Brindeyev
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: