[
https://issues.apache.org/jira/browse/KAFKA-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019149#comment-16019149
]
ASF GitHub Bot commented on KAFKA-4923:
---
Github user asfgit closed the pull request at:
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
[
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
>
[
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
>
[
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
[
https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019117#comment-16019117
]
Guozhang Wang commented on KAFKA-3502:
--
Have not seen this happen again since KAFKA-5198 is merged,
[
https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019115#comment-16019115
]
Qingsong Xie commented on KAFKA-5153:
-
[~arpan.khagram0...@gmail.com] Hi, did this issue occur again?
[
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019074#comment-16019074
]
huxi commented on KAFKA-5296:
-
With 0.10.2 client, could you try to enlarge `request.timeout.ms` a little bit
[
https://issues.apache.org/jira/browse/KAFKA-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019072#comment-16019072
]
huxi commented on KAFKA-5299:
-
How did you specify the whitelist? It should be a valid regular expression.
>
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
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
[
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
[
https://issues.apache.org/jira/browse/KAFKA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019054#comment-16019054
]
ASF GitHub Bot commented on KAFKA-5186:
---
GitHub user hachikuji opened a pull request:
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
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://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019046#comment-16019046
]
ASF GitHub Bot commented on KAFKA-3995:
---
Github user asfgit closed the pull request at:
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
[
https://issues.apache.org/jira/browse/KAFKA-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018987#comment-16018987
]
ASF GitHub Bot commented on KAFKA-4208:
---
Github user asfgit closed the pull request at:
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
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
22 matches
Mail list logo
