-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.3
-
Component/s: Replication
-
Environment:Thu Jun 06 13:21:10.788 [initandlisten] MongoDB starting : pid=7356 port=27017 dbpath=e:\mongodb_rssc01\data\db 64-bit host=LOG-MNGSC21
Thu Jun 06 13:21:10.788 [initandlisten] db version v2.4.3
Thu Jun 06 13:21:10.788 [initandlisten] git version: fe1743177a5ea03e91e0052fb5e2cb2945f6d95f
Thu Jun 06 13:21:10.788 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49
Thu Jun 06 13:21:10.788 [initandlisten] MongoDB starting : pid=7356 port=27017 dbpath=e:\mongodb_rssc01\data\db 64-bit host=LOG-MNGSC21 Thu Jun 06 13:21:10.788 [initandlisten] db version v2.4.3 Thu Jun 06 13:21:10.788 [initandlisten] git version: fe1743177a5ea03e91e0052fb5e2cb2945f6d95f Thu Jun 06 13:21:10.788 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49
-
Windows
We have a environment with 2 nodes and 1 arbiter with the following configuration:
{
"_id" : "rssc01",
"version" : 3,
"members" : [
,
,
{ "_id" : 2, "host" : "log-mngsc22:27018", "arbiterOnly" : true } ]
}
LOG-MNGSC11 is the primary and LOG-MNGSC21 is the secondary.
Suddenly, the replication fails with the following message on secondary:
Thu Jun 06 11:56:50.656 [rsHealthPoll] replset info LOG-MNGSC11:27017 thinks that we are down
Thu Jun 06 11:56:52.310 [rsHealthPoll] replset info log-mngsc22:27018 thinks that we are down
Thu Jun 06 11:56:52.481 [conn12160] command admin.$cmd command:
ntoreturn:1 keyUpdates:0 reslen:44 300005ms
Thu Jun 06 11:56:52.668 [rsHealthPoll] replset info LOG-MNGSC11:27017 thinks that we are down
Thu Jun 06 11:56:52.793 [rsBackgroundSync] Socket recv() timeout 172.29.106.92:27017
Thu Jun 06 11:56:52.793 [rsBackgroundSync] SocketException: remote: 172.29.106.92:27017 error: 9001 socket exception [3] server [172.29.106.92:27017]
Thu Jun 06 11:56:52.793 [rsBackgroundSync] DBClientCursor::init call() failed
At primary, I see the following messages:
Thu Jun 06 11:56:52.524 [initandlisten] connection accepted from 172.29.106.95:56714 #16239 (66 connections now open)
Thu Jun 06 11:56:55.847 [rsHealthPoll] DBClientCursor::init call() failed
Thu Jun 06 11:56:57.329 [conn16236] query local.oplog.rs query: { ts:
} cursorid:479480611067557781 ntoreturn:0 ntoskip:0 nscanned:102 keyUpdates:0 numYields: 2264 locks(micros) r:727945 nreturned:101 reslen:12039 35319ms
Thu Jun 06 11:56:57.329 [conn16236] end connection 172.29.106.95:56704 (65 connections now open)
- depends on
-
SERVER-13681 MongoDB stalls during background flush on Windows
- Closed
-
SERVER-13725 Reads & Writes are blocked during Memory Map File Remap on win/solaris
- Closed
-
SERVER-13729 Reads & Writes are blocked during data file allocation on Windows
- Closed
- is related to
-
SERVER-12880 Server pauses on requests every 60 seconds
- Closed
-
SERVER-13444 Long locked flush without inserts and updates
- Closed