Sometimes (it happened to us two or more times) getObjectIdFromOplogEntry throws the exceptions, which leads to river failure. I'm not sure it is a good idea to catch any exception here. But I believe such cases must not affect the indexing service availability.
Sometimes (it happened to us two or more times)
getObjectIdFromOplogEntrythrows the exceptions, which leads to river failure. I'm not sure it is a good idea to catch any exception here. But I believe such cases must not affect the indexing service availability.