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

Sharded collections becomes inaccessible when it becomes to big

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • ALL
    • Hide

      Create a sharded setup where the config.chunks collection contains 40 million entries and half of them relates to one single collection.

      Try to start a MongoS

      Show
      Create a sharded setup where the config.chunks collection contains 40 million entries and half of them relates to one single collection. Try to start a MongoS

    Description

      I have a large sharded (+500TB) collection that right now is inaccessible because of a timeout in the synchronization between MongoC and MongoS.

      Both MongoS and MongoC are run on enterprise class servers with 10Gbit network with <0.1ms latency.

      The Shareded collection has +20 million entries in the config.chunks collection on the MongoC - and the total number of entries in config.chunks collection is +40 million. When the MongoS starts there is a (hardcoded?) limit of 1 min for each collection to sync config.chunks from the MongoC to the MongoS...And if it fails the MongoS will not start at all.
      I have tried to add loadRoutingTableOnStartup: false to the mongos config and the result is that mongos starts and all other collections are accessible but I am still not able to access the large sharded collection.

      Is there a way to change that timeout in the MongoS?

      Attachments

        Activity

          People

            eric.sedor@mongodb.com Eric Sedor
            nicolai@niro-it.dk Nicolai Ødum
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: