Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-2483

Mongo Dump: error writing data for collection `.oplog` to disk

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.16
    • Component/s: mongodump
    • Labels:
      None

      Hi,

      I'm trying to dump a collection of 235 GB approx but i'm getting the following error:

       

      2020-02-05T16:49:01.877+0000 ######################. analytics.stats 351300604/355758432 (98.7%)
      2020-02-05T16:49:04.877+0000 ######################. analytics.stats 351640594/355758432 (98.8%)
      2020-02-05T16:49:07.877+0000 ######################. analytics.stats 351980793/355758432 (98.9%)
      2020-02-05T16:49:10.877+0000 ######################. analytics.stats 352278639/355758432 (99.0%)
      2020-02-05T16:49:13.877+0000 ######################. analytics.stats 352619533/355758432 (99.1%)
      2020-02-05T16:49:16.877+0000 ######################. analytics.stats 352961026/355758432 (99.2%)
      2020-02-05T16:49:19.877+0000 ######################. analytics.stats 353312675/355758432 (99.3%)
      2020-02-05T16:49:22.877+0000 ######################. analytics.stats 353656270/355758432 (99.4%)
      2020-02-05T16:49:25.877+0000 ######################. analytics.stats 354000236/355758432 (99.5%)
      2020-02-05T16:49:28.877+0000 ######################. analytics.stats 354342676/355758432 (99.6%)
      2020-02-05T16:49:31.877+0000 ######################. analytics.stats 354666623/355758432 (99.7%)
      2020-02-05T16:49:34.877+0000 ######################. analytics.stats 354986628/355758432 (99.8%)
      2020-02-05T16:49:37.877+0000 ######################. analytics.stats 355373627/355758432 (99.9%)
      2020-02-05T16:49:40.877+0000 ######################. analytics.stats 355674217/355758432 (100.0%)
      2020-02-05T16:49:41.641+0000 ####################### analytics.stats 355767137/355758432 (100.0%)
      2020-02-05T16:49:41.641+0000 MuxIn close analytics.stats
      2020-02-05T16:49:41.688+0000 Mux close namespace analytics.stats
      2020-02-05T16:49:41.688+0000 done dumping analytics.stats (355767137 documents)
      2020-02-05T16:49:41.688+0000 ending dump routine with id=3, no more work to do
      2020-02-05T16:49:41.689+0000 dump phase III: the oplog
      2020-02-05T16:49:41.695+0000 checking if oplog entry 6789959539648102408 still exists
      2020-02-05T16:49:41.696+0000 oldest oplog entry has timestamp 6789752273116374733
      2020-02-05T16:49:41.696+0000 oplog entry 6789959539648102408 still exists
      2020-02-05T16:49:41.696+0000 writing captured oplog to
      2020-02-05T16:49:41.696+0000 MuxIn open .oplog
      2020-02-05T16:49:41.704+0000 Mux open namespace .oplog
      2020-02-05T16:55:25.528+0000 counted 34203690 documents in .oplog
      2020-02-05T16:55:25.877+0000 [........................] .oplog 9119/34203690 (0.0%)
      2020-02-05T16:55:28.877+0000 [........................] .oplog 136605/34203690 (0.4%)
      2020-02-05T16:55:31.877+0000 [........................] .oplog 274229/34203690 (0.8%)
      2020-02-05T16:55:34.877+0000 [........................] .oplog 407426/34203690 (1.2%)
      2020-02-05T16:55:37.877+0000 [........................] .oplog 534544/34203690 (1.6%)
      2020-02-05T16:55:40.877+0000 [........................] .oplog 648386/34203690 (1.9%)
      2020-02-05T16:55:43.877+0000 [........................] .oplog 771454/34203690 (2.3%)
      2020-02-05T16:55:46.877+0000 [........................] .oplog 897006/34203690 (2.6%)
      2020-02-05T16:55:49.877+0000 [........................] .oplog 1032218/34203690 (3.0%)
      2020-02-05T16:55:52.877+0000 [........................] .oplog 1154521/34203690 (3.4%)
      2020-02-05T16:55:55.877+0000 [........................] .oplog 1272329/34203690 (3.7%)
      2020-02-05T16:55:58.877+0000 [........................] .oplog 1393692/34203690 (4.1%)
      2020-02-05T16:56:01.877+0000 ....................... .oplog 1520767/34203690 (4.4%)
      2020-02-05T16:56:04.877+0000 ....................... .oplog 1648026/34203690 (4.8%)
      2020-02-05T16:56:07.877+0000 ....................... .oplog 1762560/34203690 (5.2%)
      2020-02-05T16:56:10.877+0000 ....................... .oplog 1879797/34203690 (5.5%)
      2020-02-05T16:56:13.657+0000 ....................... .oplog 2011259/34203690 (5.9%)
      2020-02-05T16:56:13.657+0000 MuxIn close .oplog
      2020-02-05T16:56:13.943+0000 Mux close namespace .oplog
      2020-02-05T16:56:13.943+0000 Mux finish
      2020-02-05T16:56:13.944+0000 mux completed successfully
      2020-02-05T16:56:13.944+0000 Failed: error dumping oplog: error writing data for collection `.oplog` to disk: cannot dump with oplog while renames occur

      }}{{
      I have plenty of disk space,  I've also increased the oplog as well... Even tried to create a hidden node but nothing changed. 

      rs0:SECONDARY> db.getReplicationInfo()rs0:SECONDARY> db.getReplicationInfo(){ "logSizeMB" : 65536, "usedMB" : 65183.89, "timeDiff" : 58591, "timeDiffHours" : 16.28, "tFirst" : "Sun Feb 16 2020 19:26:35 GMT+0000 (UTC)", "tLast" : "Mon Feb 17 2020 11:43:06 GMT+0000 (UTC)", "now" : "Mon Feb 17 2020 11:43:06 GMT+0000 (UTC)"}rs0:SECONDARY> 

      Is there anything I need to do or change? 

       

            Assignee:
            tim.fogarty@mongodb.com Tim Fogarty
            Reporter:
            david.castaneda@exoclick.com David Castañeda
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: