Partition data for deleted topic found in kafka-logs, also, found leader: -1

, Yogesh Sangvikar

Re: Partition data for deleted topic found in kafka-logs, also, found leader: -1

Hi Team, Could you please help to understand those features? Thanks, Yogesh Sangvikar On Tue, Jun 18, 2013 at 6:55 PM, Yogesh Sangvikar < yogesh.sangvi...@gmail.com> wrote: > Hi Team, > > I am exploring kafka 0.8 beta release to understand data flow, replication > features.

Questions on kafka leader selection

s? Thanks, Yogesh Sangvikar

Re: Questions on kafka leader selection

goes down but the controller active? As this helps to make high data availability. Thanks, Yogesh Sangvikar On Wed, Jun 19, 2013 at 8:53 PM, Jun Rao wrote: > If leader is -1, that indicates the partition is unavailable. Were replicas > 4,2,3 all down at that time? If so, you need to st

kafka.common.FailedToSendMessageException: Failed to send messages after 3 tries.

Hi Team, We are using kafka-0.8.0-beta1-candidate1 release. ( https://github.com/apache/kafka/tree/0.8.0-beta1-candidate1). While running producer with following configuration, we found an issue "kafka.common. FailedToSendMessageException: Failed to send messages after 3 tries", We are using def

Re: kafka.common.FailedToSendMessageException: Failed to send messages after 3 tries.

com.pearson.firehose.KafkaProducer.main(KafkaProducer.java:44) Please let me know if you need the complete producer code. Thanks, Yogesh Sangvikar On Tue, Jun 25, 2013 at 10:05 AM, Jun Rao wrote: > Could you attach the log before FailedToSendMessageException in the > producer? It should tell y

Re: kafka.common.FailedToSendMessageException: Failed to send messages after 3 tries.

uot;, "async");". I suppose, the producer.type=sync is working wrongly in release kafka-0.8.0-beta1-candidate1. Team please have a look on this. If my understanding is wrong please help to correct. Thanks, Yogesh Sangvikar On Tue, Jun 25, 2013 at 4:38 PM, Jonathan Hodges wrote: &

Re: kafka.common.FailedToSendMessageException: Failed to send messages after 3 tries.

t; Jonathan > >> > >> > >> > >> On Tue, Jun 25, 2013 at 1:12 AM, Florin Trofin > >>wrote: > >> > >>> I got the same error but I think I had a different issue than you: My > >>>code > >>&

Fwd: Data loss while upgrading confluent 3.0.0 kafka cluster to confluent 3.2.2

Hi Team, Please help to find resolution for below kafka rolling upgrade issue. Thanks, Yogesh On Monday, September 18, 2017 at 9:03:04 PM UTC+5:30, Yogesh Sangvikar wrote: > > Hi Team, > > Currently, we are using confluent 3.0.0 kafka cluster in our production > environme

Re: Data loss while upgrading confluent 3.0.0 kafka cluster to confluent 3.2.2

ing a protocol version bump? > > > > > > > > On Mon, Sep 18, 2017 at 9:33 AM Ismael Juma wrote: > > > > > Hi Yogesh, > > > > > > Can you please clarify what you mean by "observing data loss"? > > > > > > Ismael > &

Re: Data loss while upgrading confluent 3.0.0 kafka cluster to confluent 3.2.2

; 3. When doing a rolling restart, it's generally a good idea to ensure that > there are no under-replicated partitions. > 4. Is controlled shutdown completing successfully? > > Ismael > > On Tue, Sep 19, 2017 at 12:33 PM, Yogesh Sangvikar < > yogesh.sangvi...@gmai

Re: Data loss while upgrading confluent 3.0.0 kafka cluster toconfluent 3.2.2

=3 (default, 0) *for kafka rest producer config (kafka-rest.properties) and getting some duplicate events in topic. Thanks, Yogesh On Thu, Sep 21, 2017 at 7:09 AM, yogesh sangvikar < yogesh.sangvi...@gmail.com> wrote: > Thanks Ismael. > I will try the solution and update all. >