Problem code:
catch ( std::exception& e ) { if ( inShutdown() ) { // we're shutting down, so just clean up return; } log() << "WriteBackListener exception : " << e.what() << endl; // It's possible this shard was removed Shard::reloadShardInfo(); }
Note that reloadShardInfo can also throw exceptions and since it is not handled in the run method, the writeback listener thread would just terminate. Sample scenarios that reloadShardInfo can throw is when config servers are unreachable.
- is depended on by
-
SERVER-9323 client session locks up when mongos socket goes into state warning: waiting for writeback 5166929d0000000000000492 from connection
- Closed