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

Auto-repair operation after an Unexpected Shutdown

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.5
    • Component/s: None
    • None
    • ALL
    • Hide

      Sometimes because of a power failure, when Windows start the mongodb service fail to start. Mongodb service it is set on 'Automatic' startup-type. Recovery service options are: first & second failure = 'restart service', subsequent failures = 'take no action'.
      Mongodb service remains in 'starting' state an for each try to start step write in logs lines like in attached file 'mongod_part.log'.

      Show
      Sometimes because of a power failure, when Windows start the mongodb service fail to start. Mongodb service it is set on 'Automatic' startup-type. Recovery service options are: first & second failure = 'restart service', subsequent failures = 'take no action'. Mongodb service remains in 'starting' state an for each try to start step write in logs lines like in attached file 'mongod_part.log'.

      Hello,

      I read the next article http://docs.mongodb.org/manual/tutorial/recover-data-following-unexpected-shutdown/ where there are described the steps to start mongo service again.

      Could you please implement an auto-repair mechanism so the user don't have to do any manual intervention.

      We are requesting for this because we have customers that reported this problem and mongod.log file reaches huge size(tens of giga written in logs because service try to start in a loop without succes). It is not comfortable to discover your hard-disk running out of space.

      We are using mongo 2.0.5 32 bits version.

        1. mongod_part.log
          2 kB

            Assignee:
            mark.benvenuto@mongodb.com Mark Benvenuto
            Reporter:
            gabi_badescu Gabriel Badescu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: