One clarification below:
On Wed, Sep 20, 2017 at 3:50 PM, Ismael Juma wrote:
> Comments inline.
>
> On Wed, Sep 20, 2017 at 11:56 AM, Yogesh Sangvikar <
> yogesh.sangvi...@gmail.com> wrote:
>
>> 2. At which point in the sequence below was the code for the brokers
>> updated to 0.10.2?
>>
>> [Com
Comments inline.
On Wed, Sep 20, 2017 at 11:56 AM, Yogesh Sangvikar <
yogesh.sangvi...@gmail.com> wrote:
> 2. At which point in the sequence below was the code for the brokers
> updated to 0.10.2?
>
> [Comment: On the kafka servers, we have confluent-3.0.0 and confluent-3.2.2
> packages deployed
Hi Ismael,
A few questions:
1. Please share the code for the test script.
[Comment: We are publishing events using kafka-rest
*POST: /topics/* API. And, using Jmeter script to call the API
to publish events continuously for 2 hrs. The "key" value for the event is
constant so that, we can ch
Hi Yogesh,
A few questions:
1. Please share the code for the test script.
2. At which point in the sequence below was the code for the brokers
updated to 0.10.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 s
t: Re: Data loss while upgrading confluent
3.0.0 kafka cluster to confluent 3.2.2
Hi Team,
Thanks for providing comments.
Here adding more details on steps followed for upgrade,
Cluster details: We are using 4 node kafka cluster and topics with 3
replication factor. For upgrade test, we are using a
Hi Team,
Thanks for providing comments.
Here adding more details on steps followed for upgrade,
Cluster details: We are using 4 node kafka cluster and topics with 3
replication factor. For upgrade test, we are using a topic with 5
partitions & 3 replication factor.
Topic:student-activity Parti
Hi Scott,
There is nothing preventing a replica running a newer version from being in
sync as long as the instructions are followed (i.e.
inter.broker.protocol.version has to be set correctly and, if there's a
message format change, log.message.format.version). That's why I asked
Yogesh for more d
Can we get some clarity on this point:
>older version leader is not allowing newer version replicas to be in sync,
so the data pushed using this older version leader
That is super scary.
What protocol version is the older version leader running?
Would this happen if you are skipping a protocol v
Hi Yogesh,
Can you please clarify what you mean by "observing data loss"?
Ismael
On Mon, Sep 18, 2017 at 5:08 PM, Yogesh Sangvikar <
yogesh.sangvi...@gmail.com> wrote:
> Hi Team,
>
> Please help to find resolution for below kafka rolling upgrade issue.
>
> Thanks,
>
> Yogesh
>
> On Monday, Sept
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
> environment. And, we are plani
10 matches
Mail list logo
