-
Type: Question
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.0
-
Component/s: Logging, WiredTiger
-
None
Dear Team,
A critical issues observed at our side.
MongoTimeoutException is occurring even when DB is running!!
we observed that MOngoServer didnt receive any metadata from the client-172.29.105.17.
Note: Both Client and MOngoServer are running on same Machine
Detailed Scenario is described below
As observed from the MongoDB logs
on 1st may 2018
2018-05-01T16:26:25.089-0400 I STORAGE [initandlisten] Service running
2018-05-01T16:26:25.089-0400 I NETWORK [thread1] waiting for connections on port 8090
{{2018-05-01T16:26:29.642-0400 I NETWORK [conn1] received client metadata from 172.29.105.17:64758 conn1: { driver:Unknown macro: { name}, os: { type: "Windows", name: "Windows Server 2012 R2", architecture: "x86", version: "6.3" }, platform: "Java/Oracle Corporation/1.8.0_144-b01" }}}
{{2018-05-01T16:26:29.854-0400 I NETWORK [conn2] received client metadata from 172.29.105.17:64759 conn2: { driver:Unknown macro: { name}, os: { type: "Windows", name: "Windows Server 2012 R2", architecture: "x86", version: "6.3" }, platform: "Java/Oracle Corporation/1.8.0_144-b01" }}}
on 12th may 2018
2018-05-12T17:24:33.148-0400 I CONTROL [main] Trying to start Windows service 'SRDMDbServer8090'
2018-05-12T17:24:33.224-0400 I CONTROL [initandlisten] MongoDB starting : pid=1404 port=8090 dbpath=C:\SRDM\SRDM2.5.0.11308.17\SRDM\Svr\DBService\bin64\..\data\db 64-bit host=WIN-OHPM52MOHG1
2018-05-12T17:24:45.446-0400 I STORAGE [initandlisten] Service running
2018-05-12T17:24:45.464-0400 I NETWORK [thread1] waiting for connections on port 8090
So, between 1st may 2018 & 12th may 2018 the difference we observed was server did'nt receive metadata from client .
hence when CLient initiate any DB Operations MOngoDB Timeout exceptions is occured with
com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Client view of cluster state is {type=UNKNOWN, servers=[{address=172.29.105.17:8090, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by \{java.net.SocketException: Network is unreachable: connect}}]
Please let us know Why DB Operations is not successful in above said scenario??
Thanks & Regards
Sandeep KS
- is related to
-
SERVER-29109 Client metadata log message verbosity is not parallel with connection start/end messages
- Closed