[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465970#comment-16465970
]
Ismael Juma commented on KAFKA-5473:
[~glasser], I added a comment to KAFKA-4041 and reopened it. It
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461823#comment-16461823
]
David Glasser commented on KAFKA-5473:
--
KAFKA-4041 claims that this fix, which is in 1.1, should
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293384#comment-16293384
]
ASF GitHub Bot commented on KAFKA-5473:
---
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260874#comment-16260874
]
Ismael Juma commented on KAFKA-5473:
[~junrao] [~prasincs], I've closed a bunch of JIRAs as duplicates
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252192#comment-16252192
]
Prasanna Gautam commented on KAFKA-5473:
[~junrao] [~ijuma] I have updated the PR without the
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248033#comment-16248033
]
Jun Rao commented on KAFKA-5473:
[~prasincs], thanks. Another thing that I mentioned in the PR is that it
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247927#comment-16247927
]
Prasanna Gautam commented on KAFKA-5473:
[~junrao] so looks like I can get it done this weekend. I
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241272#comment-16241272
]
Jun Rao commented on KAFKA-5473:
[~prasincs], thanks. I think the existing zk state metric is probably
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240979#comment-16240979
]
Prasanna Gautam commented on KAFKA-5473:
Ok, yeah. I ran into same/related issue this weekend on a
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240928#comment-16240928
]
Jun Rao commented on KAFKA-5473:
[~prasincs], after the discussion in KIP-217, we decided not to expose a
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235419#comment-16235419
]
Stevo Slavic commented on KAFKA-5473:
-
IMO this issue is related to KAFKA-4871.
> handle ZK session
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223232#comment-16223232
]
Prasanna Gautam commented on KAFKA-5473:
Thanks [~junrao], looks like a good start. Is there plan
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222990#comment-16222990
]
Jun Rao commented on KAFKA-5473:
[~prasincs], I created
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192247#comment-16192247
]
Jun Rao commented on KAFKA-5473:
The PR is in https://github.com/apache/kafka/pull/3990. We agreed to fix
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192126#comment-16192126
]
Guozhang Wang commented on KAFKA-5473:
--
[~ijuma] there seems still no PR yet. Is it a blocker for
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185434#comment-16185434
]
Prasanna Gautam commented on KAFKA-5473:
[~ijuma] I added a new configuration that's consistent
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185158#comment-16185158
]
Ismael Juma commented on KAFKA-5473:
[~prasincs], can you update this JIRA tomorrow with your progress
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185144#comment-16185144
]
Prasanna Gautam commented on KAFKA-5473:
Yeah, I'm OK if someone can pick it up too. I'm aiming
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184683#comment-16184683
]
Ismael Juma commented on KAFKA-5473:
We would need the PR to be submitted ASAP so that there's time
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184653#comment-16184653
]
Prasanna Gautam commented on KAFKA-5473:
Think I can make it to the code freeze. I'm at a
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184496#comment-16184496
]
Ismael Juma commented on KAFKA-5473:
Do you think you can submit it within the next few days? The code
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184314#comment-16184314
]
Prasanna Gautam commented on KAFKA-5473:
[~ijuma] Yes I intend to send a PR for this. I need to
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16183429#comment-16183429
]
Ismael Juma commented on KAFKA-5473:
[~prasincs], are you planning to submit a PR for this?
> handle
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125827#comment-16125827
]
Jun Rao commented on KAFKA-5473:
[~braedon], yes, this is the same issue as described in KAFKA-3984.
>
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125226#comment-16125226
]
Braedon Vickers commented on KAFKA-5473:
Can someone confirm if this would fix KAFKA-3984? Thanks!
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063437#comment-16063437
]
Jun Rao commented on KAFKA-5473:
[~prasincs], there are a couple cases to consider. (1) This is the case
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061610#comment-16061610
]
Prasanna Gautam commented on KAFKA-5473:
[~junrao] Why not do an exponential backoff (with jitter)
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061578#comment-16061578
]
Jun Rao commented on KAFKA-5473:
We could retry up to zk.connection.time.ms and then give up.
> handle ZK
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061049#comment-16061049
]
Ismael Juma commented on KAFKA-5473:
A couple of things:
1. [~junrao], you don't think it's worth
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060973#comment-16060973
]
Jun Rao commented on KAFKA-5473:
[~prasincs], yes, the simplest solution is for the broker to exit on
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060243#comment-16060243
]
Prasanna Gautam commented on KAFKA-5473:
I don't think failing the Broker immediately is the right
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054960#comment-16054960
]
Jun Rao commented on KAFKA-5473:
Yes, the issue is there since KAFKA-2405 was committed. So, it's
[
https://issues.apache.org/jira/browse/KAFKA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054757#comment-16054757
]
Jun Rao commented on KAFKA-5473:
The simplest solution is to just fail the broker if the new ZK session
33 matches
Mail list logo