Hi Ning,
I mean by "when there are some messages left in the original cluster",
when the consumer switches from the original cluster to the new
cluster before entirely consuming the messages at the original
cluster.
This commit illustrates this situation.
https://github.com/elakito/kafka/commit/906
Hey,
*Without any code change*, just by bumping the kafka version from 2.5.1 to
2.6.1 (clients only) - my stream application started throwing
NullPointerException (sometimes, not in a predicted pattern).
Maybe it's worth mentioning that I also removed the "UPGRADE_FROM" conf
that was forgotten ther
hello Aki,
I guess overall you are right.
When the consumer have not finish consuming the latest message from primary and
switch to the backup, the left messages will be still replicated from primary
to backup by MM, so your consumer will still be able to consume the left
messages at backup,
