RE?? [DISCUSS] KIP-148: Add a connect timeout for client

Hi Guozhang, Thanks for the clarify. For the clarify 2, I think the key thing is not users control how much time in maximum to wait for inside code, but is the network client can be aware of the connecting can't be finished and try a good node. In the producer.sender even the selector.poll can

[GitHub] kafka pull request #2991: KAFKA-4208: Add Record Headers

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2991 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4208) Add Record Headers

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

[GitHub] kafka pull request #2638: KAFKA-3995: fix compression ratio estimation.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2638 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

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

[GitHub] kafka pull request #3112: HOTFIX: In Connect test with auto topic creation d...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/3112 HOTFIX: In Connect test with auto topic creation disabled, ensure precreated topic is always used You can merge this pull request into a Git repository by running: $ git pull https://github.co

[GitHub] kafka pull request #3113: KAFKA-5186: Avoid expensive log scan to build prod...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3113 KAFKA-5186: Avoid expensive log scan to build producer state when upgrading You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KA

[jira] [Commented] (KAFKA-5186) Avoid expensive initialization of producer state when upgrading

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

[jira] [Updated] (KAFKA-5186) Avoid expensive initialization of producer state when upgrading

[ https://issues.apache.org/jira/browse/KAFKA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5186: --- Status: Patch Available (was: In Progress) > Avoid expensive initialization of producer state

[GitHub] kafka pull request #3112: HOTFIX: In Connect test with auto topic creation d...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3112 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] kafka pull request #2765: MINOR: Fix race condition in TestVerifiableProduce...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2765 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-5299) MirrorMaker with New.consumer doesn't consume message from multiple topics whitelisted

[ https://issues.apache.org/jira/browse/KAFKA-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019072#comment-16019072 ] huxi commented on KAFKA-5299: - How did you specify the whitelist? It should be a valid regular

[jira] [Commented] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019074#comment-16019074 ] huxi commented on KAFKA-5296: - With 0.10.2 client, could you try to enlarge `request.timeout.m

[jira] [Updated] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Fix Version/s: 0.11.0.0 > Split the ProducerBatch and resend when received RecordTooLargeException >

[jira] [Updated] (KAFKA-3995) Split the ProducerBatch and resend when received RecordTooLargeException

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3995: Resolution: Fixed Status: Resolved (was: Patch Available) > Split the ProducerBatch and res

[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&focusedCommentId=16019115#comment-16019115 ] Qingsong Xie commented on KAFKA-5153: - [~arpan.khagram0...@gmail.com] Hi, did this iss

[jira] [Commented] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019117#comment-16019117 ] Guozhang Wang commented on KAFKA-3502: -- Have not seen this happen again since KAFKA-5

[jira] [Updated] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3502: - Component/s: unit tests > Build is killed during kafka streams tests due to `pure virtual method

[jira] [Updated] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3502: - Component/s: streams > Build is killed during kafka streams tests due to `pure virtual method > c

[jira] [Updated] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5063: - Labels: unit-test (was: ) > Flaky > ResetIntegrationTest.testReprocessingFromScratchAfterResetWi

[GitHub] kafka pull request #2974: KAFKA-4923: Add Exaclty-Once Semantics to Streams ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2974 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4923) Add Exactly-Once Semantics to Streams

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

[jira] [Commented] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

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

[GitHub] kafka pull request #3114: KAFKA-5211: Do not skip a corrupted record in cons...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/3114 KAFKA-5211: Do not skip a corrupted record in consumer You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-5211 Alternative

[jira] [Updated] (KAFKA-5211) KafkaConsumer should not skip a corrupted record after throwing an exception.

[ https://issues.apache.org/jira/browse/KAFKA-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5211: Status: Patch Available (was: In Progress) > KafkaConsumer should not skip a corrupted record after

[jira] [Updated] (KAFKA-5134) Replace zkClient.getChildren method with zkUtils.getChildren

[ https://issues.apache.org/jira/browse/KAFKA-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-5134: - Status: Patch Available (was: In Progress) > Replace zkClient.getChildren method with zkUtils.get