[jira] [Created] (KAFKA-8419) Enable KafkaLog4JAppender to use SASL Authentication Callback Handlers

2019-05-23 Thread Ryan P (JIRA)
Ryan P created KAFKA-8419: - Summary: Enable KafkaLog4JAppender to use SASL Authentication Callback Handlers Key: KAFKA-8419 URL: https://issues.apache.org/jira/browse/KAFKA-8419 Project: Kafka

[jira] [Created] (KAFKA-6893) Processors created after acceptor started which can cause in a brief refusal to accept connections

2018-05-10 Thread Ryan P (JIRA)
Ryan P created KAFKA-6893: - Summary: Processors created after acceptor started which can cause in a brief refusal to accept connections Key: KAFKA-6893 URL: https://issues.apache.org/jira/browse/KAFKA-6893

[jira] [Created] (KAFKA-6440) Expose Connect leader via REST

2018-01-10 Thread Ryan P (JIRA)
Ryan P created KAFKA-6440: - Summary: Expose Connect leader via REST Key: KAFKA-6440 URL: https://issues.apache.org/jira/browse/KAFKA-6440 Project: Kafka Issue Type: Improvement Components:

[jira] [Created] (KAFKA-6295) Add 'Coordinator Id' to consumer metrics

2017-12-01 Thread Ryan P (JIRA)
Ryan P created KAFKA-6295: - Summary: Add 'Coordinator Id' to consumer metrics Key: KAFKA-6295 URL: https://issues.apache.org/jira/browse/KAFKA-6295 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-6169) Kafka Log should reject negative timestamps

2017-11-04 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P resolved KAFKA-6169. --- Resolution: Won't Fix > Kafka Log should reject negative timestamps >

[jira] [Created] (KAFKA-6169) Kafka Log should reject negative timestamps

2017-11-03 Thread Ryan P (JIRA)
Ryan P created KAFKA-6169: - Summary: Kafka Log should reject negative timestamps Key: KAFKA-6169 URL: https://issues.apache.org/jira/browse/KAFKA-6169 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6149) LogCleanerManager should include topic partition name when warning of invalid cleaner offset

2017-10-30 Thread Ryan P (JIRA)
Ryan P created KAFKA-6149: - Summary: LogCleanerManager should include topic partition name when warning of invalid cleaner offset Key: KAFKA-6149 URL: https://issues.apache.org/jira/browse/KAFKA-6149

[jira] [Created] (KAFKA-5764) KafkaShortnamer should allow for case inensitive matches

2017-08-22 Thread Ryan P (JIRA)
Ryan P created KAFKA-5764: - Summary: KafkaShortnamer should allow for case inensitive matches Key: KAFKA-5764 URL: https://issues.apache.org/jira/browse/KAFKA-5764 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-5691) ZKUtils.CreateRecursive should handle NOAUTH

2017-08-01 Thread Ryan P (JIRA)
Ryan P created KAFKA-5691: - Summary: ZKUtils.CreateRecursive should handle NOAUTH Key: KAFKA-5691 URL: https://issues.apache.org/jira/browse/KAFKA-5691 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5526) ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets

2017-06-27 Thread Ryan P (JIRA)
Ryan P created KAFKA-5526: - Summary: ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets Key: KAFKA-5526 URL: https://issues.apache.org/jira/browse/KAFKA-5526

[jira] [Created] (KAFKA-5091) ReassignPartitionsCommand should protect against empty replica list assignment

2017-04-19 Thread Ryan P (JIRA)
Ryan P created KAFKA-5091: - Summary: ReassignPartitionsCommand should protect against empty replica list assignment Key: KAFKA-5091 URL: https://issues.apache.org/jira/browse/KAFKA-5091 Project: Kafka

[jira] [Created] (KAFKA-5066) KafkaMetricsConfig properties and description notably missing from documentation

2017-04-13 Thread Ryan P (JIRA)
Ryan P created KAFKA-5066: - Summary: KafkaMetricsConfig properties and description notably missing from documentation Key: KAFKA-5066 URL: https://issues.apache.org/jira/browse/KAFKA-5066 Project: Kafka

[jira] [Created] (KAFKA-4985) kafka-acls should resolve dns names and accept ip ranges

