[jira] [Commented] (KAFKA-5372) Unexpected state transition Dead to PendingShutdown

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

[jira] [Updated] (KAFKA-5515) Consider removing date formatting from Segments class

[ https://issues.apache.org/jira/browse/KAFKA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5515: --- Description: Currently the {{Segments}} class uses a date when calculating the segment id and uses

[jira] [Commented] (KAFKA-5516) Formatting verifiable producer/consumer output in a similar fashion

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

[jira] [Updated] (KAFKA-5515) Consider removing date formatting from Segments class

[ https://issues.apache.org/jira/browse/KAFKA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5515: --- Description: Currently the {{Segments}} class uses a date when calculating the segment id and uses

[jira] [Commented] (KAFKA-4388) Connect key and value converters are listed without default values

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

[jira] [Created] (KAFKA-5516) Formatting verifiable producer/consumer output in a similar fashion

Paolo Patierno created KAFKA-5516: - Summary: Formatting verifiable producer/consumer output in a similar fashion Key: KAFKA-5516 URL: https://issues.apache.org/jira/browse/KAFKA-5516 Project: Kafka

[jira] [Created] (KAFKA-5514) KafkaConsumer ignores default values in Properties object because of incorrect use of Properties object.

Geert Schuring created KAFKA-5514: - Summary: KafkaConsumer ignores default values in Properties object because of incorrect use of Properties object. Key: KAFKA-5514 URL:

[jira] [Commented] (KAFKA-5517) Support linking to particular configuration parameters

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

[jira] [Commented] (KAFKA-5473) handle ZK session expiration properly when a new session can't be established

[ 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

[jira] [Updated] (KAFKA-5517) Support linking to particular configuration parameters

[ https://issues.apache.org/jira/browse/KAFKA-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Bentley updated KAFKA-5517: --- Labels: patch-available (was: ) > Support linking to particular configuration parameters >

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063228#comment-16063228 ] Jun Rao commented on KAFKA-5413: Merged https://github.com/apache/kafka/pull/3397 to 0.10.2. > Log

[jira] [Created] (KAFKA-5517) Support linking to particular configuration parameters

Tom Bentley created KAFKA-5517: -- Summary: Support linking to particular configuration parameters Key: KAFKA-5517 URL: https://issues.apache.org/jira/browse/KAFKA-5517 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-5518) General Kafka connector performanc workload

Chen He created KAFKA-5518: -- Summary: General Kafka connector performanc workload Key: KAFKA-5518 URL: https://issues.apache.org/jira/browse/KAFKA-5518 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063452#comment-16063452 ] Chen He commented on KAFKA-3554: Thank you for the quick reply [~becket_qin]. This work is really

[jira] [Created] (KAFKA-5519) Support for multiple certificates in a single keystore

Alla Tumarkin created KAFKA-5519: Summary: Support for multiple certificates in a single keystore Key: KAFKA-5519 URL: https://issues.apache.org/jira/browse/KAFKA-5519 Project: Kafka Issue

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063456#comment-16063456 ] Joseph Aliase commented on KAFKA-5007: -- I believe that's the error we are seeing in the log. Let me

[jira] [Commented] (KAFKA-3465) kafka.tools.ConsumerOffsetChecker won't align with kafka New Consumer mode

[ https://issues.apache.org/jira/browse/KAFKA-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063569#comment-16063569 ] Colin P. McCabe commented on KAFKA-3465: Should we rename the tool or add documentation to make it

[jira] [Commented] (KAFKA-3465) kafka.tools.ConsumerOffsetChecker won't align with kafka New Consumer mode

[ https://issues.apache.org/jira/browse/KAFKA-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063618#comment-16063618 ] Vahid Hashemian commented on KAFKA-3465: [~cmccabe] I have opened a PR to update the relevant

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063514#comment-16063514 ] Nicholas Ngorok commented on KAFKA-5413: Thanks [~Kelvinrutt] for getting this solved very

[jira] [Commented] (KAFKA-4849) Bug in KafkaStreams documentation

[ https://issues.apache.org/jira/browse/KAFKA-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063739#comment-16063739 ] Guozhang Wang commented on KAFKA-4849: -- We have resolved all the reported issues in this JIRA except

[jira] [Updated] (KAFKA-5520) Extend Consumer Group Reset Offset tool for Stream Applications

[ https://issues.apache.org/jira/browse/KAFKA-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate updated KAFKA-5520: -- Description: KIP documentation:

[jira] [Updated] (KAFKA-5464) StreamsKafkaClient should not use StreamsConfig.POLL_MS_CONFIG

[ https://issues.apache.org/jira/browse/KAFKA-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5464: --- Fix Version/s: 0.11.1.0 > StreamsKafkaClient should not use StreamsConfig.POLL_MS_CONFIG >

[jira] [Updated] (KAFKA-5464) StreamsKafkaClient should not use StreamsConfig.POLL_MS_CONFIG

[ https://issues.apache.org/jira/browse/KAFKA-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5464: --- Fix Version/s: 0.11.0.1 0.10.2.2 > StreamsKafkaClient should not use

[jira] [Resolved] (KAFKA-5367) Producer should not expiry topic from metadata cache if accumulator still has data for this topic

[ https://issues.apache.org/jira/browse/KAFKA-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5367. - Resolution: Invalid > Producer should not expiry topic from metadata cache if accumulator still has >

[jira] [Commented] (KAFKA-5464) StreamsKafkaClient should not use StreamsConfig.POLL_MS_CONFIG

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

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064176#comment-16064176 ] Mahesh Veerabathiran commented on KAFKA-5153: - Having the same issue. do anyone has a

[jira] [Commented] (KAFKA-4750) KeyValueIterator returns null values

[ https://issues.apache.org/jira/browse/KAFKA-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063956#comment-16063956 ] Matthias J. Sax commented on KAFKA-4750: I think [~damianguy] or [~enothereska] can comment best

[jira] [Created] (KAFKA-5521) Support replicas movement between log directories (KIP-113)

Dong Lin created KAFKA-5521: --- Summary: Support replicas movement between log directories (KIP-113) Key: KAFKA-5521 URL: https://issues.apache.org/jira/browse/KAFKA-5521 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3465) kafka.tools.ConsumerOffsetChecker won't align with kafka New Consumer mode

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

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063798#comment-16063798 ] James Cheng commented on KAFKA-3806: [~junrao], your example of "track when an offset is obsolete

[jira] [Created] (KAFKA-5522) ListOffset should take LSO into account when searching by timestamp

Jason Gustafson created KAFKA-5522: -- Summary: ListOffset should take LSO into account when searching by timestamp Key: KAFKA-5522 URL: https://issues.apache.org/jira/browse/KAFKA-5522 Project: Kafka

[jira] [Assigned] (KAFKA-4388) Connect key and value converters are listed without default values

[ https://issues.apache.org/jira/browse/KAFKA-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Veretennikov reassigned KAFKA-4388: -- Assignee: Evgeny Veretennikov > Connect key and value converters are listed

[jira] [Commented] (KAFKA-4750) KeyValueIterator returns null values

[ https://issues.apache.org/jira/browse/KAFKA-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062575#comment-16062575 ] Evgeny Veretennikov commented on KAFKA-4750: If we invoke {{store.put(key, value)}}, and

[jira] [Created] (KAFKA-5512) KafkaConsumer: High memory allocation rate when idle

Stephane Roset created KAFKA-5512: - Summary: KafkaConsumer: High memory allocation rate when idle Key: KAFKA-5512 URL: https://issues.apache.org/jira/browse/KAFKA-5512 Project: Kafka Issue

[jira] [Updated] (KAFKA-5512) KafkaConsumer: High memory allocation rate when idle

[ https://issues.apache.org/jira/browse/KAFKA-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5512: --- Labels: performance (was: ) > KafkaConsumer: High memory allocation rate when idle >

[jira] [Updated] (KAFKA-5512) KafkaConsumer: High memory allocation rate when idle

[ https://issues.apache.org/jira/browse/KAFKA-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5512: --- Fix Version/s: 0.11.0.1 > KafkaConsumer: High memory allocation rate when idle >

[jira] [Commented] (KAFKA-5512) KafkaConsumer: High memory allocation rate when idle

[ https://issues.apache.org/jira/browse/KAFKA-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062859#comment-16062859 ] Ismael Juma commented on KAFKA-5512: Nice catch. Are you intending to submit a PR with your fixes? >