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

SocketException: remote: 10.200.66.92:27019 error: 9001 socket exception

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.12
    • Component/s: None
    • None
    • ALL
    • Hide

      we restart the config server will solve this problem, and when this time in de config server will have close_time tcp connect , and in the mongos will have FIN_WAIT2 status.

      Show
      we restart the config server will solve this problem, and when this time in de config server will have close_time tcp connect , and in the mongos will have FIN_WAIT2 status.

      Nov 17 16:21:43 [LockPinger] DBClientCursor::init call() failed
      Nov 17 16:21:43 [LockPinger] scoped connection to 10.200.67.92:27019,10.200.65.92:27019,10.200.66.92:27019 not being returned to the pool
      Nov 17 16:21:43 [LockPinger] distributed lock pinger '10.200.67.92:27019,10.200.65.92:27019,10.200.66.92:27019/g37-gs09-10021.i.nease.net:30000:1507709978:1804289383' detected an exception while pinging. :: caused by :: SyncClusterConnection write op failed: 10.200.66.92:27019 (10.200.66.92) failed: {} DBClientBase::findN: transport error: 10.200.66.92:27019 ns: admin.$cmd query: { getlasterror: 1, fsync: 1 }
      Nov 17 16:22:02 Socket recv() timeout  10.200.66.92:27019
      Nov 17 16:22:02 SocketException: remote: 10.200.66.92:27019 error: 9001 socket exception [RECV_TIMEOUT] server [10.200.66.92:27019]
      Nov 17 16:22:02 DBClientCursor::init call() failed
      Nov 17 16:22:02  couldn't check dbhash on config server 10.200.66.92:27019 :: caused by :: 10276 DBClientBase::findN: transport error: 10.200.66.92:27019 ns: config.$cmd query: { dbhash: 1, collections: [ "chunks", "databases", "collections", "shards", "version" ] }
      Nov 17 16:22:18 [UserCacheInvalidator] SyncClusterConnection connecting to [10.200.67.92:27019]
      Nov 17 16:22:18 [UserCacheInvalidator] SyncClusterConnection connecting to [10.200.65.92:27019]
      Nov 17 16:22:18 [UserCacheInvalidator] SyncClusterConnection connecting to [10.200.66.92:27019]
      Nov 17 16:22:45 [LockPinger] Socket recv() timeout  10.200.66.92:27019
      Nov 17 16:22:45 [LockPinger] SocketException: remote: 10.200.66.92:27019 error: 9001 socket exception [RECV_TIMEOUT] server [10.200.66.92:27019]
      Nov 17 16:22:45 [LockPinger] DBClientCursor::init call() failed
      Nov 17 16:22:45 [LockPinger] scoped connection to 10.200.67.92:27019,10.200.65.92:27019,10.200.66.92:27019 not being returned to the pool
      Nov 17 16:22:45 [LockPinger] distributed lock pinger '10.200.67.92:27019,10.200.65.92:27019,10.200.66.92:27019/g37-gs09-10021.i.nease.net:30000:1507709978:1804289383' detected an exception while pinging. :: caused by :: SyncClusterConnection write op failed: 10.200.66.92:27019 (10.200.66.92) failed: {} DBClientBase::findN: transport error: 10.200.66.92:27019 ns: admin.$cmd query: { getlasterror: 1, fsync: 1 }
      

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            zhouhancang hancang2000
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: