[
https://issues.apache.org/jira/browse/KAFKA-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-5098.
---
Resolution: Fixed
> KafkaProducer.send() blocks and generates TimeoutException if topic name has
>
[
https://issues.apache.org/jira/browse/KAFKA-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964994#comment-15964994
]
Joel Koshy commented on KAFKA-5011:
---
Yes that is correct - it is rare. I think it's reasonable to close
Joel Koshy created KAFKA-5011:
-
Summary: Replica fetchers may need to down-convert messages during
a selective message format upgrade
Key: KAFKA-5011
URL: https://issues.apache.org/jira/browse/KAFKA-5011
[
https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-4250.
---
Resolution: Fixed
> make ProducerRecord and ConsumerRecord extensible
>
[
https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy reopened KAFKA-4250:
---
cc [~becket_qin] [~nsolis] [~radai]
> make ProducerRecord and ConsumerRecord extensible
>
[
https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-4250:
--
Fix Version/s: 0.10.2.0
> make ProducerRecord and ConsumerRecord extensible
>
[
https://issues.apache.org/jira/browse/KAFKA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-1911:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Log deletion on stopping replicas
Joel Koshy created KAFKA-4409:
-
Summary: ZK consumer shutdown/topic event deadlock
Key: KAFKA-4409
URL: https://issues.apache.org/jira/browse/KAFKA-4409
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645583#comment-15645583
]
Joel Koshy commented on KAFKA-4362:
---
In this specific issue, the coordinator is available, but has moved
[
https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645427#comment-15645427
]
Joel Koshy commented on KAFKA-4362:
---
Sorry - missed this comment. It does not recover because the
[
https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645419#comment-15645419
]
Joel Koshy commented on KAFKA-4381:
---
This is up to you but I definitely agree with Jason that it's
[
https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-4362:
--
Summary: Consumer can fail after reassignment of the offsets topic
partition (was: Offset commits fail
[
https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624520#comment-15624520
]
Joel Koshy commented on KAFKA-4362:
---
Btw, the summary doesn't make it clear that this also affects
Joel Koshy created KAFKA-4362:
-
Summary: Offset commits fail after a partition reassignment
Key: KAFKA-4362
URL: https://issues.apache.org/jira/browse/KAFKA-4362
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-4250.
---
Resolution: Fixed
Assignee: radai rosenblatt
Reviewer: Joel Koshy
Fix
[
https://issues.apache.org/jira/browse/KAFKA-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15583851#comment-15583851
]
Joel Koshy commented on KAFKA-1351:
---
Yes - this is still an issue. cc [~nsolis]
> String.format is very
[
https://issues.apache.org/jira/browse/KAFKA-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-4025.
---
Resolution: Fixed
Assignee: radai rosenblatt
Reviewer: Joel Koshy
Fix
[
https://issues.apache.org/jira/browse/KAFKA-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-4293:
--
Assignee: radai rosenblatt
It turns out we should be able to handle all of our current codecs by
[
https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-3175:
--
Resolution: Fixed
Reviewer: Joel Koshy
Status: Resolved (was: Patch Available)
> topic
[
https://issues.apache.org/jira/browse/KAFKA-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553228#comment-15553228
]
Joel Koshy commented on KAFKA-4254:
---
It seems (2) would still help as there are use-cases which set
[
https://issues.apache.org/jira/browse/KAFKA-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524443#comment-15524443
]
Joel Koshy commented on KAFKA-4207:
---
I have a KIP draft that has been sitting around for a while. I
[
https://issues.apache.org/jira/browse/KAFKA-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511604#comment-15511604
]
Joel Koshy commented on KAFKA-4178:
---
[~junrao] sorry I don't remember, but you might :) It appears the
[
https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-4158.
---
Resolution: Fixed
Pushed to trunk.
Not sure if we need this in 0.9 since there is an easy work-around
[
https://issues.apache.org/jira/browse/KAFKA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-4158:
--
Fix Version/s: 0.10.1.0
> Reset quota to default value if quota override is deleted for a given
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15471686#comment-15471686
]
Joel Koshy commented on KAFKA-4074:
---
Yes - totally missed KAFKA-3175
> Deleting a topic can make it
Joel Koshy created KAFKA-4074:
-
Summary: Deleting a topic can make it unavailable even if
delete.topic.enable is false
Key: KAFKA-4074
URL: https://issues.apache.org/jira/browse/KAFKA-4074
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-4050.
---
Resolution: Fixed
Fix Version/s: 0.10.0.2
0.10.1.0
Pushed to trunk and
[
https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425906#comment-15425906
]
Joel Koshy commented on KAFKA-4050:
---
[~toddpalino] I had left a comment about this on the PR - one
[
https://issues.apache.org/jira/browse/KAFKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423839#comment-15423839
]
Joel Koshy commented on KAFKA-4050:
---
A stack trace should help further clarify. (This is from a thread
[
https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228733#comment-15228733
]
Joel Koshy commented on KAFKA-3494:
---
I'm not sure that the second suggested solution in the description
[
https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-3234:
--
Fix Version/s: (was: 0.10.0.0)
0.10.0.1
> Minor documentation edits: clarify
[
https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2960:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 1018
[
https://issues.apache.org/jira/browse/KAFKA-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-1148.
---
Resolution: Fixed
Fix Version/s: 0.10.0.0
Issue resolved by pull request 1018
[
https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-3197:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk.
> Producer can
[
https://issues.apache.org/jira/browse/KAFKA-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-3298.
---
Resolution: Duplicate
Thanks for the report. KAFKA-3234 addresses this and other such
[
https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168065#comment-15168065
]
Joel Koshy commented on KAFKA-3197:
---
Hi [~fpj] so your suggestion is to preemptively invoke the
[
https://issues.apache.org/jira/browse/KAFKA-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153180#comment-15153180
]
Joel Koshy commented on KAFKA-2670:
---
It should be possible to accomplish this with a custom [consumer
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy closed KAFKA-3088.
-
Thanks for the patches - this has been pushed to trunk and 0.9
> 0.9.0.0 broker crash on receipt of produce
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145738#comment-15145738
]
Joel Koshy commented on KAFKA-3088:
---
[~granthenke] I'm leaving this open for 0.9 (i.e., 0.9.1.0)
>
Joel Koshy created KAFKA-3234:
-
Summary: Minor documentation edits: clarify minISR; some
topic-level configs are missing
Key: KAFKA-3234
URL: https://issues.apache.org/jira/browse/KAFKA-3234
Project:
[
https://issues.apache.org/jira/browse/KAFKA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140105#comment-15140105
]
Joel Koshy commented on KAFKA-2750:
---
[~felixgv] You mean retry with the older protocol? It does not do
[
https://issues.apache.org/jira/browse/KAFKA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-3179:
--
Resolution: Fixed
Fix Version/s: (was: 0.9.0.1)
0.9.1.0
Status:
[
https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130781#comment-15130781
]
Joel Koshy commented on KAFKA-3197:
---
[~enothereska] - the documentation is accurate in that it . The
[
https://issues.apache.org/jira/browse/KAFKA-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15130785#comment-15130785
]
Joel Koshy commented on KAFKA-3197:
---
Sorry - hit enter too soon. "in that it does not specifically say
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111679#comment-15111679
]
Joel Koshy commented on KAFKA-3088:
---
[~aauradkar] can chime in since this is related to code that he
[
https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111675#comment-15111675
]
Joel Koshy commented on KAFKA-2758:
---
Unless I'm misunderstanding I don't think we should do (1) - i.e.,
Joel Koshy created KAFKA-3124:
-
Summary: Update protocol wiki page to reflect latest
request/response formats
Key: KAFKA-3124
URL: https://issues.apache.org/jira/browse/KAFKA-3124
Project: Kafka
Joel Koshy created KAFKA-2863:
-
Summary: Authorizer should provide lifecycle (shutdown) methods
Key: KAFKA-2863
URL: https://issues.apache.org/jira/browse/KAFKA-2863
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2664.
---
Resolution: Fixed
Fix Version/s: (was: 0.9.0.1)
0.9.0.0
Issue resolved
[
https://issues.apache.org/jira/browse/KAFKA-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2663.
---
Resolution: Fixed
Fix Version/s: (was: 0.9.0.1)
0.9.0.0
Issue resolved
[
https://issues.apache.org/jira/browse/KAFKA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974502#comment-14974502
]
Joel Koshy commented on KAFKA-2235:
---
Agreed with Todd - this is very similar to the proposal in btw,
[
https://issues.apache.org/jira/browse/KAFKA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971728#comment-14971728
]
Joel Koshy commented on KAFKA-2235:
---
While I think the change is well-motivated I'm not sure this is the
[
https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2454:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 153
Joel Koshy created KAFKA-2663:
-
Summary: Add quota-delay time to request processing time break-up
Key: KAFKA-2663
URL: https://issues.apache.org/jira/browse/KAFKA-2663
Project: Kafka
Issue Type:
Joel Koshy created KAFKA-2664:
-
Summary: Adding a new metric with several pre-existing metrics is
very expensive
Key: KAFKA-2664
URL: https://issues.apache.org/jira/browse/KAFKA-2664
Project: Kafka
Joel Koshy created KAFKA-2668:
-
Summary: Add a metric that records the total number of metrics
Key: KAFKA-2668
URL: https://issues.apache.org/jira/browse/KAFKA-2668
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14961595#comment-14961595
]
Joel Koshy commented on KAFKA-2664:
---
[~gwenshap] in general yes it could, but if we did register
[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958442#comment-14958442
]
Joel Koshy commented on KAFKA-2017:
---
Ashish, that is correct - consumers can still remain detached from
[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959266#comment-14959266
]
Joel Koshy commented on KAFKA-2017:
---
bq. But if we really want to have group metadata persisted in 0.9
[
https://issues.apache.org/jira/browse/KAFKA-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2660:
--
Reviewer: Joel Koshy
> Correct cleanableRatio calculation
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959392#comment-14959392
]
Joel Koshy commented on KAFKA-2017:
---
btw, I just realized a migration as described above probably won't
[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14957348#comment-14957348
]
Joel Koshy commented on KAFKA-2017:
---
If we reused this topic, then I think we could end up doing
[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14957204#comment-14957204
]
Joel Koshy commented on KAFKA-2017:
---
I agree with those benefits. If we go that route then I would
[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14956108#comment-14956108
]
Joel Koshy commented on KAFKA-2017:
---
In offline threads we were going to discuss the options of
[
https://issues.apache.org/jira/browse/KAFKA-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2567.
---
Resolution: Fixed
Issue resolved by pull request 213
[https://github.com/apache/kafka/pull/213]
>
[
https://issues.apache.org/jira/browse/KAFKA-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2443.
---
Resolution: Fixed
Fix Version/s: 0.9.0.0
Issue resolved by pull request 213
[
https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2419.
---
Resolution: Fixed
> Allow certain Sensors to be garbage collected after inactivity
>
[
https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943698#comment-14943698
]
Joel Koshy commented on KAFKA-2580:
---
I was wondering if we can do with something much simpler -
[
https://issues.apache.org/jira/browse/KAFKA-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943694#comment-14943694
]
Joel Koshy commented on KAFKA-2584:
---
Here is a quick summary of the patch we ended up applying at
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2120:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
+1 and committed to trunk.
> Add a
[
https://issues.apache.org/jira/browse/KAFKA-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933781#comment-14933781
]
Joel Koshy commented on KAFKA-2580:
---
[~guozhang] actually it is now at 400k.
[~vinothchandar] yes that
Joel Koshy created KAFKA-2584:
-
Summary: SecurityProtocol enum validation should be removed or
relaxed for non-config usages
Key: KAFKA-2584
URL: https://issues.apache.org/jira/browse/KAFKA-2584
Project:
[
https://issues.apache.org/jira/browse/KAFKA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903046#comment-14903046
]
Joel Koshy edited comment on KAFKA-1911 at 9/22/15 5:34 PM:
The original
[
https://issues.apache.org/jira/browse/KAFKA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903046#comment-14903046
]
Joel Koshy commented on KAFKA-1911:
---
The original motivation in this ticket was to avoid a high latency
[
https://issues.apache.org/jira/browse/KAFKA-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876545#comment-14876545
]
Joel Koshy commented on KAFKA-2438:
---
FYI, I find that this patch appears to exacerbate timing-related
[
https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875986#comment-14875986
]
Joel Koshy commented on KAFKA-2419:
---
However, we should think through the effect of doing this. i.e.,
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803291#comment-14803291
]
Joel Koshy commented on KAFKA-2120:
---
I see test failures on b7d4043d8da1d296519faf321e9f0f7188d7d67a as
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804570#comment-14804570
]
Joel Koshy commented on KAFKA-2120:
---
Actually some of the confusion on my side is because I was running
[
https://issues.apache.org/jira/browse/KAFKA-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804600#comment-14804600
]
Joel Koshy commented on KAFKA-2552:
---
Reported in KAFKA-1599 as well?
> Certain admin commands such as
[
https://issues.apache.org/jira/browse/KAFKA-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804835#comment-14804835
]
Joel Koshy commented on KAFKA-1215:
---
[~allenxwang] you should have access now.
> Rack-Aware replica
[
https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804893#comment-14804893
]
Joel Koshy commented on KAFKA-2419:
---
Re: the options in
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791049#comment-14791049
]
Joel Koshy commented on KAFKA-2120:
---
Yes I did note failures in the RB, but those were on trunk as well
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy reopened KAFKA-2120:
---
> Add a request timeout to NetworkClient
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791284#comment-14791284
]
Joel Koshy commented on KAFKA-2120:
---
Hmm.. actually after rerunning tests I'm not sure this patch is not
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2120:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks [~mgharat] for the patch, and
[
https://issues.apache.org/jira/browse/KAFKA-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739774#comment-14739774
]
Joel Koshy commented on KAFKA-2529:
---
Yes this was done in KAFKA-1901, but one issue is that the above is
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14739766#comment-14739766
]
Joel Koshy commented on KAFKA-2120:
---
Thanks for the updated patch - I will review again later today
>
[
https://issues.apache.org/jira/browse/KAFKA-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2502:
--
Description:
Complete quotas documentation
Also,
[
https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2437.
---
Resolution: Fixed
Fix Version/s: 0.8.3
> Controller does not handle zk node deletion
[
https://issues.apache.org/jira/browse/KAFKA-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2332:
--
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
Issue
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2120:
--
Status: In Progress (was: Patch Available)
Add a request timeout to NetworkClient
[
https://issues.apache.org/jira/browse/KAFKA-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2351:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk.
Brokers are
[
https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712324#comment-14712324
]
Joel Koshy commented on KAFKA-2136:
---
Thanks for the patches - pushed to trunk. Can you
[
https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14707091#comment-14707091
]
Joel Koshy commented on KAFKA-2454:
---
Thanks - got it. Will take a look at your patch
[
https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-2442:
--
Reviewer: Joel Koshy
will do
QuotasTest should not fail when cpu is busy
[
https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14706019#comment-14706019
]
Joel Koshy commented on KAFKA-2454:
---
I'm a bit unclear on the root cause that you
[
https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-1901:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the patch - committed to
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703921#comment-14703921
]
Joel Koshy commented on KAFKA-2084:
---
I pushed a trivial commit to address this. However,
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703965#comment-14703965
]
Joel Koshy commented on KAFKA-2084:
---
Actually I did not mean full-fledged
[
https://issues.apache.org/jira/browse/KAFKA-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy resolved KAFKA-2446.
---
Resolution: Fixed
Pushed to trunk.
KAFKA-2205 causes existing Topic config changes to be lost
1 - 100 of 741 matches
Mail list logo
