Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-49050

Cannot differentiate logs from different shards with python fixtures

XMLWordPrintableJSON

    • Fully Compatible
    • STM 2020-06-29

      A log line looks like:

      [ReplicaSetFixture:job3:primary] 2020-06-23T20:45:36.852+0000 | 2020-06-23T20:45:36.852+00:00 D2 REPL_HB  24096   [conn10] "Processing heartbeat request","attr":{"from":"localhost:20752","cmdObj":{"replSetHeartbeat":"shard-rs0","configVersion":2,"configTerm":1,"hbv":1,"from":"localhost:20752","fromId":1,"term":1,"primaryId":0,"$replData":1,"$clusterTime":{"clusterTime":{"$timestamp":{"t":1592945134,"i":10006}},"signature":{"hash":{"$binary":{"base64":"y8JOMcj9Fb52irp9PYt2OwlEJ5I=","subType":"0"}},"keyId":6841647160363057000}},"$configTime":{"$timestamp":{"t":1592945134,"i":2}},"$db":"admin"}}

      But I do not think there's a way to really know which shard/csrs it belongs to. We just know it's a primary on in some replica set. The test fixture knows its replica set name, so we just need to include it in the log.

            Assignee:
            carl.worley@mongodb.com Raiden Worley (Inactive)
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: