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

Additional logv2 message cleanup for sharding

    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-06-01, Sharding 2020-06-15

      Found a couple more messages we missed in the Evergreen logs. There may be other messages in those files that don't happen to show up in the Evergreen logs, so may be worth another look over those files.

      src/mongo/db/s/config/sharding_catalog_manager_chunk_operations.cpp: 23887
      src/mongo/db/s/range_deletion_util.cpp: 23774
      src/mongo/db/s/move_primary_command.cpp: 23762
      src/mongo/s/write_ops/batch_write_exec.cpp: 22911

      The last one is puzzling - it looks to be fixed in master, but it was showing up in the display_sharding_multiversion test yesterday.

      {"t":{"$date":"2020-05-20T07:36:03.538+00:00"},"s":"W",  "c":"SHARDING", "id":22911,   "ctx":"conn57","msg":"could not refresh targeter{causedBy_refreshStatus_reason}","attr":{"causedBy_refreshStatus_reason":" :: caused by :: operation was interrupted"}}
      

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: