Hi Ryanne,
> I frequently demo this stuff, where I pull the plug on entire DCs and
apps keep running like nothing happened.
Is there any public recording, documentation about these demos?
I would be very useful to see how it works.
Thanks,
Peter
On Thu, 13 Feb 2020 at 00:42, Ryanne Dolan
Thanks Ryanne.
However what I dont understand clearly if the case of primary crashes, what
do I need to do in the secondary? For example, LB at the entrance will
just point to the primary front-end so all the data will be injected in the
local topic "topic1" in secondary that will be consumed
Hi,
I knew about uReplicator but I discarded because it uses Helix. Anyway, I
will have a look to the talk
Thanks very much
On Wed, Feb 12, 2020 at 9:59 PM Brian Sang wrote:
> Not sure if you saw this before, but you might be interested in some of the
> work Uber has done for inter-cluster
> elaborate a bit more about the active-active
Active/active in this context just means that both (or multiple)
clusters are used under normal operation, not just during an outage.
For this to work, you basically have isolated instances of your application
stack running in each DC, with MM2
Not sure if you saw this before, but you might be interested in some of the
work Uber has done for inter-cluster replication and federation. They of
course use their own tool, uReplicator (https://github.com/uber/uReplicator),
instead of mirror maker, but you should be able to draw the same
Hi Ryanne,
Please could you elaborate a bit more about the active-active
recommendation?
Thanks in advance
On Mon, Feb 10, 2020 at 10:21 PM benitocm wrote:
> Thanks very much for the response.
>
> Please could you elaborate a bit more about "I'd
> arc in that direction. Instead of migrating
Thanks very much for the response.
Please could you elaborate a bit more about "I'd
arc in that direction. Instead of migrating A->B->C->D..., active/active is
more like having one big cluster".
Another thing that I would like to share is that currently my consumers
only consumer from one topic
Hello, sounds like you have this all figured out actually. A couple notes:
> For now, we just need to handle DR requirements, i.e., we would not need
active-active
If your infrastructure is sufficiently advanced, active/active can be a lot
easier to manage than active/standby. If you are
Hi,
After having a look to the talk
https://www.confluent.io/kafka-summit-lon19/disaster-recovery-with-mirrormaker-2-0
and the
https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0#KIP-382
I am trying to understand how I would use it
in the setup that I have. For now, we
