[jira] [Updated] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5621: --- Fix Version/s: 0.11.1.0 > The producer should retry expired batches when retries are enabled >

[jira] [Commented] (KAFKA-5000) Framework should log some progress information regularly to assist in troubleshooting

[ https://issues.apache.org/jira/browse/KAFKA-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095830#comment-16095830 ] Ewen Cheslack-Postava commented on KAFKA-5000: -- Should this be logs or just covered by the

[jira] [Comment Edited] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096059#comment-16096059 ] Andrey edited comment on KAFKA-4915 at 7/21/17 9:36 AM: Not really. You log

[jira] [Assigned] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-4930: Assignee: Sönke Liebau > Connect Rest API allows creating connectors with

[jira] [Commented] (KAFKA-5067) java.sql.SQLDataException on TimeStamp column when using AWS Redshift as a JDBC source

[ https://issues.apache.org/jira/browse/KAFKA-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095854#comment-16095854 ] Ewen Cheslack-Postava commented on KAFKA-5067: -- This also looks like it has more to do with

[jira] [Commented] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096059#comment-16096059 ] Andrey commented on KAFKA-4915: --- Not really. You log message with "WARN" log level. However the first word

[jira] [Commented] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095825#comment-16095825 ] Ewen Cheslack-Postava commented on KAFKA-4915: -- [~dernasherbrezon] Can you clarify the

[jira] [Resolved] (KAFKA-5089) JAR mismatch in KafkaConnect leads to NoSuchMethodError in HDP 2.6

[ https://issues.apache.org/jira/browse/KAFKA-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5089. -- Resolution: Fixed Going to close this since it should be resolved by

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095916#comment-16095916 ] huxihx commented on KAFKA-5611: --- [~pskianis] In the log, seems that the consumer on Server 3 did not get any

[jira] [Comment Edited] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096059#comment-16096059 ] Andrey edited comment on KAFKA-4915 at 7/21/17 9:44 AM: Not really. You log the

[jira] [Commented] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096662#comment-16096662 ] Guozhang Wang commented on KAFKA-3992: -- [~cmolter] There are some discussions about whether we should

[jira] [Updated] (KAFKA-5625) Invalid subscription data may cause streams app to throw BufferUnderflowException

[ https://issues.apache.org/jira/browse/KAFKA-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-5625: - Affects Version/s: 0.11.0.0 Component/s: streams > Invalid subscription data may cause

[jira] [Created] (KAFKA-5625) Invalid subscription data may cause streams app to throw BufferUnderflowException

Xavier Léauté created KAFKA-5625: Summary: Invalid subscription data may cause streams app to throw BufferUnderflowException Key: KAFKA-5625 URL: https://issues.apache.org/jira/browse/KAFKA-5625

[jira] [Commented] (KAFKA-5563) Clarify handling of connector name in config

[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096076#comment-16096076 ] Sönke Liebau commented on KAFKA-5563: - Alright, I'll prepare a PR to introduce this check once

[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=16096111#comment-16096111 ] zhaojianbo commented on KAFKA-5007: --- @Joseph Aliase Is there any conclusion now? Did you find the

[jira] [Commented] (KAFKA-5618) Kafka stream not receive any topic/partitions/records info

[ https://issues.apache.org/jira/browse/KAFKA-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096112#comment-16096112 ] Yogesh BG commented on KAFKA-5618: -- I enabled debug and that is all the logs I got and there are no

[jira] [Commented] (KAFKA-5608) System test failure due to timeout starting Jmx tool

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

[jira] [Comment Edited] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096887#comment-16096887 ] Dominic Evans edited comment on KAFKA-3978 at 7/21/17 9:21 PM: --- [~ijuma] we

[jira] [Commented] (KAFKA-3978) Cannot truncate to a negative offset (-1) exception at broker startup

[ https://issues.apache.org/jira/browse/KAFKA-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096887#comment-16096887 ] Dominic Evans commented on KAFKA-3978: -- [~ijuma] we actually hit this issue the other day on 0.10.2

[jira] [Comment Edited] (KAFKA-4559) Add a site search bar on the Web site

[ https://issues.apache.org/jira/browse/KAFKA-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095728#comment-16095728 ] Ravi Raj Singh edited comment on KAFKA-4559 at 7/21/17 9:48 PM: Had a

[jira] [Updated] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3992: --- Fix Version/s: 0.11.1.0 > InstanceAlreadyExistsException Error for Consumers Starting in Parallel >

[jira] [Commented] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096309#comment-16096309 ] Helena Edelson commented on KAFKA-3992: --- Hi, I see this in 0.10.2.1 and I believe I saw it in 0.11,

[jira] [Comment Edited] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096309#comment-16096309 ] Helena Edelson edited comment on KAFKA-3992 at 7/21/17 2:34 PM: Hi, I see

[jira] [Commented] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096330#comment-16096330 ] Ismael Juma commented on KAFKA-3992: https://github.com/apache/kafka/pull/3328 is related, but it

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096311#comment-16096311 ] Panos Skianis commented on KAFKA-5611: -- [~huxi_2b] Yep, that seems to be the case indeed (and usually

[jira] [Comment Edited] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097048#comment-16097048 ] Panos Skianis edited comment on KAFKA-5611 at 7/22/17 1:15 AM: --- Somehow

[jira] [Commented] (KAFKA-5481) ListOffsetResponse isn't logged in the right way with trace level enabled

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

[jira] [Commented] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097077#comment-16097077 ] Ewen Cheslack-Postava commented on KAFKA-4915: -- [~dernasherbrezon] No, this is actually

[jira] [Comment Edited] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097048#comment-16097048 ] Panos Skianis edited comment on KAFKA-5611 at 7/22/17 1:18 AM: --- Somehow

[jira] [Updated] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Panos Skianis updated KAFKA-5611: - Attachment: bad-server-with-more-logging-1.tar.gz > One or more consumers in a consumer-group

[jira] [Updated] (KAFKA-4915) Don't include "error" in log messages at non-error levels

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4915: - Summary: Don't include "error" in log messages at non-error levels (was: Make

[jira] [Updated] (KAFKA-5615) Consumer hang in poll method while rebalancing is in progress (Duplicate)

[ https://issues.apache.org/jira/browse/KAFKA-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Stewart updated KAFKA-5615: Reviewer: Vahid Hashemian > Consumer hang in poll method while rebalancing is in progress

[jira] [Updated] (KAFKA-5624) Unsafe use of expired sensors

[ https://issues.apache.org/jira/browse/KAFKA-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5624: --- Description: Seems a couple unhandled cases following sensor expiration: 1. Static sensors

[jira] [Resolved] (KAFKA-3741) Allow setting of default topic configs via StreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-3741. --- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request 3459

[jira] [Commented] (KAFKA-3741) Allow setting of default topic configs via StreamsConfig

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

[jira] [Resolved] (KAFKA-1421) Error: Could not find or load main class kafka.perf.SimpleConsumerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryl Erwin resolved KAFKA-1421. Resolution: Done > Error: Could not find or load main class kafka.perf.SimpleConsumerPerformance >

[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=16096406#comment-16096406 ] ASF GitHub Bot commented on KAFKA-5512: --- Github user asfgit closed the pull request at:

[jira] [Created] (KAFKA-5624) Unsafe use of expired sensors

Jason Gustafson created KAFKA-5624: -- Summary: Unsafe use of expired sensors Key: KAFKA-5624 URL: https://issues.apache.org/jira/browse/KAFKA-5624 Project: Kafka Issue Type: Bug