alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-848 Removed explicit primary node change handling. It is handled by mongoDb driver internally. Explicit primary node change event handling was causing issue that no mongo events were read after primary change. This issue only happened when rs.stepDown(<time s>) was used on mongo node.

Browse Source
This commit is contained in:
Tautvydas Januskevicius 2018-11-23 16:42:15 +02:00 committed by Gunnar Morling
parent 470cd1eaba
commit addf13ca06
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
debezium-connector-mongodb/src/main/java/io/debezium/connector/mongodb/Replicator.java
View File

@ -452,10 +452,9 @@ protected boolean handleOplogEvent(ServerAddress primaryAddress, Document event)
ServerAddress serverAddress = address.get();
if (serverAddress != null && !serverAddress.equals(primaryAddress)) {
logger.info("Found new primary event in oplog, so stopping use of {} to continue with new primary",
primaryAddress);
// There is a new primary, so stop using this server and instead use the new primary ...
return false;
//primary switch will be handled automatically by mongo driver.
logger.info("Found new primary event in oplog, so stopping use of {} to continue with new primary {}",
primaryAddress, serverAddress);
} else {
logger.info("Found new primary event in oplog, current {} is new primary. " +
"Continue to process oplog event.", primaryAddress);