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

Add to information contained in logfile about "moveChunk.to"

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2, v4.0, v3.6

      Description

      Current log files for shards do not have consistency between "moveChunk.from" and moveChunk.to" log events.

      moveChunk.from provides both source shard and destination shard fields whilst moveChunk.to does not. I am aware that this can be sourced from previous events such as moveChunk.commit, but it will be a lot better if the information can be gathered from one line

      moveChunk.from:

      2020-01-21T14:51:49.275+1100 I SHARDING [conn29] about to log metadata event into changelog: { _id: "XX", server: "XX", clientAddr: "", time: new Date(1579578709275), what: "moveChunk.from", ns: "test.products", details: { min: { sku: MinKey }, max: { sku: 23153496 }, step 1 of 6: 0, step 2 of 6: 1, step 3 of 6: 226, step 4 of 6: 13441, step 5 of 6: 331, step 6 of 6: 61, to: "shard02", from: "shard01", note: "success" } }
      

      moveChunk.to:

      2020-01-21T14:51:49.207+1100 I SHARDING [migrateThread] about to log metadata event into changelog: { _id: "XX, server: "XX", clientAddr: "", time: new Date(1579578709206), what: "moveChunk.to", ns: "test.products", details: { min: { sku: MinKey }, max: { sku: 23153496 }, step 1 of 6: 157, step 2 of 6: 20, step 3 of 6: 11589, step 4 of 6: 0, step 5 of 6: 1704, step 6 of 6: 293, note: "success" } }
      

       

        Attachments

          Activity

            People

            Assignee:
            josef.ahmad Josef Ahmad
            Reporter:
            giuliano.celani Giuliano Celani (Inactive)
            Participants:
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: