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

Add backoff to key collection manager refresh scheduling

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.9
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-06-19

      The following executor configuration

      executor:
        config:
          shell_options:
            global_vars:
              TestData:
                auth: true
                authMechanism: SCRAM-SHA-1
                keyFile: *keyFile
                keyFileData: *keyFileData
            nodb: ''
            readMode: commands
        fixture:
          class: ShardedClusterFixture
          mongos_options:
            bind_ip_all: ''
            set_parameters:
              enableTestCommands: 1
              logComponentVerbosity:
                verbosity: 0
                command: 1
                network:
                  verbosity: 1
                  asio: 2
                tracking: 1 
      
          mongod_options:
            bind_ip_all: ''
            nopreallocj: ''
            enableMajorityReadConcern: ''
            set_parameters:
              enableTestCommands: 1
              logComponentVerbosity:
                verbosity: 0
                command: 1
                network:
                  verbosity: 1
                  asio: 2
                replication:
                  heartbeats: 2
                tracking: 1 
              numInitialSyncAttempts: 1
          num_rs_nodes_per_shard: 2
          enable_sharding:
          - test
      

      this executor when run in resmoke will show too frequent key refresh events in its log. Need to adjust the scheduling in the presence of failures.

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: