You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This also affects the dispatcher when writing logs for the items
time="2018-08-01T14:04:11Z" level=error msg="failed to store logs for job in metastore" endTime="2018-08-01T14:03:59.316864Z" error="error creates document: EOF" message="failed to store logs for job in metastore" messageID=59179d5fba354a21b68d3ea71212571b startTime="2018-08-01T14:03:20.16158Z" taskDurationSec=0x107ed30 taskID=0xc4201ed890 taskName=0xc4201ed8a0 taskNodeID=0xc4201edbe0 taskPoolID=0xc4201edbd0
time="2018-08-01T14:04:11Z" level=error msg="failed to log to logstore" endTime="2018-08-01T14:03:59.316864Z" error="error creates document: EOF" message="failed to log to logstore" messageID=59179d5fba354a21b68d3ea71212571b startTime="2018-08-01T14:03:20.16158Z" taskDurationSec=0x107ed30 taskID=0xc4201ed890 taskName=0xc4201ed8a0 taskNodeID=0xc4201edbe0 taskPoolID=0xc4201edbd0
One solution would be to panic either component when this occurs, another would be to investigate if mgo_v2 support some kind of automated recovery from a lost connection
Mgo looks like it doesn't automatically recover from a dropped mongo connection, this affects the front API.
The text was updated successfully, but these errors were encountered: