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

Dropping 95G collection on VM crashes DB

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.8.0-rc2
    • Component/s: Diagnostics, Internal Code
    • None
    • ALL
    • Hide

      --Started mongod in 3 nodes

      mongod --dbpath /u01/data --logpath /u01/logs/log.rep01 --logappend --journal --fork --replSet repl0

      --on firstnode
      1) mongo
      2) Replica configuration
      config = {_id: "repl0",
      members:[
      {_id: 0, host: '172.20.43.14:27017'},
      {_id: 1, host: '172.20.43.15:27017'},
      {_id: 2, host: '172.20.43.16:27017'}],
      "settings" : {
      "chainingAllowed" : true,
      "heartbeatTimeoutSecs" : 10,
      "getLastErrorModes" : {

      },
      "getLastErrorDefaults" :

      { "w" : 1, "wtimeout" : 0 }

      }
      }

      3) Initiate the replica server

      rs.initiate(config);

      4) Check the status

      rs.status()

      5) use clm

      6)import the table customer using retail_customer_request_json.txt

      7) Duplicate the data for 92 GB
      nohup mongo clm --eval 'var copy = db.customer.findOne();for (var i = 0; i< 3000000; i++)

      {copy._id = new ObjectId();j = "PC00" + i;copy.profileDetails.basicDetails.customerCode=j;db.customer.insert(copy);}

      ' &

      8) drop the table using

      db.customer.drop() or drop the database clm

      Show
      --Started mongod in 3 nodes mongod --dbpath /u01/data --logpath /u01/logs/log.rep01 --logappend --journal --fork --replSet repl0 --on firstnode 1) mongo 2) Replica configuration config = {_id: "repl0", members:[ {_id: 0, host: '172.20.43.14:27017'}, {_id: 1, host: '172.20.43.15:27017'}, {_id: 2, host: '172.20.43.16:27017'}], "settings" : { "chainingAllowed" : true, "heartbeatTimeoutSecs" : 10, "getLastErrorModes" : { }, "getLastErrorDefaults" : { "w" : 1, "wtimeout" : 0 } } } 3) Initiate the replica server rs.initiate(config); 4) Check the status rs.status() 5) use clm 6)import the table customer using retail_customer_request_json.txt 7) Duplicate the data for 92 GB nohup mongo clm --eval 'var copy = db.customer.findOne();for (var i = 0; i< 3000000; i++) {copy._id = new ObjectId();j = "PC00" + i;copy.profileDetails.basicDetails.customerCode=j;db.customer.insert(copy);} ' & 8) drop the table using db.customer.drop() or drop the database clm

      Dropped a 92G collection on VM. It crashed the database.Database never came up after crash. Replication Secondary also failed to come up.
      Please refer the Log file Mongodb_Droptable_issue_log.txt

      Note:
      Overcommit_Memory and transparent_hugepage was not set to the recommended values 0 and never.

        1. mdiag-bapdmong-14.nova.dev.txt.gz
          63 kB
          Lakshminarayanan S Iyer
        2. Mongodb_Droptable_issue_log.txt
          11 kB
          Lakshminarayanan S Iyer
        3. retail_customer_request_json.txt
          90 kB
          Lakshminarayanan S Iyer

            Assignee:
            sam.kleinman Sam Kleinman (Inactive)
            Reporter:
            lnarayanan Lakshminarayanan S Iyer
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: