Uploaded image for project: 'MongoDB ETL Tools'
  1. MongoDB ETL Tools
  2. TOOLS-2301

Dramatic connection time difference for mongodump/mongorestore on Windows since 3.4



    • Type: Bug
    • Status: Accepted
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: 3.4.21, 4.0.9, 3.6.13
    • Fix Version/s: None
    • Component/s: mongodump, mongorestore
    • Labels:
    • Environment:


      Tools on windows connecting to localhost suffer a long name resolution delay. A workaround is to connect to


      After migration from MongoDB v2.0.9 to v4.0.9 the main bad thing I noticed is a huge time for execution dump/restore commands.

      For v2.0.9 those operations were almost instantaneous (dataset is tiny). But same commands for same datasets with new binaries for v4.0.9 take seconds for the same operations.

      From the verbose log, I can see that 2 seconds it does nothing before starting to perform the operation.


      2019-06-04T11:14:26.413+0300 will listen for SIGTERM, SIGINT, and SIGKILL
      2019-06-04T11:14:28.430+0300 enqueued collection 'potrust_1.ReadStats'
      2019-06-04T11:14:29.503+0300    finishing dump



       I use dump/restore a lot in test cases between tests (actually hundreds of such operations) so now my tests run like 2-3 times longer (

      Am I doing something wrong or is it really should be so slow now? Is it because tools are now written in go?


        1. logs_3.2.txt
          4 kB
        2. logs_3.4_with_host.txt
          4 kB
        3. logs_3.4.txt
          5 kB
        4. logs_4.2.txt
          4 kB
        5. verbose_mongod_3.2.log
          145 kB
        6. verbose_mongod_3.4.log
          107 kB

          Issue Links



              • Assignee:
                backlog-server-tools Backlog - Server Tools Team
                inversion Yura Babak
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created: