Hi there,
Resending as probably missed earlier to grab your attention.
Regards,
Umesh
-- Forwarded message -
From: UMESH CHAUDHARY
Date: Mon, 3 Jul 2017 at 11:04
Subject: [DISCUSS] KIP-174 - Deprecate and remove internal converter
configs in WorkerConfig
To: d
; migrate to newer versions which would no longer support that?
>
> -Ewen
>
>
> On Fri, Jul 14, 2017 at 2:37 AM, UMESH CHAUDHARY
> wrote:
>
> > Hi there,
> > Resending as probably missed earlier to grab your attention.
> >
> > Regards,
> > Umesh
&g
Hi Ewen,
Sorry, I am bit late in responding this.
Thanks for your inputs and I've updated the KIP by adding more details to
it.
Regards,
Umesh
On Mon, 31 Jul 2017 at 21:51 Ewen Cheslack-Postava
wrote:
> On Sun, Jul 30, 2017 at 10:21 PM, UMESH CHAUDHARY
> wrote:
>
>> Hi
uot;
> and "since the JsonConverter is the default, the configs will be removed
> immediately from the example worker configuration files").
>
> Other than that this LGTM and I'll be happy to get rid of those settings!
>
> -Ewen
>
> On Tue, Aug 8, 2017 at 2:54 AM
Are you seeing any errors in consumer when your broker gets down? May be
any debug messages would be helpful. After killing the broker do you
notice any leadership change for those topic's partitions using
[kafka-topics.sh --zookeepr <> --describe] ?
On Fri, 11 Aug 2017 at 06:23 Rakesh Singh
wro
Erik Kringen, Erkan Unal, Evgeny
> Veretennikov,
> > Ewen Cheslack-Postava, Florian Hussonnois, Janek P, Gregor Uhlenheuer,
> > Guozhang Wang, Gwen Shapira, Hamidreza Afzali, Hao Chen, Jiefang He,
> Holden
> > Karau, Hooman Broujerdi, Hugo Louro, Ismael Juma, Jacek Laskowski, J
Congratulations Onur!
On Tue, 7 Nov 2017 at 21:44 Jun Rao wrote:
> Affan,
>
> All known problems in the controller are described in the doc linked from
> https://issues.apache.org/jira/browse/KAFKA-5027.
>
> Thanks,
>
> Jun
>
> On Mon, Nov 6, 2017 at 11:00 PM, Affan Syed wrote:
>
> > Congrats O
Do you find any messages on broker 3 w.r.t. Topic: XYZ Partition 82? Also
broker 3 is in isr for other partitions (at least 83,84) so I don't see any
broker issue in this.
On Thu, 14 Dec 2017 at 01:23 Tarun Garg wrote:
> Hi,
>
> I have a Kafka cluster and it is running from a long time, just tod
deprecation commit through. It seems like
> a good idea as this has been confusing to users from day one.
>
> -Ewen
>
> On Wed, Aug 9, 2017 at 5:18 AM, UMESH CHAUDHARY
> wrote:
>
>> Thanks Ewen,
>> I just edited the KIP to reflect the changes.
>>
>> Regards,
Congratulations Rajini !
On Fri, 19 Jan 2018 at 07:11 Jun Rao wrote:
> Congratulations, Rajini !
>
> Jun
>
> On Wed, Jan 17, 2018 at 10:48 AM, Gwen Shapira wrote:
>
> > Dear Kafka Developers, Users and Fans,
> >
> > Rajini Sivaram became a committer in April 2017. Since then, she
> remained
>
You might want to set group.id config in kafka-console-consumer (or in any
other consumer) to the value which you haven't used before. This will
replay all available messages in the topic from start if you use
--from-beginning in console consumer.
On Wed, 28 Feb 2018 at 14:19 Zoran wrote:
> Hi,
Hi Folks,
Was searching for some command to list all connected(live) producers to
Kafka brokers.
Is there any such tool to get the live producers and consumers?
Regards,
Umesh
Hey Folks,
I was trying to understand the behavior of MirrorMaker but looks like I am
missing something here. Please see the steps which I performed :
1) I configured MM on source Kafka cluster
2) Created a topic and pushed some data in it using console producer.
3) My understanding is that MM wou
time of its startup and mirrors the data. When you add some new topics
after its startup it doesn't pick it automatically?
Regards,
Umesh Chaudhary
On Thu, 25 Aug 2016 at 19:23 cs user wrote:
> Hi Umesh,
>
> I am new to kafka as well, and configuring the MirrorMaker. I got mine
&g
is hang MM was not able to
replicate other topics.
When I deleted that zombie topic, MM worked as expected.
Regards,
Umesh Chaudhary
On Fri, 26 Aug 2016 at 12:40 cs user wrote:
> Hi Umesh,
>
> I haven't had that problem, it seems to work fine for me. The only issue I
> found, wh
No that is not required, when you use new consumer API. You have to
specify bootstrap.servers,
which will have 9092 (for PLAINTEXT usually ).
In old consumer API you need zookeeper server which points on 2181.
On Thu, 15 Sep 2016 at 17:03 kant kodali wrote:
> I haven't changed anything from
> ht
Did you test that kafka console consumer is displaying the produced
message?
On Fri, Jan 6, 2017 at 9:18 AM, Gupta, Swati wrote:
> Hello All,
>
>
>
> I am trying to create a Consumer using Apache Camel for a topic in Apache
> Kafka.
> I am using Camel 2.17.0 and Kafka 0.10 and JDK 1.8.
> I have
17 matches
Mail list logo
