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

db.getCollectionNames can take more than 10 minutes to execute

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.5
    • Component/s: None
    • None
    • Sharding
    • ALL
    • Hide

      Set up a mongodb 3.6.5 cluster of three nodes(maybe one is also ok).

      Create over 75000 collections. 

      Access mongodb via WAN from mongo shell.

      Call db.getCollectionNames().

      Observe it execute for a very long time (around 8 minutes).

      Show
      Set up a mongodb 3.6.5 cluster of three nodes(maybe one is also ok). Create over 75000 collections.  Access mongodb via WAN from mongo shell. Call db.getCollectionNames(). Observe it execute for a very long time (around 8 minutes).
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      db.getCollectionNames works unacceptably slow via internet if you have thousands of collections.

      doesn't reproduce with local networks

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            developer@tab-trader.com tab trader
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: