[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

2015-10-25 Thread Rajini Sivaram (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973164#comment-14973164 ] Rajini Sivaram commented on KAFKA-2644: --- [~junrao] [~ijuma] [~harsha_ch] [~ewencp] I had made the

[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

2015-10-25 Thread Ewen Cheslack-Postava (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973474#comment-14973474 ] Ewen Cheslack-Postava commented on KAFKA-2644: -- [~rsivaram] Having tests is better than not

[jira] [Commented] (KAFKA-2642) Run replication tests in ducktape with SSL for clients

2015-10-25 Thread Rajini Sivaram (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973466#comment-14973466 ] Rajini Sivaram commented on KAFKA-2642: --- Will do this under KAFKA-2644 along with the SASL tests. >

[DISCUSS] KIP-40 - Extend GroupMetadata request to return group and member status

2015-10-25 Thread Jason Gustafson
Hi Kafka Devs, Currently, the new consumer provides no way to view a group's status except by inspecting coordinator and consumer logs. This includes listing the members of the group and their partition assignments. For the old consumer, tools could read this information directly from Zookeeper,

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

2015-10-25 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973551#comment-14973551 ] Jun Rao commented on KAFKA-1686: [~sriharsha], you mentioned that if the Kerberos tickets can't be

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

2015-10-25 Thread Sriharsha Chintalapani (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973566#comment-14973566 ] Sriharsha Chintalapani commented on KAFKA-1686: --- [~junrao] once the connection is

[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

2015-10-25 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973742#comment-14973742 ] Jun Rao commented on KAFKA-2644: [~rsivaram], we can start with the ducktape tests that you have with

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

2015-10-25 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973752#comment-14973752 ] Jun Rao commented on KAFKA-1686: [~sriharsha], I was thinking what happens when a user is removed from KDC

Re: Java high level consumer providing duplicate messages when auto commit is off

2015-10-25 Thread Cliff Rhyne
I was reflecting on this more and I think there is a change or two that should be considered for kafka. First off, auto-commit is a very resilient mode. Drops in zookeeper sessions due to garbage collection, network, rebalance or other interference are handled gracefully within the kafka client.

[jira] [Commented] (KAFKA-2680) Zookeeper SASL check prevents any SASL code being run with IBM JDK

2015-10-25 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973437#comment-14973437 ] ASF GitHub Bot commented on KAFKA-2680: --- GitHub user rajinisivaram opened a pull request:

[GitHub] kafka pull request: KAFKA-2680: Use IBM ConfigFile class to load j...

2015-10-25 Thread rajinisivaram
GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/357 KAFKA-2680: Use IBM ConfigFile class to load jaas config if IBM JDK Use IBM ConfigFile class with IBM JDK since JavaLoginConfig provided by SUN provider is not included with IBM JDK. You can

[jira] [Updated] (KAFKA-2680) Zookeeper SASL check prevents any SASL code being run with IBM JDK

2015-10-25 Thread Rajini Sivaram (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-2680: -- Status: Patch Available (was: Open) > Zookeeper SASL check prevents any SASL code being run

[jira] [Commented] (KAFKA-2675) SASL/Kerberos follow-up

2015-10-25 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973366#comment-14973366 ] Ismael Juma commented on KAFKA-2675: [~harsha_ch], I had a look at implementing SASL_KAFA_SERVER_REALM

[jira] [Updated] (KAFKA-2460) Fix capitalization in SSL classes

2015-10-25 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2460: --- Fix Version/s: 0.9.0.0 > Fix capitalization in SSL classes > - > >