Hello Kafka experts,
We are running Kafka on AWS, main question is what is the best way to
retain broker.id on new instance spun-up in-place of instance/broker failed.
We are currently running Kafka in AWS with broker.id gets auto generated.
But we are having issues when a broker is failed, new b
s any other/better way to
re-assingn/retain/impersonate the old broker.id.
Thanks and Regards,
Srinivas
On Wed, Nov 14, 2018 at 11:48 AM naresh Goud
wrote:
> Static IP. Buying static IP may help. I am not aws expert
>
> On Wed, Nov 14, 2018 at 12:47 PM Srinivas Rapolu
> wrote:
naresh Goud
> wrote:
>
> > Static IP. Buying static IP may help. I am not aws expert
> >
> > On Wed, Nov 14, 2018 at 12:47 PM Srinivas Rapolu
> > wrote:
> >
> > > Hello Kafka experts,
> > >
> > > We are running Kafka on AWS, main ques
d broker IDs and keep that in a
> table persisted somewhere (e.g., DynamoDB).
>
> Eno
>
> On Wed, Nov 14, 2018 at 7:38 PM Srinivas Rapolu
> wrote:
>
> > EBS is one of the option. But we use instance level storage where we
> loose
> > all data as soon as we have
t; > help re-spin/start the unhealthy instance with same instance id.
> >
> > On Thu, Nov 15, 2018 at 6:08 PM Srinivas Rapolu
> > wrote:
> >
> > > having all this stored in DB is getting too complicated, especially
> with
> > > instance level storage and not
ov 16, 2018 at 10:53 AM Ryanne Dolan
> wrote:
>
> > > if we are not using EBS
> >
> > In that case, what's the point of keeping the broker id? The data will be
> > lost anyway right?
> >
> >
> > On Thu, Nov 15, 2018, 11:40 AM Srinivas Rap
By looking at the responses: It looks like there is *NO *standard
solution, we will have to come up with some custom/manual script. any
one has any other suggestions?
On Fri, Nov 16, 2018 at 11:18 AM Srinivas Rapolu wrote:
> Yes, that is the whole point of discussion, replication factor