2017-03-30 Thread Ryan P (JIRA)
Ryan P created KAFKA-4985: - Summary: kafka-acls should resolve dns names and accept ip ranges Key: KAFKA-4985 URL: https://issues.apache.org/jira/browse/KAFKA-4985 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4041) kafka unable to reconnect to zookeeper behind an ELB

2017-01-18 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828420#comment-15828420 ] Ryan P commented on KAFKA-4041: --- This is actually the result of a ZK bug which is being actively worked on

[jira] [Commented] (KAFKA-4606) make getOffsetsTopicPartitionCount mutable

2017-01-06 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806253#comment-15806253 ] Ryan P commented on KAFKA-4606: --- Artificial was the wrong word, but I still think an argument can be made to

[jira] [Created] (KAFKA-4606) make getOffsetsTopicPartitionCount mutable

2017-01-06 Thread Ryan P (JIRA)
Ryan P created KAFKA-4606: - Summary: make getOffsetsTopicPartitionCount mutable Key: KAFKA-4606 URL: https://issues.apache.org/jira/browse/KAFKA-4606 Project: Kafka Issue Type: Improvement

[jira] [Issue Comment Deleted] (KAFKA-4364) Sink tasks expose secrets in DEBUG logging

2016-11-08 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-4364: -- Comment: was deleted (was: https://github.com/apache/kafka/pull/2115) > Sink tasks expose secrets in DEBUG

[jira] [Commented] (KAFKA-4364) Sink tasks expose secrets in DEBUG logging

2016-11-08 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15649205#comment-15649205 ] Ryan P commented on KAFKA-4364: --- https://github.com/apache/kafka/pull/2115 > Sink tasks expose secrets in

[jira] [Updated] (KAFKA-4364) Sink tasks expose secrets in DEBUG logging

2016-11-08 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-4364: -- Assignee: Ryan P (was: Ewen Cheslack-Postava) > Sink tasks expose secrets in DEBUG logging >

[jira] [Created] (KAFKA-4369) ZkClient is not closed upon streams shutdown

2016-11-02 Thread Ryan P (JIRA)
Ryan P created KAFKA-4369: - Summary: ZkClient is not closed upon streams shutdown Key: KAFKA-4369 URL: https://issues.apache.org/jira/browse/KAFKA-4369 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-4364) Sink tasks expose secrets in DEBUG logging

2016-11-01 Thread Ryan P (JIRA)
Ryan P created KAFKA-4364: - Summary: Sink tasks expose secrets in DEBUG logging Key: KAFKA-4364 URL: https://issues.apache.org/jira/browse/KAFKA-4364 Project: Kafka Issue Type: Bug

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

2016-10-13 Thread Ryan P (JIRA)
Ryan P created KAFKA-4301: - Summary: Include some SSL/TLS logging to avoid need need for javax debug util every time an issue arises Key: KAFKA-4301 URL: https://issues.apache.org/jira/browse/KAFKA-4301

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

2016-10-12 Thread Ryan P (JIRA)
Ryan P created KAFKA-4294: - Summary: Allow password file in server.properties to separate 'secrets' from standard configs Key: KAFKA-4294 URL: https://issues.apache.org/jira/browse/KAFKA-4294 Project: Kafka

[jira] [Updated] (KAFKA-4247) kafka-run-class has potential to add a leading colon to classpath

2016-10-08 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-4247: -- Description: https://github.com/confluentinc/kafka/blob/trunk/bin/kafka-run-class.sh#L128-L133 In the event

[jira] [Updated] (KAFKA-4247) kafka-run-class has potential to add a leading colon to classpath

2016-10-08 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-4247: -- Description: https://github.com/confluentinc/kafka/blob/trunk/bin/kafka-run-class.sh#L128-L133 In the event

[jira] [Updated] (KAFKA-3719) Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too narrow

2016-09-14 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3719: -- Assignee: Ryan P > Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too > narrow >

[jira] [Reopened] (KAFKA-3719) Pattern regex org.apache.kafka.common.utils.Utils.HOST_PORT_PATTERN is too narrow

2016-09-14 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P reopened KAFKA-3719: --- I would like to re-open this topic for discussion. While [~gwenshap] is correct, underscores are not valid

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

2016-08-04 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408544#comment-15408544 ] Ryan P commented on KAFKA-3665: --- [~junrao] yes I do think that SNI is still relevant despite the presence of

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

2016-08-03 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405659#comment-15405659 ] Ryan P commented on KAFKA-3665: --- RFC-6066 describes an extension to the TLS protocol to handle the VIP case.

[jira] [Created] (KAFKA-3986) completedReceives can contain closed channels

2016-07-23 Thread Ryan P (JIRA)
Ryan P created KAFKA-3986: - Summary: completedReceives can contain closed channels Key: KAFKA-3986 URL: https://issues.apache.org/jira/browse/KAFKA-3986 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3983) It would be helpful if SocketServer's Acceptors logged both the SocketChannel port and the processor ID upon registra

2016-07-21 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3983: -- Description: Currently Acceptors log the following message prior to registering passing the accepted channel

[jira] [Created] (KAFKA-3983) It would be helpful if SocketServer's Acceptors logged both the SocketChannel port and the processor ID upon registra

2016-07-21 Thread Ryan P (JIRA)
Ryan P created KAFKA-3983: - Summary: It would be helpful if SocketServer's Acceptors logged both the SocketChannel port and the processor ID upon registra Key: KAFKA-3983 URL:

[jira] [Updated] (KAFKA-3754) Kafka default -Xloggc settings should include GC log rotation flags

2016-05-25 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3754: -- Description: By default kafka-run-class.sh defines it's GC settings like so:

[jira] [Updated] (KAFKA-3754) Kafka default -Xloggc settings should include GC log rotation flags

2016-05-25 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3754: -- Description: By default kafka-run-class.sh defines it's GC settings like so:

[jira] [Assigned] (KAFKA-3754) Kafka default -Xloggc settings should include GC log rotation flags

2016-05-25 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P reassigned KAFKA-3754: - Assignee: Ryan P > Kafka default -Xloggc settings should include GC log rotation flags >

[jira] [Created] (KAFKA-3754) Kafka default -Xloggc settings should include GC log rotation flags

2016-05-25 Thread Ryan P (JIRA)
Ryan P created KAFKA-3754: - Summary: Kafka default -Xloggc settings should include GC log rotation flags Key: KAFKA-3754 URL: https://issues.apache.org/jira/browse/KAFKA-3754 Project: Kafka Issue

[jira] [Updated] (KAFKA-3667) Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration

2016-05-06 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3667: -- Description: Kafka's documentation should include additional guidance on how to properly enable SSL with

[jira] [Created] (KAFKA-3667) Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration

2016-05-06 Thread Ryan P (JIRA)
Ryan P created KAFKA-3667: - Summary: Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration Key: KAFKA-3667 URL: https://issues.apache.org/jira/browse/KAFKA-3667

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

2016-05-06 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274035#comment-15274035 ] Ryan P commented on KAFKA-3665: --- [~ijuma], I can absolutely do that. Would you like me to include the

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

2016-05-06 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274001#comment-15274001 ] Ryan P commented on KAFKA-3665: --- [~ijuma], just a nit but [RFC 6125|https://tools.ietf.org/search/rfc6125]

[jira] [Resolved] (KAFKA-3533) Kafka Consumer Config validation should be AND not OR

2016-04-08 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P resolved KAFKA-3533. --- Resolution: Invalid Misinterpreted the intended purpose of this check. > Kafka Consumer Config validation

[jira] [Created] (KAFKA-3533) Kafka Consumer Config validation should be AND not OR

2016-04-08 Thread Ryan P (JIRA)
Ryan P created KAFKA-3533: - Summary: Kafka Consumer Config validation should be AND not OR Key: KAFKA-3533 URL: https://issues.apache.org/jira/browse/KAFKA-3533 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

2016-03-24 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210423#comment-15210423 ] Ryan P commented on KAFKA-3445: --- [~ewencp], sorry about that I should have read that beforehand. >

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

2016-03-22 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Status: Patch Available (was: Open) > ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit >

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

2016-03-22 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Description: I'll be the first to admit this is a bit nit picky any property marked with Importance.HIGH

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

2016-03-22 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Description: I'll be the first to admit this is a bit nit picky but any property marked with Importance.HIGH

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

2016-03-22 Thread Ryan P (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3445: -- Attachment: KAFKA-3445.patch Adding a variable for TASKS_MIN_CONFIG is probably a bit of overkill but that can

[jira] [Created] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

2016-03-22 Thread Ryan P (JIRA)
Ryan P created KAFKA-3445: - Summary: ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit Key: KAFKA-3445 URL: https://issues.apache.org/jira/browse/KAFKA-3445 Project: Kafka Issue