DR issues?
>
> Thank you for your time
>
> Henning Røigaard-Petersen
>
> -Original Message-
> From: Ryanne Dolan
> Sent: 3. september 2018 20:27
> To: users@kafka.apache.org
> Subject: Re: Official Kafka Disaster Recovery is insufficient - Suggestions
> need
ue to the DR issues?
>
> Thank you for your time
>
> Henning Røigaard-Petersen
>
> -Original Message-
> From: Ryanne Dolan
> Sent: 3. september 2018 20:27
> To: users@kafka.apache.org
> Subject: Re: Official Kafka Disaster Recovery is insufficient -
>
Dolan
Sent: 3. september 2018 20:27
To: users@kafka.apache.org
Subject: Re: Official Kafka Disaster Recovery is insufficient - Suggestions
needed
Sorry to have misspelled your name Henning.
On Mon, Sep 3, 2018, 1:26 PM Ryanne Dolan wrote:
> Hanning,
>
> In mission-critical (and in
Sorry to have misspelled your name Henning.
On Mon, Sep 3, 2018, 1:26 PM Ryanne Dolan wrote:
> Hanning,
>
> In mission-critical (and indeed GDPR-related) applications, I've ETL'd
> Kafka to a secondary store e.g. HDFS, and built tooling around recovering
> state back into Kafka. I've had
Hanning,
In mission-critical (and indeed GDPR-related) applications, I've ETL'd
Kafka to a secondary store e.g. HDFS, and built tooling around recovering
state back into Kafka. I've had situations where data is accidentally or
incorrectly ingested into Kafka, causing downstream systems to process
I am looking for advice on how to handle disasters not covered by the official
methods of replication, whether intra-cluster replication (via replication
factor and producer acks) or multi-cluster replication (using Confluent
Replicator).
We are looking into using Kafka not only as a broker
