[
https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1870:
---
Attachment: kafka-1870_2015-01-16_12:08:05.patch
> Cannot commit with simpleConsumer on Zookeeper only with Ja
[
https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280756#comment-14280756
]
Jun Rao commented on KAFKA-1870:
Updated reviewboard https://reviews.apache.org/r/29977/di
[
https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280768#comment-14280768
]
Jun Rao commented on KAFKA-1870:
I think it makes sense to pin the version of OffsetCommit
[
https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1870:
---
Priority: Blocker (was: Minor)
Fix Version/s: 0.8.2
Marking this as an 0.8.2 blocker.
> Cannot comm
[
https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1870:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the reviews. Committed to 0.8.2
[
https://issues.apache.org/jira/browse/KAFKA-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281166#comment-14281166
]
Jun Rao commented on KAFKA-1723:
Actually committed the delta patch to 0.8.2 as well.
> m
[
https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1864:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the reviews. Committed to 0.8.2
[
https://issues.apache.org/jira/browse/KAFKA-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281175#comment-14281175
]
Jun Rao commented on KAFKA-1867:
When fixing this, we should remove the TODO items in
Pro
[
https://issues.apache.org/jira/browse/KAFKA-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1846.
Resolution: Duplicate
Fix Version/s: (was: 0.8.3)
Duplicate of KAFKA-1864.
> Offset storage topi
[
https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281182#comment-14281182
]
Jun Rao commented on KAFKA-1864:
Yes, thanks for the reminder.
> Revisit defaults for the
[
https://issues.apache.org/jira/browse/KAFKA-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281429#comment-14281429
]
Jun Rao commented on KAFKA-1872:
Done for both wiki and jira.
> Update Developer Setup
>
[
https://issues.apache.org/jira/browse/KAFKA-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281433#comment-14281433
]
Jun Rao commented on KAFKA-1873:
Hmm, our build script is the following. It explicitly spe
[
https://issues.apache.org/jira/browse/KAFKA-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281436#comment-14281436
]
Jun Rao commented on KAFKA-1870:
Yes, the scala one still defaults to version 1. This is a
[
https://issues.apache.org/jira/browse/KAFKA-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1872:
---
Assignee: Sree Vaddi
> Update Developer Setup
> --
>
> Key: KAFKA-1872
>
[
https://issues.apache.org/jira/browse/KAFKA-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282056#comment-14282056
]
Jun Rao commented on KAFKA-1866:
I think deleting a topic probably can reproduce the issue
[
https://issues.apache.org/jira/browse/KAFKA-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282073#comment-14282073
]
Jun Rao commented on KAFKA-1855:
This could be related to KAFKA-1738. Could you try the la
Jun Rao created KAFKA-1876:
--
Summary: pom file for scala 2.11 should reference a specific
version
Key: KAFKA-1876
URL: https://issues.apache.org/jira/browse/KAFKA-1876
Project: Kafka
Issue Type: Bu
[
https://issues.apache.org/jira/browse/KAFKA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1876:
---
Status: Patch Available (was: Open)
> pom file for scala 2.11 should reference a specific version
> -
[
https://issues.apache.org/jira/browse/KAFKA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1876:
---
Attachment: kafka-1876.patch
> pom file for scala 2.11 should reference a specific version
> -
[
https://issues.apache.org/jira/browse/KAFKA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282083#comment-14282083
]
Jun Rao commented on KAFKA-1876:
Created reviewboard https://reviews.apache.org/r/30019/di
[
https://issues.apache.org/jira/browse/KAFKA-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1761:
---
Resolution: Fixed
Fix Version/s: 0.8.2
Status: Resolved (was: Patch Available)
Thanks for t
[
https://issues.apache.org/jira/browse/KAFKA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282685#comment-14282685
]
Jun Rao commented on KAFKA-1728:
Thanks for the update. Could you attach a patch against
[
https://issues.apache.org/jira/browse/KAFKA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1878:
---
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
Thanks for t
[
https://issues.apache.org/jira/browse/KAFKA-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282868#comment-14282868
]
Jun Rao commented on KAFKA-1874:
You need to add the dependency to scala-parser-combinator
[
https://issues.apache.org/jira/browse/KAFKA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1876:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the reviews. Committed to 0.8.2
Jun Rao created KAFKA-1881:
--
Summary: transient unit test failure in testDeleteTopicWithCleaner
due to OOME
Key: KAFKA-1881
URL: https://issues.apache.org/jira/browse/KAFKA-1881
Project: Kafka
Issu
[
https://issues.apache.org/jira/browse/KAFKA-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282917#comment-14282917
]
Jun Rao commented on KAFKA-1881:
Perhaps we can just reduce the amount of data written in
[
https://issues.apache.org/jira/browse/KAFKA-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1879:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the patch. +1. Committed to 0.8.
[
https://issues.apache.org/jira/browse/KAFKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283216#comment-14283216
]
Jun Rao commented on KAFKA-1824:
Gwen, thanks for point this out. I am reverting KAFKA-171
[
https://issues.apache.org/jira/browse/KAFKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reopened KAFKA-1824:
Reopening the issue since the followup patch hasn't been committed yet.
> in ConsoleProducer - properties key.s
[
https://issues.apache.org/jira/browse/KAFKA-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283419#comment-14283419
]
Jun Rao commented on KAFKA-1881:
Not sure id writeDups is causing the issue. I just ran gr
[
https://issues.apache.org/jira/browse/KAFKA-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1337.
Resolution: Fixed
Fix Version/s: 0.8.2
The followup patch has been committed to 0.8.2. Resolving the
Jun Rao created KAFKA-1887:
--
Summary: controller error message on shutting the last broker
Key: KAFKA-1887
URL: https://issues.apache.org/jira/browse/KAFKA-1887
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284502#comment-14284502
]
Jun Rao commented on KAFKA-1887:
When shutting down the broker, we unregister the broker f
[
https://issues.apache.org/jira/browse/KAFKA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285029#comment-14285029
]
Jun Rao commented on KAFKA-1728:
Thanks for the patch. +1 and committed to site.
1. Yes,
[
https://issues.apache.org/jira/browse/KAFKA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1674.
Resolution: Duplicate
This is fixed in KAFKA-1728.
> auto.create.topics.enable docs are misleading
> --
[
https://issues.apache.org/jira/browse/KAFKA-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286158#comment-14286158
]
Jun Rao commented on KAFKA-1728:
Thanks for the patch for missing configs . +1 and committ
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286651#comment-14286651
]
Jun Rao commented on KAFKA-1729:
[~jjkoshy], are you on track to complete the doc for the
[
https://issues.apache.org/jira/browse/KAFKA-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286676#comment-14286676
]
Jun Rao commented on KAFKA-1697:
>From the discussion in the mailing list, we decided not
[
https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286763#comment-14286763
]
Jun Rao commented on KAFKA-1634:
I guess you mean rebasing KAFAK-1841, instead of KAFKA-14
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289595#comment-14289595
]
Jun Rao commented on KAFKA-1729:
Do you mean that you need to make code changes in the 0.8
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290132#comment-14290132
]
Jun Rao commented on KAFKA-1729:
[~jjkoshy], thanks for the update. Yes, I agree that we d
Jun Rao created KAFKA-1902:
--
Summary: fix MetricName so that Yammer reporter can work correctly
Key: KAFKA-1902
URL: https://issues.apache.org/jira/browse/KAFKA-1902
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293747#comment-14293747
]
Jun Rao commented on KAFKA-1902:
Created reviewboard https://reviews.apache.org/r/30321/di
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1902:
---
Status: Patch Available (was: Open)
> fix MetricName so that Yammer reporter can work correctly
> ---
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1902:
---
Attachment: kafka-1902.patch
> fix MetricName so that Yammer reporter can work correctly
> ---
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293794#comment-14293794
]
Jun Rao commented on KAFKA-1902:
The fix is to use tag name as the scope. So, we will have
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293919#comment-14293919
]
Jun Rao commented on KAFKA-1902:
Thanks for the explanation. A couple of things: (1) Since
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294195#comment-14294195
]
Jun Rao commented on KAFKA-1902:
Topic and clientId allow underscores too. How about repla
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294286#comment-14294286
]
Jun Rao commented on KAFKA-1902:
Is graphite the only reporter using scope? t seems that t
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294289#comment-14294289
]
Jun Rao commented on KAFKA-1902:
In Kafka, topic/group/clientId can include only -, _ and
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294299#comment-14294299
]
Jun Rao commented on KAFKA-1902:
clientId is useful because one may want to run multiple p
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294474#comment-14294474
]
Jun Rao commented on KAFKA-1902:
Making the replacing character configurable is actually n
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295420#comment-14295420
]
Jun Rao commented on KAFKA-1902:
Updated reviewboard https://reviews.apache.org/r/30321/di
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1902:
---
Attachment: kafka-1902_2015-01-28_09:23:51.patch
> fix MetricName so that Yammer reporter can work correctly
>
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295435#comment-14295435
]
Jun Rao commented on KAFKA-1902:
It seems that the ganglia reporter replaces anything othe
[
https://issues.apache.org/jira/browse/KAFKA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296176#comment-14296176
]
Jun Rao commented on KAFKA-1904:
Does this happen on 0.8.2 too?
> run sanity failed test
[
https://issues.apache.org/jira/browse/KAFKA-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1902:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the reviews. Committed to 0.8.2
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296205#comment-14296205
]
Jun Rao commented on KAFKA-1729:
Joel, thanks for the patch. +1 and committed to 0.8.2. Th
[
https://issues.apache.org/jira/browse/KAFKA-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1861:
---
Resolution: Fixed
Fix Version/s: 0.8.2
Status: Resolved (was: Patch Available)
Thanks for t
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301736#comment-14301736
]
Jun Rao commented on KAFKA-1729:
Joel,
Thanks for the doc. Looks good. Just a few minor c
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303446#comment-14303446
]
Jun Rao commented on KAFKA-1729:
[~jjkoshy], for 0.8.2, we can probably just update the do
[
https://issues.apache.org/jira/browse/KAFKA-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305733#comment-14305733
]
Jun Rao commented on KAFKA-1730:
[~omkreddy], could you add those mbeans for the new produ
[
https://issues.apache.org/jira/browse/KAFKA-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1730.
Resolution: Fixed
Assignee: Manikumar Reddy
Thanks for the metrics doc patch. +1 and committed to site
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Attachment: kafka-1952.patch
> High CPU Usage in 0.8.2 release
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321131#comment-14321131
]
Jun Rao commented on KAFKA-1952:
The issue is that after purgatory refactoring, we make a
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Status: Patch Available (was: Open)
> High CPU Usage in 0.8.2 release
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321130#comment-14321130
]
Jun Rao commented on KAFKA-1952:
Created reviewboard https://reviews.apache.org/r/31040/di
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322244#comment-14322244
]
Jun Rao commented on KAFKA-1952:
Updated reviewboard https://reviews.apache.org/r/31040/di
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Attachment: kafka-1952_2015-02-15_15:26:33.patch
> High CPU Usage in 0.8.2 release
> -
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322246#comment-14322246
]
Jun Rao commented on KAFKA-1952:
Uploaded a new patch that addresses the review comments.
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Fix Version/s: (was: 0.8.2.0)
0.8.2.1
> High CPU Usage in 0.8.2 release
> -
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325435#comment-14325435
]
Jun Rao commented on KAFKA-1952:
Created reviewboard https://reviews.apache.org/r/31150/di
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Attachment: kafka-1952.patch
> High CPU Usage in 0.8.2 release
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325439#comment-14325439
]
Jun Rao commented on KAFKA-1952:
Attach a patch for trunk. The CPU load and the end to end
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the review. Committed to 0.8.2.1
Jun Rao created KAFKA-1964:
--
Summary: testPartitionReassignmentCallback hangs occasionally
Key: KAFKA-1964
URL: https://issues.apache.org/jira/browse/KAFKA-1964
Project: Kafka
Issue Type: Bug
A
[
https://issues.apache.org/jira/browse/KAFKA-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1964:
---
Attachment: stack.out
Saw the test hang once in trunk. Attached is the full stacktrace.
"Test worker" prio=5
[
https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326883#comment-14326883
]
Jun Rao commented on KAFKA-1729:
Thanks for the patch. Pushed the change to 0.8.2. Could y
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328371#comment-14328371
]
Jun Rao commented on KAFKA-1952:
There is a separate patch for 0.8.2 and is always committ
Jun Rao created KAFKA-1971:
--
Summary: starting a broker with a conflicting id will delete the
previous broker registration
Key: KAFKA-1971
URL: https://issues.apache.org/jira/browse/KAFKA-1971
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329154#comment-14329154
]
Jun Rao commented on KAFKA-1971:
This issue is that when broker 2's ZK registration fails,
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329157#comment-14329157
]
Jun Rao commented on KAFKA-1971:
A simple fix is not to explicitly delete the broker regis
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329327#comment-14329327
]
Jun Rao commented on KAFKA-1971:
[~guozhang], the explicit de-registration was added in KA
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329675#comment-14329675
]
Jun Rao commented on KAFKA-1971:
[~gwenshap], what you said only applies to the case when
[
https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao closed KAFKA-1419.
--
> cross build for scala 2.11
> --
>
> Key: KAFKA-1419
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329842#comment-14329842
]
Jun Rao commented on KAFKA-1419:
The fix will be included in 0.8.2.x. Closing the jira.
>
[
https://issues.apache.org/jira/browse/KAFKA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1969:
---
Attachment: stack.out
Also, saw the test fail occasionally. Attached is the stack trace.
> NPE in unit test f
Jun Rao created KAFKA-1975:
--
Summary: testGroupConsumption occasionally hang
Key: KAFKA-1975
URL: https://issues.apache.org/jira/browse/KAFKA-1975
Project: Kafka
Issue Type: Bug
Affects Versions
[
https://issues.apache.org/jira/browse/KAFKA-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1975:
---
Attachment: stack.out
Attached is the stack trace. This may be related to KAFKA-1969.
> testGroupConsumption
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330334#comment-14330334
]
Jun Rao commented on KAFKA-1971:
Attach a fix in the following RB against trunk.
https://
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1971:
---
Assignee: Jun Rao
Status: Patch Available (was: Open)
> starting a broker with a conflicting id will de
Jun Rao created KAFKA-1976:
--
Summary: transient unit test failure in
ProducerFailureHandlingTest.testNotEnoughReplicasAfterBrokerShutdown
Key: KAFKA-1976
URL: https://issues.apache.org/jira/browse/KAFKA-1976
[
https://issues.apache.org/jira/browse/KAFKA-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332513#comment-14332513
]
Jun Rao commented on KAFKA-1976:
I suspect the issue is the following: Since broker failur
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1971:
---
Attachment: kafka-1971_2015-02-22_21:11:52.patch
> starting a broker with a conflicting id will delete the pre
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333012#comment-14333012
]
Jun Rao commented on KAFKA-1971:
Updated reviewboard https://reviews.apache.org/r/31260/di
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333015#comment-14333015
]
Jun Rao commented on KAFKA-1971:
It seems that the reason why we explicitly delete the bro
[
https://issues.apache.org/jira/browse/KAFKA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1971:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the review. Double committed to
Jun Rao created KAFKA-1982:
--
Summary: change kafka.examples.Producer to use the new java
producer
Key: KAFKA-1982
URL: https://issues.apache.org/jira/browse/KAFKA-1982
Project: Kafka
Issue Type: Im
Jun Rao created KAFKA-1983:
--
Summary: TestEndToEndLatency can be unreliable after hard kill
Key: KAFKA-1983
URL: https://issues.apache.org/jira/browse/KAFKA-1983
Project: Kafka
Issue Type: Improveme
501 - 600 of 3542 matches
Mail list logo
