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

Mongodb crashed after - FlushViewOfFile for F:/data/xq.4 failed with error 1117 after 1 attempts taking 7076 ms

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 2.2.2
    • Fix Version/s: None
    • Component/s: Internal Code
    • Labels:
      None
    • Environment:
      Azure Worker Role - 3 replica set databases on 3 Azure instances
    • Operating System:
      Windows
    • Steps To Reproduce:
      Hide

      This appears to be a random event.

      Show
      This appears to be a random event.

      Description

      This happened in our production system in the middle of the night on a Sunday morning. I cannot see anything that might of triggered this. The database did recover once we restarted mongod.

      See attached log file for more details. This is failure extracted from that file.

      [DataFileSync] FlushViewOfFile for F:/data/xq.4 failed with error 1117 after 1 attempts taking 7076 ms
      [DataFileSync]   Fatal Assertion 16387
      [DataFileSync] mongod.exe    ...\src\mongo\util\stacktrace.cpp(161)                           mongo::printStackTrace+0x3e
      [DataFileSync] mongod.exe    ...\src\mongo\util\assert_util.cpp(126)                          mongo::fassertFailed+0x43
      [DataFileSync] mongod.exe    ...\src\mongo\util\mmap_win.cpp(375)                             mongo::WindowsFlushable::flush+0x425
      [DataFileSync] mongod.exe    ...\src\mongo\util\mmap.cpp(183)                                 mongo::MongoFile::_flushAll+0x2b3
      [DataFileSync] mongod.exe    ...\src\mongo\db\db.cpp(427)                                     mongo::DataFileSync::run+0x24c
      [DataFileSync] mongod.exe    ...\src\mongo\util\background.cpp(64)                            mongo::BackgroundJob::jobBody+0x25c
      [DataFileSync] mongod.exe    ...\src\third_party\boost\boost\bind\mem_fn_template.hpp(165)    boost::_mfi::mf1<void,mongo::BackgroundJob,boost::shared_ptr<mongo::BackgroundJob::JobStatus> >::operator()+0x47
      [DataFileSync] mongod.exe    ...\src\third_party\boost\boost\thread\detail\thread.hpp(63)     boost::detail::thread_data<boost::_bi::bind_t<void,boost::_mfi::mf1<void,mongo::BackgroundJob,boost::shared_ptr<mongo::BackgroundJob::JobStatus> >,boost::_bi::list2<boost::_bi::value<mongo::BackgroundJob * __ptr64>,boost::_bi::value<boost::shared_ptr<mongo::BackgroundJob::JobStatus> > > > >::run+0x31
      [DataFileSync] mongod.exe    ...\src\third_party\boost\libs\thread\src\win32\thread.cpp(180)  boost::`anonymous namespace'::thread_start_function+0x21
      [DataFileSync] mongod.exe    f:\dd\vctools\crt_bld\self_64_amd64\crt\src\threadex.c(314)      _callthreadstartex+0x17
      [DataFileSync] mongod.exe    f:\dd\vctools\crt_bld\self_64_amd64\crt\src\threadex.c(292)      _threadstartex+0x7f
      [DataFileSync] kernel32.dll                                                                   BaseThreadInitThunk+0xd
      [DataFileSync]
      ***aborting after fassert() failure

        Attachments

        1. MongoCrash.log
          20 kB
        2. WADWindowsEventLogsTable.csv
          4 kB

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: