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

mongos aborts with InterruptedAtShutdown exception

    • Cluster Scalability
    • ALL
    • 2

      In this patch build
      mongos aborts with this stack trace:
      (gdb) ba
      #0 0x00007f6f5dd09c1f in raise () from /lib64/libpthread.so.0
      #1 0x00007f6f60a27b5e in mongo::(anonymous namespace)::endProcessWithSignal (signalNum=6) at src/mongo/util/signal_handlers_synchronous.cpp:120
      #2 mongo::(anonymous namespace)::myTerminate () at src/mongo/util/signal_handlers_synchronous.cpp:262
      #3 0x00007f6f602107fa in _cxxabiv1::_terminate(void ()) () from /data/debug/lib/libfmt.so
      #4 0x00007f6f60210865 in std::terminate() () from /data/debug/lib/libfmt.so
      #5 0x00007f6f5aa6439b in __clang_call_terminate () from /data/debug/lib/libperiodic_runner_impl.so
      #6 0x00007f6f5aa60bdc in mongo::stdx::thread::thread<mongo::PeriodicRunnerImpl::PeriodicJobImpl::_run()::$_0, , 0>(mongo::PeriodicRunnerImpl::PeriodicJobImpl::_run()::$_0)::{lambda()#1}::operator()() (this=<optimized out>) at src/mongo/stdx/thread.h:193
      #7 std::_invoke_impl<void, mongo::stdx::thread::thread<mongo::PeriodicRunnerImpl::PeriodicJobImpl::_run()::$_0, , 0>(mongo::PeriodicRunnerImpl::PeriodicJobImpl::_run()::$_0)::{lambda()#1}>(std::invoke_other, mongo::stdx::thread::thread<mongo::PeriodicRunnerImpl::PeriodicJobImpl::_run()::$_0, , 0>(mongo::PeriodicRunnerImpl::PeriodicJobImpl::_run()::$_0)::{lambda()#1}&&) (_f=...) at /opt/mongodbtoolchain/revisions/69f4f0673ffcb290ce2307560a4883ecf2ad138c/stow/gcc-v4.35T/lib/gcc/x86_64-mongodb-linux/11.3.0/../../../../include/c++/11.3.0/bits/invoke.h:61
      #8 0x00007f6f5f18e644 in execute_native_thread_routine () from /data/debug/lib/libabsl_base.so
      #9 0x00007f6f5dcff2de in start_thread () from /lib64/libpthread.so.0
      #10 0x00007f6f5d817a63 in clone () from /lib64/libc.so.6
       

      Max suggests the following: "I would say the InterruptedAtShutdown exception likely came from https://github.com/mongodb/mongo/blob/7060765f3e0d33b74b2f6c7764fb3e88ece3b805/src/mongo/idl/cluster_server_parameter_refresher.cpp#L289 where the SharedLock acquisition in https://github.com/mongodb/mongo/blob/7060765f3e0d33b74b2f6c7764fb3e88ece3b805/src/mongo/db/query/query_settings_manager.cpp#L167 threw because the server shutdown sequence was started and that causes all OperationContexts to report as being interrupted https://github.com/mongodb/mongo/blob/7060765f3e0d33b74b2f6c7764fb3e88ece3b805/src/mongo/db/operation_context.cpp#L244-L247"

       

      Creating this ticket to follow up on issue.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            adi.zaimi@mongodb.com Adi Zaimi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: