-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Hi,
I create a mongo Client for db operations like
cli.Database("database").Collection("table").FindOneAndUpdate(xxxxx)
It works as expected.
However, after some days, the operations fails with errors like these:
connection(gd07v.tq.bjzt.qianxin-inc.cn:27017[-4788]) incomplete read of message header: read tcp 172.17.0.103:35266->10.47.88.7:27017: i/o timeout
auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-256": context deadline exceeded
context deadline exceeded
connection() : dial tcp: i/o timeout
connection() : dial tcp: i/o timeout
connection() : dial tcp: i/o timeout
sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-256": context deadline exceeded
context deadline exceeded
context deadline exceeded
incomplete read of message header: read tcp 172.17.0.103:35408->10.47.88.7:27017: i/o timeout
auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-256": context deadline exceeded
auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-256": context deadline exceeded
connection() : dial tcp: i/o timeout
auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-256": context deadline exceeded
connection() : dial tcp: i/o timeout
Ok, maybe some network problem occurs, but what I expected is it should return back to normal after the problem disappears.
While, in fact, after the last error message has been reported, the next operation will block and never return. Even I add a context.WithTimeout context for the operation.
It keeps blocked even the network has been restored.
How can I recovery from this blocking.
1.
|
mongo client has i/o timeout after network exception | GODRIVER-1814 | Closed | Unassigned |