I’m running a replication test with two realtime nodes that are setup with the same spec file for replication. I don’t use tranquility or kafka but use the receiver firehose and update the data via post requests to the individual realtime nodes.
In my test the broker seems to have favoured realtime node1 for querying. When i shut down node1 the broker used node2 from there on - all good. But when node1 came back online it used node1 again for queries - even if we had data updates in the meantime that made it to the segments in node2.
Is it possible to mark the segments of node1 as dirty if the node goes down for a while so the broker would pick up the more accurate node2 in this example and only uses node1 again if node2 would disappear as well?