On 16/12/16 16:30, Emmanuel Bernard wrote:
The Emmanuel Dec 9th proposal handles I think the case of topology
changes and nodes going down.
We need a better name :)
For a cluster-wide shutdown with no time to flush queues, I think
both Artemis and the local debezium talking to remote Kafka will be in trouble.
The main difference is I imagine that your Artemis log will be local to the node being
shut down. But that would mean a complex system to restart with the unflushed queue from
all node that were shut down. Are we there yet?
I'm specifically thinking about when the Debezium embedded in Infinispan
cannot talk to Kafka for whatever reason, and the user wants to shutdown.
Tristan
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat