[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Ye updated KAFKA-343:
--
Attachment: kafka_343.diff.6
I've made changes to the waitUntilLeaderIsElectedOrChanged() to
waitUntilLiveLeade
Is there a producer someplace that implements the proposed kafka-audit
messages?
https://issues.apache.org/jira/browse/KAFKA-260
-Jonathan
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Ye updated KAFKA-343:
--
Attachment: (was: kafka_controller_v5.patch)
> revisit the become leader and become follower state chang
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Ye updated KAFKA-343:
--
Attachment: kafka_343.diff.5
> revisit the become leader and become follower state change operations using
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-181:
--
Affects Version/s: 0.8
Status: Patch Available (was: Open)
Attach patch v1. Added a wrapper clas
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-181:
--
Attachment: kafka_181_v1.patch
> Log errors for unrecognized config options
> --
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-181:
-
Assignee: Jun Rao
> Log errors for unrecognized config options
> -
I was originally going to follow this was a [VOTE] thread, but most of
the responses are a +1 anyway. I think we can do this and it will be a
significant improvement. I'll follow up with INFRA this week.
We don't have to do this, or do it now. So if anyone does have concerns
please do speak up.
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jian fan updated KAFKA-411:
---
Attachment: (was: InvalidTopic.patch)
> Message Error in high cocurrent environment
>
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jian fan updated KAFKA-411:
---
Attachment: kafka-411.patch
> Message Error in high cocurrent environment
> --
[
https://issues.apache.org/jira/browse/KAFKA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Ye updated KAFKA-343:
--
Attachment: kafka_controller_v5.patch
50. RequestSendThread.run(): Not sure if we need to handle
AsynchronousCl
[
https://issues.apache.org/jira/browse/KAFKA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Howard updated KAFKA-278:
--
Attachment: bootstrap_new_brokers.patch
Here's a patch we applied to our fork to deal with this issue.
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425294#comment-13425294
]
Jun Rao commented on KAFKA-384:
---
+1 on v2 too.
> Fix intermittent test failu
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425274#comment-13425274
]
Jay Kreps commented on KAFKA-384:
-
You are my hero...
> Fix intermittent t
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425221#comment-13425221
]
Joel Koshy commented on KAFKA-384:
--
+1 for v2.
> Fix intermittent test fa
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-384:
Attachment: kafka-384-v2.patch
Thanks for the review, Jun. That is a good point. I fixed that and al
[
https://issues.apache.org/jira/browse/KAFKA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425180#comment-13425180
]
Jun Rao commented on KAFKA-384:
---
Thanks for the patch. It looks good. Just 1 comment:
1. Asy
Issue Subscription
Filter: outstanding kafka patches (45 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-425 Wrong class name in performance test scripts
https://issues.apache.org/jira/browse/KAFKA-425
KAFKA-424 Remove
[
https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425024#comment-13425024
]
Jun Rao commented on KAFKA-376:
---
Prashanth,
Thanks for the patch. Some comments:
1. In Kafk
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424952#comment-13424952
]
Jun Rao commented on KAFKA-411:
---
Thanks for the patch. It may not be the right fix though sin
Just to throw in (an admittedly external) $0.02: with Git, at least, *everyone*
has a full copy of the repo, +/- local changes, so even a catastrophic failure
of the apache Git servers would still allow a reconstruct of the repo elsewhere
(say GitHub, or a different apache server). AFAIK, this i
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424769#comment-13424769
]
jian fan commented on KAFKA-411:
In high cocurrent environment, the tcp server will drop so
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jian fan updated KAFKA-411:
---
Attachment: InvalidTopic.patch
In high cocurrent environment, the tcp server will drop some package when the
[
https://issues.apache.org/jira/browse/KAFKA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jian fan updated KAFKA-411:
---
Fix Version/s: 0.7.2
0.8
Labels: InvalidTopic (was: )
Status: Patch A
24 matches
Mail list logo
