[jira] [Assigned] (KAFKA-7983) supporting replication.throttled.replicas in dynamic broker configuration

[ https://issues.apache.org/jira/browse/KAFKA-7983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7983: Assignee: (was: lambdaliu) > supporting replication.throttled.replicas in dynamic broker

[jira] [Assigned] (KAFKA-7986) distinguish the logging from different ZooKeeperClient instances

[ https://issues.apache.org/jira/browse/KAFKA-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7986: Assignee: (was: lambdaliu) > distinguish the logging from different ZooKeeperClient instances

[jira] [Assigned] (KAFKA-7986) distinguish the logging from different ZooKeeperClient instances

[ https://issues.apache.org/jira/browse/KAFKA-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7986: Assignee: lambdaliu > distinguish the logging from different ZooKeeperClient instances >

[jira] [Updated] (KAFKA-7811) Avoid unnecessary lock acquire when KafkaConsumer commit offsets

[ https://issues.apache.org/jira/browse/KAFKA-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-7811: - Description: In KafkaConsumer#commitSync, we have the following logic: {code:java} public void

[jira] [Created] (KAFKA-7811) Avoid unnecessary lock acquire when KafkaConsumer commit offsets

lambdaliu created KAFKA-7811: Summary: Avoid unnecessary lock acquire when KafkaConsumer commit offsets Key: KAFKA-7811 URL: https://issues.apache.org/jira/browse/KAFKA-7811 Project: Kafka

[jira] [Assigned] (KAFKA-7734) Metrics tags should use LinkedHashMap to guarantee ordering

[ https://issues.apache.org/jira/browse/KAFKA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7734: Assignee: lambdaliu > Metrics tags should use LinkedHashMap to guarantee ordering >

[jira] [Commented] (KAFKA-7535) KafkaConsumer doesn't report records-lag if isolation.level is read_committed

[ https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661789#comment-16661789 ] lambdaliu commented on KAFKA-7535: -- bug introduced from this

[jira] [Assigned] (KAFKA-7535) KafkaConsumer doesn't report records-lag if isolation.level is read_committed

[ https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7535: Assignee: lambdaliu > KafkaConsumer doesn't report records-lag if isolation.level is

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589573#comment-16589573 ] lambdaliu commented on KAFKA-7190: -- Hi [~guozhang] As far as I am concerned , the follower also

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586903#comment-16586903 ] lambdaliu commented on KAFKA-7190: -- Hi [~mjsax], Changing the log level to DEBUG can't avoid the

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586886#comment-16586886 ] lambdaliu commented on KAFKA-7190: -- Hi [~hachikuji], sorry for the later reply. I have thought about

[jira] [Commented] (KAFKA-5587) Processor got uncaught exception: NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567718#comment-16567718 ] lambdaliu commented on KAFKA-5587: -- Hi [~rsivaram], I found this issue still appears in version

[jira] [Updated] (KAFKA-5587) Processor got uncaught exception: NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-5587: - Affects Version/s: 0.10.2.1 > Processor got uncaught exception: NullPointerException >

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564694#comment-16564694 ] lambdaliu commented on KAFKA-7190: -- Hi [~hachikuji], What do you think about the solution of the

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558265#comment-16558265 ] lambdaliu commented on KAFKA-7190: -- Hello [~guozhang]. My team developed a cloud version Kafka and I am

[jira] [Commented] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555730#comment-16555730 ] lambdaliu commented on KAFKA-7190: -- Hello [~mjsax]  [~guozhang], sorry for the late reply. I also agree

[jira] [Assigned] (KAFKA-7190) Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID

[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7190: Assignee: lambdaliu > Under low traffic conditions purging repartition topics cause WARN

[jira] [Comment Edited] (KAFKA-7160) Add check for group ID length

[ https://issues.apache.org/jira/browse/KAFKA-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549162#comment-16549162 ] lambdaliu edited comment on KAFKA-7160 at 7/19/18 12:02 PM: Hi, [~Bitswazsky]

[jira] [Commented] (KAFKA-7160) Add check for group ID length

[ https://issues.apache.org/jira/browse/KAFKA-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16549162#comment-16549162 ] lambdaliu commented on KAFKA-7160: -- Hi, [~Bitswazsky] [~a.bircakovic] Sorry for the late reply.  I have

[jira] [Created] (KAFKA-7160) Add check for group ID length

lambdaliu created KAFKA-7160: Summary: Add check for group ID length Key: KAFKA-7160 URL: https://issues.apache.org/jira/browse/KAFKA-7160 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5409) Providing a custom client-id to the ConsoleProducer tool

[ https://issues.apache.org/jira/browse/KAFKA-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534715#comment-16534715 ] lambdaliu commented on KAFKA-5409: -- Hi [~ppatierno], We also encounter this issue when using

[jira] [Updated] (KAFKA-5409) Providing a custom client-id to the ConsoleProducer tool

[ https://issues.apache.org/jira/browse/KAFKA-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-5409: - Affects Version/s: 1.1.0 1.0.1 > Providing a custom client-id to the

[jira] [Commented] (KAFKA-7120) When Connect throws CONFLICT error for REST requests, it will help to see more details

[ https://issues.apache.org/jira/browse/KAFKA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528659#comment-16528659 ] lambdaliu commented on KAFKA-7120: -- Hi, I am a newbie. I want to get familiar with the contribution

[jira] [Updated] (KAFKA-7120) When Connect throws CONFLICT error for REST requests, it will help to see more details

[ https://issues.apache.org/jira/browse/KAFKA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-7120: - Component/s: KafkaConnect > When Connect throws CONFLICT error for REST requests, it will help to see >

[jira] [Updated] (KAFKA-7120) When Connect throws CONFLICT error for REST requests, it will help to see more details

[ https://issues.apache.org/jira/browse/KAFKA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-7120: - Labels: kafkaconnect (was: connect) > When Connect throws CONFLICT error for REST requests, it will

[jira] [Updated] (KAFKA-7120) When Connect throws CONFLICT error for REST requests, it will help to see more details

[ https://issues.apache.org/jira/browse/KAFKA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-7120: - Labels: (was: kafkaconnect) > When Connect throws CONFLICT error for REST requests, it will help to

[jira] [Assigned] (KAFKA-7120) When Connect throws CONFLICT error for REST requests, it will help to see more details

[ https://issues.apache.org/jira/browse/KAFKA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu reassigned KAFKA-7120: Assignee: lambdaliu > When Connect throws CONFLICT error for REST requests, it will help to see

[jira] [Updated] (KAFKA-7120) When Connect throws CONFLICT error for REST requests, it will help to see more details

[ https://issues.apache.org/jira/browse/KAFKA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lambdaliu updated KAFKA-7120: - Labels: connect (was: ) > When Connect throws CONFLICT error for REST requests, it will help to see >