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

replicaet data integrity fail

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      linux (openvz kernel without limit on vhosts, vserver kernel, native linux kernel), mongodb1.8
    • Linux

      Critical bug in replica set synchronisation.

      I've runned repairDatabase() to compact database files on my replSet primary host(HOST1).
      After running that command server has exhausted resources (full mem and swap use).
      MongoDB was restarted. Other host (HOST2) in replSet was set to primary status.

      When I check http://ANYHOST:28017/_replSet I found that optime on all nodes is the same.
      I've restarted primary host and HOST1 became primary.

      After logging to mongo cli and running command "show dbs"; I've seen that two first dbs was showned as "empty".

            Assignee:
            mathias@mongodb.com Mathias Stearn
            Reporter:
            msz MartinS
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: