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

While upgrading from Shard 3.4 to Shard 3.6 config.system.sessions is not sharded.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.6.5
    • Component/s: Sharding
    • Labels:
      None
    • ALL
    • Hide

      1. db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )

      Run this command from Mongos. 

      2. Made sure the compatiblity is 3.4 before starting the upgrade. 

      3. Stop the balancer. 

      4. Choose the secondary. Gracefully shutdown the servers.

      5, Remove the 3.4 packages. 

      6. Install 3.6.5 packages. 

      7. Start the mongod and mongo config server. 

      8. Wait for the servers to join the cluster. 

      9. Repeat the steps from 4 to 8 for the other secondary. 

      10. Step down the mongo shard primary and mongo config primary. 

      11. Repeat steps 4 to 8 on the last secondary. 

      12. After that upgrade the mongos component. 

      13. Start the balancer. 

      14. Monitor the error logs. 

      Show
      1. db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } ) Run this command from Mongos.  2. Made sure the compatiblity is 3.4 before starting the upgrade.  3. Stop the balancer.  4. Choose the secondary. Gracefully shutdown the servers. 5, Remove the 3.4 packages.  6. Install 3.6.5 packages.  7. Start the mongod and mongo config server.  8. Wait for the servers to join the cluster.  9. Repeat the steps from 4 to 8 for the other secondary.  10. Step down the mongo shard primary and mongo config primary.  11. Repeat steps 4 to 8 on the last secondary.  12. After that upgrade the mongos component.  13. Start the balancer.  14. Monitor the error logs. 
    • Sharding 2018-07-16

      Hello, 

       

      I have 2 shards. And each shard is running with 1 primary and 2 secondary. 

      I am sharing the config server along with mongod to share the cost of the project. 

      All components were running on mongo 3.4.10. 

      For the upgrade I followed the below process. 

       

      These are the error logs found. 

       

      2018-07-04T22:57:34.431+0800 I REPL [rsBackgroundSync] could not find member to sync from
      2018-07-04T22:57:39.429+0800 I REPL [SyncSourceFeedback] SyncSourceFeedback error sending update to mongo-dba-test01.mylab.com:27017: InvalidSyncSource: Sync source was cleared. Was mongo-dba-test01.mylab.com:27017
      2018-07-04T22:57:40.476+0800 I REPL [replexec-7] Starting an election, since we've seen no PRIMARY in the past 10000ms

       

      NetworkInterfaceASIO-ShardRegistry-0] Connecting to mongo-dba-test01.mylab.com:27017
      2018-07-04T22:56:48.659+0800 I ASIO [NetworkInterfaceASIO-ShardRegistry-0] Successfully connected to mongo-dba-test01.mylab.com:27017, took 2ms (1 connections now open to mongo-dba-test01.mylab.com:27017)
      2018-07-04T22:56:48.661+0800 I SHARDING [ShardServerCatalogCacheLoader-0] Refresh for collection config.system.sessions took 4 ms and failed :: caused by :: CommandNotFound: no such command: 'forceRoutingTableRefresh', bad cmd: '{ forceRoutingTableRefresh: "config.system.sessions", maxTimeMS: 30000 }'

      bad command.

      The configuration files and the error logs are attached. 

       

       

       

        1. a.conf
          0.5 kB
        2. b.conf
          0.5 kB
        3. cfg.conf
          0.5 kB
        4. mongos.conf
          0.4 kB
        5. log0.log
          3.61 MB
        6. Logs.rar
          625 kB

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            baabhu@yahoo.com babu balakrishnan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: