[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128638#comment-15128638 ] ASF GitHub Bot commented on KAFKA-3068: --- Github user asfgit closed the pull request at:

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121671#comment-15121671 ] ASF GitHub Bot commented on KAFKA-3068: --- Github user enothereska closed the pull request at:

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121772#comment-15121772 ] ASF GitHub Bot commented on KAFKA-3068: --- GitHub user enothereska opened a pull request:

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117071#comment-15117071 ] Eno Thereska commented on KAFKA-3068: - Ok, I'll revert to using the 0.8.2 solution (by updating the

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115702#comment-15115702 ] Jun Rao commented on KAFKA-3068: [~ewencp], having a pluggable discovery service may be reasonable.

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116465#comment-15116465 ] Ewen Cheslack-Postava commented on KAFKA-3068: -- [~junrao] Right, for people using VIP or DNS,

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113009#comment-15113009 ] ASF GitHub Bot commented on KAFKA-3068: --- GitHub user enothereska opened a pull request:

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112863#comment-15112863 ] Ewen Cheslack-Postava commented on KAFKA-3068: -- [~enothereska] [~ijuma] Agreed, likely a KIP

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112810#comment-15112810 ] Ismael Juma commented on KAFKA-3068: [~ewencp], that sounds like a worthwhile improvement, I agree.

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112812#comment-15112812 ] Eno Thereska commented on KAFKA-3068: - [~ewencp]: sounds like a KIP? In the old Kafka we could have

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112574#comment-15112574 ] Eno Thereska commented on KAFKA-3068: - We'll go with keeping the original bootstrap brokers. >

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112787#comment-15112787 ] Ewen Cheslack-Postava commented on KAFKA-3068: -- I'm thinking more about this in combination

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15087309#comment-15087309 ] Eno Thereska commented on KAFKA-3068: - [~junrao], [~hachikuji] I understand the concerns. What I don't

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15088200#comment-15088200 ] Ewen Cheslack-Postava commented on KAFKA-3068: -- [~junrao] It's definitely a real issue -- see

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15088209#comment-15088209 ] Jason Gustafson commented on KAFKA-3068: [~ewencp] Is it not correct that the topic metadata

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085688#comment-15085688 ] Ismael Juma commented on KAFKA-3068: Yeah. Or expire brokers based on time. Let's see what others

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085618#comment-15085618 ] Eno Thereska commented on KAFKA-3068: - [~ijuma], [~hachikuji]: I think a proper solution would make

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085682#comment-15085682 ] Eno Thereska commented on KAFKA-3068: - [~ijuma]: a slightly different solution would be to keep just

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085663#comment-15085663 ] Ismael Juma commented on KAFKA-3068: [~enothereska], I agree that a better solution would involve

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086580#comment-15086580 ] Ismael Juma commented on KAFKA-3068: It does to me. > NetworkClient may connect to a different Kafka

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086554#comment-15086554 ] Jason Gustafson commented on KAFKA-3068: [~ijuma],[~enothereska] Introducing a notion of cluster

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086717#comment-15086717 ] Jun Rao commented on KAFKA-3068: There are 2 possible ways of configuring bootstrap servers: (1) Using a

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084609#comment-15084609 ] Ismael Juma commented on KAFKA-3068: Reverting to the bootstrap brokers in the config seems like a

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084470#comment-15084470 ] Jun Rao commented on KAFKA-3068: [~enothereska], [~ijuma], [~guozhang], [~ewencp], [~hachikuji], since you

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084481#comment-15084481 ] Jason Gustafson commented on KAFKA-3068: [~junrao] It does seem like an issue to me (can't believe

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084478#comment-15084478 ] Guozhang Wang commented on KAFKA-3068: -- Even without this caching, we can still potentially hit this

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084507#comment-15084507 ] Jun Rao commented on KAFKA-3068: Yes, without this caching, in theory, this is still possible. However,

[jira] [Commented] (KAFKA-3068) NetworkClient may connect to a different Kafka cluster than originally configured

[ https://issues.apache.org/jira/browse/KAFKA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15084516#comment-15084516 ] Guozhang Wang commented on KAFKA-3068: -- That is right... maybe we should just use bootstrap servers