Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Process is not killing itself on fatal error (docker)
See original GitHub issueI am using docker (via OpenShift) with Mongo Connector and elastic2-doc-manager in their latest versions.
Everything is ok until I am getting for any reason ReadTimeoutError because one of the requests to the Elastic took more than 10sec.
In this case, the mongo-connector should send a SIGNAL to kill itself, It will help the Docker restart automatically (recover) and try to continue from the last oplog entry.
In my case, I noticed that the connector was “stuck” in this error for about 20 hours, And when I restarted it manually the connector failed to trace in time the changes happened in the MongoDB (there are about 20,000 updated per hour).
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Mapping the error to
OperationFailedwould cause mongo-connector to ignore the error and not exit. The real issue is that the elastic doc manager does not handle timeouts on its Elasticsearch client. That error should currently be uncaught and mongo-connector should exit. It should not be “stuck”. Can you post the ReadTimeoutError error message or stacktrace that you’re seeing?Have there been any updates on this? I’m still seeing this issue!