Sync recovery after short-term communication problems

[andrey-chorniy]

Hi Richard,

We have an issue similar to the #342. However, in our case it was a short term downtime - mongo server was restarted and just a few records were inserted during that time. After Mongo server was up and running again ES river did not resume syncing with mongo and we had to restart ES in order to resume syncing.

Is there any way to auto recover from such situations when Mongo server becomes temporarily unavailable (assuming that during that all non-synced records will still be in the OP-Log) ? In other words, can ES mongo-river periodically keep on trying to connect to mongo after connection failures? If not, is there any way to be notified about such problems?

[2015-01-30 02:24:28,499][WARN ][org.elasticsearch.river.mongodb.Slurper] Exception while looping in cursor
com.mongodb.MongoException$Network: Read operation to server mongoserver.int.com/10.69.71.87:27017 failed on database local
        at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:253)
        at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:264)
        at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:264)
        at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:216)
        at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:184)
        at com.mongodb.DBApiLayer$Result._advance(DBApiLayer.java:427)
        at com.mongodb.DBApiLayer$Result.hasNext(DBApiLayer.java:396)
        at com.mongodb.DBCursor._hasNext(DBCursor.java:464)
        at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
        at org.elasticsearch.river.mongodb.Slurper.run(Slurper.java:123)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.NoRouteToHostException: No route to host