[jira] [Commented] (KAFKA-5173) SASL tests failing with Could not find a 'KafkaServer' or 'sasl_plaintext.KafkaServer' entry in the JAAS configuration

[ https://issues.apache.org/jira/browse/KAFKA-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998210#comment-15998210 ] Rajini Sivaram commented on KAFKA-5173: --- [~baluchicken] Yes, that would be useful. Would you like to

[jira] [Commented] (KAFKA-4764) Improve diagnostics for SASL authentication failures

[ https://issues.apache.org/jira/browse/KAFKA-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998186#comment-15998186 ] Rajini Sivaram commented on KAFKA-4764: --- [~junrao] SASL was designed to be embedded into a protocol

[jira] [Commented] (KAFKA-5173) SASL tests failing with Could not find a 'KafkaServer' or 'sasl_plaintext.KafkaServer' entry in the JAAS configuration

[ https://issues.apache.org/jira/browse/KAFKA-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998045#comment-15998045 ] Rajini Sivaram commented on KAFKA-5173: --- [~ijuma] Yes, they do both look like the same issue. I

[jira] [Commented] (KAFKA-4764) Improve diagnostics for SASL authentication failures

[ https://issues.apache.org/jira/browse/KAFKA-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997421#comment-15997421 ] Rajini Sivaram commented on KAFKA-4764: --- [~junrao] Yes, Zookeeper does the same as Kafka does today.

[jira] [Updated] (KAFKA-4703) Test with two SASL_SSL listeners with different JAAS contexts

[ https://issues.apache.org/jira/browse/KAFKA-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4703: -- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch

[jira] [Updated] (KAFKA-4955) Add network handler thread utilization to request quota calculation

[ https://issues.apache.org/jira/browse/KAFKA-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4955: -- Resolution: Fixed Status: Resolved (was: Patch Available) [~junrao] Yes, thank you.

[jira] [Resolved] (KAFKA-5086) Update topic expiry time in Metadata every time the topic metadata is requested

[ https://issues.apache.org/jira/browse/KAFKA-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-5086. --- Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 2869

[jira] [Assigned] (KAFKA-5094) Censor SCRAM config change logging

[ https://issues.apache.org/jira/browse/KAFKA-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-5094: - Assignee: Rajini Sivaram > Censor SCRAM config change logging >

[jira] [Comment Edited] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967450#comment-15967450 ] Rajini Sivaram edited comment on KAFKA-5062 at 4/13/17 11:37 AM: - [~ijuma]

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967450#comment-15967450 ] Rajini Sivaram commented on KAFKA-5062: --- [~ijuma] Was it an application writing bad data - not a

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967357#comment-15967357 ] Rajini Sivaram commented on KAFKA-5062: --- [~apurva] Is this on a PLAINTEXT port? Also, do you have

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965722#comment-15965722 ] Rajini Sivaram commented on KAFKA-4814: --- [~baluchicken] Sorry, I had forgotten about this one. Yes,

[jira] [Created] (KAFKA-5051) Avoid DNS reverse lookup in security-critical TLS code path

Rajini Sivaram created KAFKA-5051: - Summary: Avoid DNS reverse lookup in security-critical TLS code path Key: KAFKA-5051 URL: https://issues.apache.org/jira/browse/KAFKA-5051 Project: Kafka

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958663#comment-15958663 ] Rajini Sivaram commented on KAFKA-4814: --- [~baluchicken] Let me know you would like me to take this.

[jira] [Updated] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4943: -- Status: Patch Available (was: Open) > SCRAM secret's should be better protected with Zookeeper

[jira] [Updated] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4943: -- Affects Version/s: 0.10.2.0 Fix Version/s: 0.10.2.1 Component/s: security >

[jira] [Commented] (KAFKA-4997) Issue with running kafka-acls.sh when using SASL between Kafka and ZK

[ https://issues.apache.org/jira/browse/KAFKA-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953144#comment-15953144 ] Rajini Sivaram commented on KAFKA-4997: --- The user principal (by default for Kerberos) for each node

[jira] [Commented] (KAFKA-4955) Add network handler thread utilization to request quota calculation

[ https://issues.apache.org/jira/browse/KAFKA-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945223#comment-15945223 ] Rajini Sivaram commented on KAFKA-4955: --- Have included this is in the KAFKA-4954 PR

[jira] [Created] (KAFKA-4957) Add documentation for request quotas

Rajini Sivaram created KAFKA-4957: - Summary: Add documentation for request quotas Key: KAFKA-4957 URL: https://issues.apache.org/jira/browse/KAFKA-4957 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-4956) Add system tests for request quotas

Rajini Sivaram created KAFKA-4956: - Summary: Add system tests for request quotas Key: KAFKA-4956 URL: https://issues.apache.org/jira/browse/KAFKA-4956 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-4955) Add network handler thread utilization to request quota calculation

Rajini Sivaram created KAFKA-4955: - Summary: Add network handler thread utilization to request quota calculation Key: KAFKA-4955 URL: https://issues.apache.org/jira/browse/KAFKA-4955 Project: Kafka

[jira] [Created] (KAFKA-4954) Implementation and unit tests for request handler thread utilization quota

Rajini Sivaram created KAFKA-4954: - Summary: Implementation and unit tests for request handler thread utilization quota Key: KAFKA-4954 URL: https://issues.apache.org/jira/browse/KAFKA-4954 Project:

[jira] [Commented] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940275#comment-15940275 ] Rajini Sivaram commented on KAFKA-4943: --- [~jstrom] [~stephane.maa...@gmail.com] Will submit a PR to

[jira] [Assigned] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4943: - Assignee: Rajini Sivaram > SCRAM secret's should be better protected with Zookeeper ACLs

[jira] [Commented] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938726#comment-15938726 ] Rajini Sivaram commented on KAFKA-4943: --- The current SCRAM implementation uses the default ACL

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890234#comment-15890234 ] Rajini Sivaram commented on KAFKA-4631: --- The attached PR solves the issue in the second failure in

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887913#comment-15887913 ] Rajini Sivaram commented on KAFKA-4779: --- The new failure looks like a very different issue. The

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880684#comment-15880684 ] Rajini Sivaram commented on KAFKA-4779: --- I couldn't recreate the failure, but the code for phase_two

[jira] [Assigned] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4779: - Assignee: Rajini Sivaram > Failure in

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877030#comment-15877030 ] Rajini Sivaram commented on KAFKA-4779: --- [~apurva] Do you by any chance have the full logs of a

[jira] [Created] (KAFKA-4764) Improve diagnostics for SASL authentication failures

Rajini Sivaram created KAFKA-4764: - Summary: Improve diagnostics for SASL authentication failures Key: KAFKA-4764 URL: https://issues.apache.org/jira/browse/KAFKA-4764 Project: Kafka Issue

[jira] [Commented] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

[ https://issues.apache.org/jira/browse/KAFKA-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839608#comment-15839608 ] Rajini Sivaram commented on KAFKA-4557: --- [~ijuma] Yes, if a message is sent to the same partition

[jira] [Commented] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

[ https://issues.apache.org/jira/browse/KAFKA-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839587#comment-15839587 ] Rajini Sivaram commented on KAFKA-4557: --- [~salaev] Does the producer application send messages from

[jira] [Assigned] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

[ https://issues.apache.org/jira/browse/KAFKA-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4557: - Assignee: Rajini Sivaram > ConcurrentModificationException in KafkaProducer event loop >

[jira] [Created] (KAFKA-4627) Intermittent test failure in consumer close test

Rajini Sivaram created KAFKA-4627: - Summary: Intermittent test failure in consumer close test Key: KAFKA-4627 URL: https://issues.apache.org/jira/browse/KAFKA-4627 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-4626) Add consumer close change to upgrade notes

Rajini Sivaram created KAFKA-4626: - Summary: Add consumer close change to upgrade notes Key: KAFKA-4626 URL: https://issues.apache.org/jira/browse/KAFKA-4626 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-4590) Add system test for SASL/SCRAM

Rajini Sivaram created KAFKA-4590: - Summary: Add system test for SASL/SCRAM Key: KAFKA-4590 URL: https://issues.apache.org/jira/browse/KAFKA-4590 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-4589) Add documentation for SASL/SCRAM

Rajini Sivaram created KAFKA-4589: - Summary: Add documentation for SASL/SCRAM Key: KAFKA-4589 URL: https://issues.apache.org/jira/browse/KAFKA-4589 Project: Kafka Issue Type: Task

[jira] [Assigned] (KAFKA-4583) KafkaConsumerTest.testGracefulClose transient failure

[ https://issues.apache.org/jira/browse/KAFKA-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4583: - Assignee: Rajini Sivaram > KafkaConsumerTest.testGracefulClose transient failure >

[jira] [Assigned] (KAFKA-4583) KafkaConsumerTest.testGracefulClose transient failure

[ https://issues.apache.org/jira/browse/KAFKA-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4583: - Assignee: Rajini Sivaram > KafkaConsumerTest.testGracefulClose transient failure >

[jira] [Updated] (KAFKA-4583) KafkaConsumerTest.testGracefulClose transient failure

[ https://issues.apache.org/jira/browse/KAFKA-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4583: -- Assignee: (was: Rajini Sivaram) > KafkaConsumerTest.testGracefulClose transient failure >

[jira] [Created] (KAFKA-4581) Fail gracefully if multiple login modules are specified in sasl.jaas.config

Rajini Sivaram created KAFKA-4581: - Summary: Fail gracefully if multiple login modules are specified in sasl.jaas.config Key: KAFKA-4581 URL: https://issues.apache.org/jira/browse/KAFKA-4581 Project:

[jira] [Created] (KAFKA-4580) Change one SASL system test to use new JAAS config property

Rajini Sivaram created KAFKA-4580: - Summary: Change one SASL system test to use new JAAS config property Key: KAFKA-4580 URL: https://issues.apache.org/jira/browse/KAFKA-4580 Project: Kafka

[jira] [Created] (KAFKA-4568) Simplify multiple mechanism support in SaslTestHarness

Rajini Sivaram created KAFKA-4568: - Summary: Simplify multiple mechanism support in SaslTestHarness Key: KAFKA-4568 URL: https://issues.apache.org/jira/browse/KAFKA-4568 Project: Kafka Issue

[jira] [Commented] (KAFKA-3687) Internal Authorization Failure at startup with ACLs and security.inter.broker.protocol=PLAINTEXT

[ https://issues.apache.org/jira/browse/KAFKA-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755587#comment-15755587 ] Rajini Sivaram commented on KAFKA-3687: --- [~raghu98...@gmail.com] You need to set

[jira] [Commented] (KAFKA-3540) KafkaConsumer.close() may block indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752780#comment-15752780 ] Rajini Sivaram commented on KAFKA-3540: --- I have opened

[jira] [Commented] (KAFKA-4536) Kafka clients throw NullPointerException on poll when delete the relative topic

[ https://issues.apache.org/jira/browse/KAFKA-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748359#comment-15748359 ] Rajini Sivaram commented on KAFKA-4536: --- This is fixed in 0.10.1.0. > Kafka clients throw

[jira] [Commented] (KAFKA-4538) Version

[ https://issues.apache.org/jira/browse/KAFKA-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748324#comment-15748324 ] Rajini Sivaram commented on KAFKA-4538: --- If you are using KafkaConsumer, this could be due to

[jira] [Assigned] (KAFKA-4431) HeartbeatThread should be a daemon thread

[ https://issues.apache.org/jira/browse/KAFKA-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4431: - Assignee: Rajini Sivaram > HeartbeatThread should be a daemon thread >

[jira] [Commented] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

[ https://issues.apache.org/jira/browse/KAFKA-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735355#comment-15735355 ] Rajini Sivaram commented on KAFKA-4515: --- This is being addressed in KIP-91:

[jira] [Commented] (KAFKA-4470) Exception (java.lang.RuntimeException) encountered during startup: org.codehaus.jackson.JsonParseException:

[ https://issues.apache.org/jira/browse/KAFKA-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708722#comment-15708722 ] Rajini Sivaram commented on KAFKA-4470: --- JIRA is on the wrong project? > Exception

[jira] [Commented] (KAFKA-4419) Unable to GetOffset when the ACL of topic is defined

[ https://issues.apache.org/jira/browse/KAFKA-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705720#comment-15705720 ] Rajini Sivaram commented on KAFKA-4419: --- There is an open JIRA to fix this: KAFKA-3355. > Unable to

[jira] [Created] (KAFKA-4440) Make producer RecordMetadata non-final

Rajini Sivaram created KAFKA-4440: - Summary: Make producer RecordMetadata non-final Key: KAFKA-4440 URL: https://issues.apache.org/jira/browse/KAFKA-4440 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-4426) Add consumer.close(timeout, unit) for graceful close with timeout

Rajini Sivaram created KAFKA-4426: - Summary: Add consumer.close(timeout, unit) for graceful close with timeout Key: KAFKA-4426 URL: https://issues.apache.org/jira/browse/KAFKA-4426 Project: Kafka

[jira] [Commented] (KAFKA-4419) Unable to GetOffset when the ACL of topic is defined

[ https://issues.apache.org/jira/browse/KAFKA-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15674826#comment-15674826 ] Rajini Sivaram commented on KAFKA-4419: --- {{GetOffsetShell}} doesn't currently support security

[jira] [Commented] (KAFKA-4413) Kakfa should support default SSLContext

[ https://issues.apache.org/jira/browse/KAFKA-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15674795#comment-15674795 ] Rajini Sivaram commented on KAFKA-4413: --- Truststore is an optional config. If you don't specify a

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670575#comment-15670575 ] Rajini Sivaram commented on KAFKA-4406: --- Perhaps it is worth writing a small KIP explaining the

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670416#comment-15670416 ] Rajini Sivaram commented on KAFKA-4406: --- Java security providers are used not just for cryptographic

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667577#comment-15667577 ] Rajini Sivaram commented on KAFKA-4406: --- The PR adds the new configuration to clients, so I had

[jira] [Commented] (KAFKA-4407) Java consumer does not always send LEAVE_GROUP request during shut down

[ https://issues.apache.org/jira/browse/KAFKA-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667173#comment-15667173 ] Rajini Sivaram commented on KAFKA-4407: --- KAFKA-3703 (PR https://github.com/apache/kafka/pull/1836)

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666957#comment-15666957 ] Rajini Sivaram commented on KAFKA-4406: --- [~magnus.reftel] You will need to create a [Kafka

[jira] [Commented] (KAFKA-4365) In case async producer closes the TCP connection to Kafka broker, last sent messages might be lost.

[ https://issues.apache.org/jira/browse/KAFKA-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628696#comment-15628696 ] Rajini Sivaram commented on KAFKA-4365: --- [PR #1836|https://github.com/apache/kafka/pull/1836] for

[jira] [Updated] (KAFKA-3703) Handle close gracefully for consumers and producers with acks=0

[ https://issues.apache.org/jira/browse/KAFKA-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3703: -- Summary: Handle close gracefully for consumers and producers with acks=0 (was:

[jira] [Created] (KAFKA-4363) Add document for dynamic JAAS configuration property sasl.jaas.config

Rajini Sivaram created KAFKA-4363: - Summary: Add document for dynamic JAAS configuration property sasl.jaas.config Key: KAFKA-4363 URL: https://issues.apache.org/jira/browse/KAFKA-4363 Project:

[jira] [Updated] (KAFKA-3751) Add support for SASL/SCRAM mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3751: -- Description: Salted Challenge Response Authentication Mechanism (SCRAM) provides secure

[jira] [Updated] (KAFKA-3751) Add support for SASL mechanism SCRAM-SHA-256

[ https://issues.apache.org/jira/browse/KAFKA-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3751: -- Fix Version/s: 0.10.2.0 Status: Patch Available (was: Open) KIP corresponding to

[jira] [Commented] (KAFKA-4294) Allow password file in server.properties to separate 'secrets' from standard configs

[ https://issues.apache.org/jira/browse/KAFKA-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574737#comment-15574737 ] Rajini Sivaram commented on KAFKA-4294: --- It may be good to bring this up in KIP-76 discussion:

[jira] [Assigned] (KAFKA-4301) Include some SSL/TLS logging to avoid need need for javax debug util every time an issue arises

[ https://issues.apache.org/jira/browse/KAFKA-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4301: - Assignee: Rajini Sivaram > Include some SSL/TLS logging to avoid need need for javax

[jira] [Created] (KAFKA-4292) Configurable SASL callback handlers

Rajini Sivaram created KAFKA-4292: - Summary: Configurable SASL callback handlers Key: KAFKA-4292 URL: https://issues.apache.org/jira/browse/KAFKA-4292 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-4265) Intermittent test failure ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle

[ https://issues.apache.org/jira/browse/KAFKA-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4265: -- Description:

[jira] [Created] (KAFKA-4267) Quota initialization for <user, clientId> uses incorrect ZK path

Rajini Sivaram created KAFKA-4267: - Summary: Quota initialization for uses incorrect ZK path Key: KAFKA-4267 URL: https://issues.apache.org/jira/browse/KAFKA-4267 Project: Kafka

[jira] [Created] (KAFKA-4265) Intermittent test failure ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle

Rajini Sivaram created KAFKA-4265: - Summary: Intermittent test failure ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle Key: KAFKA-4265 URL: https://issues.apache.org/jira/browse/KAFKA-4265

[jira] [Created] (KAFKA-4262) Intermittent unit test failure ReassignPartitionsClusterTest.shouldExecuteThrottledReassignment

Rajini Sivaram created KAFKA-4262: - Summary: Intermittent unit test failure ReassignPartitionsClusterTest.shouldExecuteThrottledReassignment Key: KAFKA-4262 URL: https://issues.apache.org/jira/browse/KAFKA-4262

[jira] [Updated] (KAFKA-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4252: -- Status: Patch Available (was: Open) > Missing ProducerRequestPurgatory >

[jira] [Commented] (KAFKA-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551696#comment-15551696 ] Rajini Sivaram commented on KAFKA-4252: --- I think the documentation was not updated when the class

[jira] [Assigned] (KAFKA-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4252: - Assignee: Rajini Sivaram > Missing ProducerRequestPurgatory >

[jira] [Updated] (KAFKA-4259) Enable JAAS configuration for Kafka clients without a config file

[ https://issues.apache.org/jira/browse/KAFKA-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4259: -- Description: See KIP-85 for details:

[jira] [Created] (KAFKA-4259) Enable JAAS configuration for Kafka clients without a config file

Rajini Sivaram created KAFKA-4259: - Summary: Enable JAAS configuration for Kafka clients without a config file Key: KAFKA-4259 URL: https://issues.apache.org/jira/browse/KAFKA-4259 Project: Kafka

[jira] [Commented] (KAFKA-3985) Transient system test failure ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade.security_protocol

[ https://issues.apache.org/jira/browse/KAFKA-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15548160#comment-15548160 ] Rajini Sivaram commented on KAFKA-3985: --- [~fpj] At the moment they use a fixed filename since the

[jira] [Commented] (KAFKA-3985) Transient system test failure ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade.security_protocol

[ https://issues.apache.org/jira/browse/KAFKA-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15548091#comment-15548091 ] Rajini Sivaram commented on KAFKA-3985: --- [~fpj] I would not have expected each test to create its

[jira] [Commented] (KAFKA-3985) Transient system test failure ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade.security_protocol

[ https://issues.apache.org/jira/browse/KAFKA-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546706#comment-15546706 ] Rajini Sivaram commented on KAFKA-3985: --- [~fpj] Would it be possible to attach the full logs of the

[jira] [Created] (KAFKA-4227) AdminManager is not shutdown when KafkaServer is shutdown

Rajini Sivaram created KAFKA-4227: - Summary: AdminManager is not shutdown when KafkaServer is shutdown Key: KAFKA-4227 URL: https://issues.apache.org/jira/browse/KAFKA-4227 Project: Kafka

[jira] [Updated] (KAFKA-4209) Reduce time taken to run quota integration tests

[ https://issues.apache.org/jira/browse/KAFKA-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4209: -- Status: Patch Available (was: Open) > Reduce time taken to run quota integration tests >

[jira] [Created] (KAFKA-4209) Reduce time taken to run quota integration tests

Rajini Sivaram created KAFKA-4209: - Summary: Reduce time taken to run quota integration tests Key: KAFKA-4209 URL: https://issues.apache.org/jira/browse/KAFKA-4209 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4188) compilation issues with org.apache.kafka.clients.consumer.internals.Fetcher.java

[ https://issues.apache.org/jira/browse/KAFKA-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502917#comment-15502917 ] Rajini Sivaram commented on KAFKA-4188: --- Can you try a clean build? > compilation issues with >

[jira] [Updated] (KAFKA-4055) Add system tests for secure quotas

[ https://issues.apache.org/jira/browse/KAFKA-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4055: -- Status: Patch Available (was: Open) > Add system tests for secure quotas >

[jira] [Updated] (KAFKA-3586) Quotas do not revert to default values when override config is deleted

[ https://issues.apache.org/jira/browse/KAFKA-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3586: -- Resolution: Fixed Status: Resolved (was: Patch Available) Fixed under KAFKA-4158. >

[jira] [Updated] (KAFKA-3930) IPv6 address can't used as ObjectName

[ https://issues.apache.org/jira/browse/KAFKA-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3930: -- Status: Patch Available (was: Open) > IPv6 address can't used as ObjectName >

[jira] [Commented] (KAFKA-3913) Old consumer's metrics error when using IPv6

[ https://issues.apache.org/jira/browse/KAFKA-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487235#comment-15487235 ] Rajini Sivaram commented on KAFKA-3913: --- Fixing under KAFKA-3930. > Old consumer's metrics error

[jira] [Assigned] (KAFKA-3930) IPv6 address can't used as ObjectName

[ https://issues.apache.org/jira/browse/KAFKA-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-3930: - Assignee: Rajini Sivaram > IPv6 address can't used as ObjectName >

[jira] [Updated] (KAFKA-4079) Document quota configuration changes from KIP-55

[ https://issues.apache.org/jira/browse/KAFKA-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4079: -- Status: Patch Available (was: Open) > Document quota configuration changes from KIP-55 >

[jira] [Updated] (KAFKA-4139) Kafka consumer stuck in ensureCoordinatorReady after broker failure

[ https://issues.apache.org/jira/browse/KAFKA-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4139: -- Status: Patch Available (was: Open) > Kafka consumer stuck in ensureCoordinatorReady after

[jira] [Created] (KAFKA-4139) Kafka consumer stuck in ensureCoordinatorReady after broker failure

Rajini Sivaram created KAFKA-4139: - Summary: Kafka consumer stuck in ensureCoordinatorReady after broker failure Key: KAFKA-4139 URL: https://issues.apache.org/jira/browse/KAFKA-4139 Project: Kafka

[jira] [Commented] (KAFKA-4119) Get topic offset with Kafka SSL

[ https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470107#comment-15470107 ] Rajini Sivaram commented on KAFKA-4119: --- Only the new consumer supports security. So if you have

[jira] [Commented] (KAFKA-4119) Get topic offset with Kafka SSL

[ https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467026#comment-15467026 ] Rajini Sivaram commented on KAFKA-4119: --- You should use the newer ConsumerGroupCommand for the new

[jira] [Commented] (KAFKA-4121) Allow creating broker listeners from hostname

[ https://issues.apache.org/jira/browse/KAFKA-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466998#comment-15466998 ] Rajini Sivaram commented on KAFKA-4121: --- Advertised listeners can specify hostnames, the exception

[jira] [Updated] (KAFKA-3703) Selector.close() doesn't complete outgoing writes

[ https://issues.apache.org/jira/browse/KAFKA-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3703: -- Status: Patch Available (was: Open) > Selector.close() doesn't complete outgoing writes >

[jira] [Updated] (KAFKA-3703) Selector.close() doesn't complete outgoing writes

[ https://issues.apache.org/jira/browse/KAFKA-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3703: -- Description: Outgoing writes may be discarded when a connection is closed. For instance, when

[jira] [Updated] (KAFKA-3703) Selector.close() doesn't complete outgoing writes

[ https://issues.apache.org/jira/browse/KAFKA-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3703: -- Affects Version/s: 0.10.0.1 Component/s: clients Summary:

[jira] [Updated] (KAFKA-4077) Backdate validity of certificates in system tests to cope with clock skew

[ https://issues.apache.org/jira/browse/KAFKA-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4077: -- Status: Patch Available (was: Open) > Backdate validity of certificates in system tests to

<    1   2   3   4   5   6   7   8   >