Look like this is bug ..
You can clean the data log on this node 3 and start the kafka process on node
3 . This should resolve the issue
On 9/15/20, 8:09 PM, "Dima Brodsky" wrote:
[External]
We are using version 2.3.1.
Two more pieces are information wrt Luke's answer. Assume
We are using version 2.3.1.
Two more pieces are information wrt Luke's answer. Assume that retention
of the data is Y and you turn on the node 3 after time Y so the data on
node 3 is old and would be deleted regardless, so there is no point in
doing another partition reassignment because the dat
It should delete the old data log based on retention of topic.
What kafka version you are using ?
On 9/15/20, 7:48 PM, "Dima Brodsky" wrote:
[External]
Hi,
I have a question, when you start kafka on a node, if there is a random
replica log should it delete it on startup? Her
Hi Dima,
They'll stick around. I think the point is that when node 3 is back, you
should do partition reassignment so that the pre-existed partition/replica
data can be reused.
But for your question, the unused log won't delete is a bug or as
designed... I think it is working as designed and it sh
Hi Shaohan,
Thanks for your inputs. I did look at request total time and request queue
time metrics and it looks to be normal. The broker was restarted a couple
times and I saw some spikes during that time alone. The kafka broker logs
don't have any errors at all. The issue started around 11:30 an
Hi,
I have a question, when you start kafka on a node, if there is a random
replica log should it delete it on startup? Here is an example: Assume
you have a 4 node cluster. Topic X has 3 replicas and it is replicated on
nodes 1, 2, and 3. Now you shutdown node 3 and you place the replica tha
You could check if there are any performance issues on the broker.
Broker metrics such as kafka_network_requestmetrics_totaltimems and
kafka_network_requestmetrics_requestqueuetimems might do you a favor.
And your acks config would also affect the e2e latency
On Wed, 16 Sep 2020 at 05:08, Navnee
Sorry that I forgot to attach my Jira id.
My ID is Shawn Yin
Cheers
On Tue, 15 Sep 2020 at 22:20, Bill Bejeck wrote:
> Hi,
>
> Can you share your Jira user-id so we can sign you up?
>
> Thanks,
> Bill
>
> On Tue, Sep 15, 2020 at 1:55 AM Shaohan Yin wrote:
>
> > Hi,
> >
> > I am interested in
Hi Ryanne/Josh,
I'm working on active-active mirror maker and while translating consumer
offset from source- cluster A to dest cluster B. any pointer would be helpful .
Cluster A
Cluster Name--A
Topic name: testA
Consumer group name: mm-testA-consumer
Cluster -B
Cluster Name--B
Topic name: sou
Hello Samuel,
I tried other consumer config and it worked. Basically, it should follow the
pattern `source-cluster-alias.consumer.`. In your case, I
think it should be `source-cluster-alias.consumer.auto.offset.reset`. But feel
free to try other consumer config and see if they work
On 2020/09/
Hi All,
We are running kafka in production with 20 brokers and version 2.3.1. I see
the below errors frequently happening and here is the producer
configuration. Need some urgent help on what could be done to resolve this
issue.
batch.size: 65536
linger.ms: 100
request.timeout.ms: 6
org.apac
I tried this but even the override does not work for me as I can still see
"earliest" on the ConsumerConfig properties. Did you manage actually to
make this work or are you just recommending this config?
Best,
On Mon, Sep 14, 2020 at 7:26 PM Ning Zhang wrote:
> Hello Samuel,
>
> I guess you are
Hi,
Can you share your Jira user-id so we can sign you up?
Thanks,
Bill
On Tue, Sep 15, 2020 at 1:55 AM Shaohan Yin wrote:
> Hi,
>
> I am interested in participating in the project. It would be appreciated if
> you could add me to the contributors list.
>
> Cheers
>
13 matches
Mail list logo
