Hi both,
Thanks for the replies. A few points:
1. It's worth emphasising that reassigning partitions is a different
process than what happens when a topic is created, so not sure trying to
make it symmetric is beneficial. In addition to what was already discussed,
one should also enable replicati
ter.com/ppatierno>
> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>
>
>
> From: isma...@gmail.com on behalf of Ismael Juma <
> ism...@juma.me.uk>
> Sent: Tuesday, Aug
Hi Paolo,
Another option is to write the new tool in Java without support for
`--zookeeper` and include some logic in the shell script to pick the
implementation based on the presence of `--bootstrap-server` or
`--zookeeper`. This would mean that we can deprecate the Scala tool while
still support
Hi Tom,
A high-level point for discussion before going into the details. The
proposed protocol API `alterTopics` has 2 types of operations:
1. Operations that cause data movement (or deletion): increase/decrease of
replication factor and partition reassignment. These are currently done by
`kafka-
Ismael Juma created KAFKA-5647:
--
Summary: Use async ZookeeperClient for Admin operations
Key: KAFKA-5647
URL: https://issues.apache.org/jira/browse/KAFKA-5647
Project: Kafka
Issue Type: Sub
Ismael Juma created KAFKA-5646:
--
Summary: Use async ZookeeperClient for Config and ISR management
Key: KAFKA-5646
URL: https://issues.apache.org/jira/browse/KAFKA-5646
Project: Kafka
Issue Type
Ismael Juma created KAFKA-5645:
--
Summary: Use async ZookeeperClient in SimpleAclAuthorizer
Key: KAFKA-5645
URL: https://issues.apache.org/jira/browse/KAFKA-5645
Project: Kafka
Issue Type: Sub
[
https://issues.apache.org/jira/browse/KAFKA-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5328.
Resolution: Duplicate
Duplicate of KAFKA-1595.
> consider switching json parser from scala
[
https://issues.apache.org/jira/browse/KAFKA-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3210.
Resolution: Won't Fix
We are following a slightly different approach, see KAFKA-5501.
&g
[
https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-5501:
> use async zookeeper apis everywhere
> ---
>
>
ort older
> releases
> > > > longer and do bug fix release for older releases, too.
> > > >
> > > > Other projects (like Flink) do a fantastic job with this regard and
> we
> > > > should learn from them.
> > > >
> > > > -Matthias
> > >
Ismael Juma created KAFKA-5637:
--
Summary: Document compatibility and release policies
Key: KAFKA-5637
URL: https://issues.apache.org/jira/browse/KAFKA-5637
Project: Kafka
Issue Type
> My two cents:
> > > > > >
> > > > > > "Dead" and "Empty" states are transient: groups usually only
> > leaves in
> > > > > this
> > > > > > state for a short while and then being deleted or transited to
On Tue, Jul 18, 2017 at 4:04 PM, Guozhang Wang wrote:
> I was actually thinking about using dot as well for the rc as well moving
> forward, but I can be convinced if we have some reason to keep it as dash
> as well.
It seems reasonable to use a dash for the RC part as it's a qualifier that
is
dy exists: alterConfigs().
>
> This API is better than having separate methods to set the number of
> partitions/replicas and assigning them to brokers, since sometimes people
> will want to set the assignment at the same time as changing the
> partitions/replicas.
>
> An API like t
> > "Dead" and "Empty" states are transient: groups usually only
> leaves in
> > > > this
> > > > > state for a short while and then being deleted or transited to
> other
> > > > > states.
> > > > >
>
Hi Tom,
I think it makes sense to keep progress reporting simple in the initial
version. As you say, time to completion is tricky to compute and it seems
like it should be tackled as its own KIP.
Regarding waiting for reassignment completion, it's easy enough for people
to do that via a script, s
Ismael Juma created KAFKA-5631:
--
Summary: Use Jackson for serialising to JSON
Key: KAFKA-5631
URL: https://issues.apache.org/jira/browse/KAFKA-5631
Project: Kafka
Issue Type: Improvement
ciding what's the version number of the next major release does not
> necessarily mean we need now to change any of these or to set the hard
> rules along with it; I'd like to keep them as two separate discussions as
> they seem semi-orthogonal to me.
>
>
> Guozhang
>
d for. Current clients support 0.10.x
and newer brokers.
7. How long are message formats supported for. We never discussed this. I
think 5 years would probably be the minimum.
Ismael
P.S. I'll file a JIRA to capture this information.
On Wed, Jul 19, 2017 at 10:12 AM, Ismael Juma wrote:
Thanks for the KIP, Colin. This will definitely be useful. One question:
would it be useful to have a metric for for the number of groups in each
possible state? The KIP suggests "PreparingRebalance" and "AwaitingSync".
That leaves "Stable", "Dead" and "Empty". Are those not useful?
Ismael
On Thu
Thanks for reporting the results. Maybe you could submit a PR that updates
the ops section?
https://github.com/apache/kafka/blob/trunk/docs/ops.html
Ismael
On Fri, Jul 21, 2017 at 2:49 PM, Ovidiu-Cristian MARCU <
ovidiu-cristian.ma...@inria.fr> wrote:
> After some tuning, I got better results.
gt; > It should be also clear how long is each version supported - e.g. if
> > > > minor.patch had meaning that there are no backward incompatible
> > changes,
> > > > it's OK to file a bug only for current major.minor.patch; previous
> > major
> >
Hi Paolo,
That's right, we deprecated those classes as they are mainly used by the
old consumer. Sounds good to avoid using them in the TopicCommand written
in Java.
Ismael
On Thu, Jul 20, 2017 at 3:33 AM, Paolo Patierno wrote:
> I found that the deprecation was added speaking about the KIP-10
x27;t check the tables. So this is now KIP-179. The old
> link
> > will point you to the right place.
> >
> > On 19 July 2017 at 15:55, Ismael Juma wrote:
> >
> >> One more thing, it looks like there is already a KIP-178:
> >>
> >> KIP-178: Size-
Thanks for the KIP, +1 (binding).
On Thu, Jun 1, 2017 at 9:44 AM, Dong Lin wrote:
> Hi all,
>
> Can you please vote for KIP-164? The KIP can be found at
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-164-+Add+
> UnderMinIsrPartitionCount+and+per-partition+UnderMinIsr+metrics
> .
>
> Tha
>
> > Per 1. I suggested exposing the constant since we are doing so for
> consumer
> > and producer configs prefix as well (CONSUMER_PREFIX, etc).
> >
> > Guozhang
> >
> > On Wed, Jul 19, 2017 at 6:01 AM, Ismael Juma wrote:
> >
> > > Thank
ourselves compatible changes
> given the output format that we have chosen for a tool.
>
> -Jason
>
> On Wed, Jul 19, 2017 at 7:54 AM, Ismael Juma wrote:
>
> > I think this is a good chance although it's unfortunate that it's likely
> to
> > break code that is
; On 19 July 2017 at 14:59, Ismael Juma wrote:
>
> > Hi Tom,
> >
> > It's fine for the tool not to have this functionality from the start.
> > However, since we're adding new Kafka protocol APIs, we need to consider
> > some of these details to ensure
I think this is a good chance although it's unfortunate that it's likely to
break code that is parsing the output of the performance tool. Would it
make sense to only enable this if an option is provided?
Ismael
On Mon, Jul 17, 2017 at 3:41 PM, Jason Gustafson wrote:
> +Users
>
> Thanks for the
Hi Tom,
It's fine for the tool not to have this functionality from the start.
However, since we're adding new Kafka protocol APIs, we need to consider
some of these details to ensure we're building towards the end state, if
that makes sense. Protocol APIs are used by multiple clients, so there is
Thanks for the KIP, Damian. +1 (binding). A couple of minor comments:
1. Do we need to expose the TOPIC_PREFIX constant?
2. The vote thread ended up inside the discuss thread in Gmail. It may be
worth sending another email to make it clear that the vote is ongoing. You
can link back to this thread
Hi Tom,
Thanks for the KIP. Two quick comments:
1. Have you considered how progress would be reported? Partition
reassignment can take a long time and it would be good to have a mechanism
for progress reporting.
2. Removals can only happen in major releases. In your example, the removal
could onl
Thanks for the KIP, +1 (binding) from me.
Ismael
On Wed, Jun 21, 2017 at 1:17 PM, Abhishek Mendhekar <
abhishek.mendhe...@gmail.com> wrote:
> Hi Kafka Dev,
>
> I did like to start the voting on -
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 168%3A+Add+TotalTopicCount+metric+per+clu
Hi Stevo,
Thanks for your feedback. We should definitely do a better job of
documenting things. We basically follow semantic versioning, but it's
currently a bit confusing because:
1. There are 4 segments in the version. The "0." part should be ignored
when deciding what is major, minor and patch
of all of them.
>
> Guozhang
>
> On Tue, Jul 18, 2017 at 3:49 PM, Gwen Shapira wrote:
>
> > Also fine with the change in general.
> >
> > As you mentioned, 1.x indicates mature APIs, compatibility and stability.
> > Are we going to remove the @unstable annot
Hi Guozhang,
Thanks for volunteering to be the release manager for the next release!
I am +1 on naming the next release 1.0.0. As you said, Kafka is mature
enough and this will make it easier for others to understand our versioning
policy.
A couple of minor questions inline.
On Tue, Jul 18, 201
On Mon, Jul 17, 2017 at 10:11 AM, Matthias J. Sax
wrote:
> I thinks, for backward compatibility, this check should be there. The
> only change should be, that if `--bootstrap-servers` is used, one can
> omit `--new-consumer` (and if used, as warning is printed).
>
You can omit "--new-consumer" s
[
https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4669.
Resolution: Fixed
Assignee: Rajini Sivaram
Closing this for now. If it reoccurs, let's r
Ismael Juma created KAFKA-5606:
--
Summary: Review consumer's RequestFuture usage pattern
Key: KAFKA-5606
URL: https://issues.apache.org/jira/browse/KAFKA-5606
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5587.
Resolution: Fixed
Fix Version/s: 0.11.1.0
0.11.0.1
> Processor
Hi Tom,
All active committers should be subscribed to jira@ so I don't think this
changes much from that perspective. If you want to get wider input on a
particular topic, then you should send an email to the mailing list,
however. This was the case before the creation of jira@ as mailing list
fil
[
https://issues.apache.org/jira/browse/KAFKA-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5584.
Resolution: Fixed
> Incorrect log size for topics larger than 2
Congratulations Jason!
Ismael
On Tue, Jul 11, 2017 at 10:32 PM, Guozhang Wang wrote:
> Hi Everyone,
>
> Jason Gustafson has been very active in contributing to the Kafka community
> since he became a Kafka committer last September and has done lots of
> significant work including the most recen
Hi Nishkam,
Not yet. Is there a particular fix that you are interested in?
Ismael
On Fri, Jul 7, 2017 at 6:53 PM, Nishkam Ravi wrote:
> Hi All,
> Do we have an expected release date for 0.11.0.1 ?
>
> Thanks,
> Nishkam
>
Ismael Juma created KAFKA-5570:
--
Summary: Join request's timeout should be slightly higher than the
rebalance timeout
Key: KAFKA-5570
URL: https://issues.apache.org/jira/browse/KAFKA-5570
Project:
Thanks everyone!
Ismael
On Wed, Jul 5, 2017 at 9:55 PM, Jun Rao wrote:
> Hi, Everyone,
>
> Ismael Juma has been active in the Kafka community since he became
> a Kafka committer about a year ago. I am glad to announce that Ismael is
> now a member of Kafka PMC.
>
> Co
[
https://issues.apache.org/jira/browse/KAFKA-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5544.
Resolution: Fixed
> The LastStableOffsetLag metric should be removed when partition is dele
lack-Postava, gosubpl, Grant Henke, Guozhang Wang, Gwen Shapira,
Hamidreza Afzali, Hao Chen, hejiefang, Hojjat Jafarpour, huxi, Ismael Juma,
Ivan A. Melnikov, Jaikiran Pai, James Cheng, James Chien, Jan Lukavsky,
Jason Gustafson, Jean-Philippe Daigle, Jeff Chao, Jeff Widman, Jeyhun
Karimov, Jiangjie Qin,
> +1
> >
> > Verified 0110 web docs and java docs; verified quick start with 2.11 /
> > 2.12 scala versions.
> >
> > One minor observation: on the web docs we show the cmd for 2.11 scala
> > version; we'd better make it templated with the version num
h the release process and the release announcement will follow
in the next few days.
Ismael
P.S. Guozhang's vote was in a separate thread due to some delivery issues
when replying to this thread.
On Fri, Jun 23, 2017 at 2:16 AM, Ismael Juma wrote:
> Hello Kafka users, develope
[
https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4815.
Resolution: Fixed
> Idempotent/transactional Producer (KIP
Ismael Juma created KAFKA-5527:
--
Summary: Idempotent/transactional Producer part 2 (KIP-98)
Key: KAFKA-5527
URL: https://issues.apache.org/jira/browse/KAFKA-5527
Project: Kafka
Issue Type: New
ead, Test
> > worker-SendThread(127.0.0.1:59720), /127.0.0.1:5494
> > 2 to /127.0.0.1:54926 workers Thread 3,
> > ZkClient-EventThread-22-127.0.0.1:54976, ProcessThread(sid:0
> > cport:54976):, Test worker-SendThread(127.0.0.1:54976), Fin
> > alizer, metrics-meter-tick-threa
gCommandTest > testQuotaDescribeEntities PASSED
>
> kafka.admin.AdminTest > testGetBrokerMetadatas PASSED
>
> kafka.admin.ConfigCommandTest > shouldParseArgumentsForClientsEntityType
> PASSED
>
> kafka.admin.AclCommandTest > testAclCli PASSED
>
> kafka.admin.ReassignParti
:54976):, Test worker-SendThread(127.0.0.1:54976), Fin
> alizer, metrics-meter-tick-thread-1)
>
> I tested on a VM and a physical machine, and both give me a lot of errors
> like this.
>
> Thanks.
> --Vahid
>
>
>
>
> From: Ismael Juma
> To: Vahid S
Hey Tom,
Thanks for the PRs you have submitted. As you suggested, most of us are
busy testing the upcoming release. It's a major release with many exciting
features and we want to make sure it's a high quality release.
I understand that it can be frustrating to wait. At the same time, there
are n
checkstyle] [ERROR] C:\Users\User\Downloads\kafka-
> 0.11.0.0-src\clients\src\main\java\org\apache\kafka\common\
> requests\AbstractResponse.java:26:1: Class Fan-Out Complexity is 42 (max
> allowed is 40). [ClassFanOutComplexity]
> :clients:checkstyleMain FAILED
>
> FAILURE: Build
[
https://issues.apache.org/jira/browse/KAFKA-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-5506:
Assignee: Ismael Juma
Nice catch, there are 2 bugs here. See the PR for the details.
> bin/ka
:
https://github.com/apache/kafka/commit/186e3d5efc79ed803f0915d472ace77cbec88694
Full diff:
https://github.com/apache/kafka/compare/5b351216621f52a471c21826d0dec3ce3187e697...0.11.0.0-rc2
Ismael
On Fri, Jun 23, 2017 at 2:16 AM, Ismael Juma wrote:
> Hello Kafka users, developers and cli
Hello Kafka users, developers and client-developers,
This is the third candidate for release of Apache Kafka 0.11.0.0.
This is a major version release of Apache Kafka. It includes 32 new KIPs.
See the release notes and release plan (
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+
Yes, it needs to be sent to the Controller. Metadata response has the
controller id.
Ismael
On Fri, Jun 23, 2017 at 12:45 AM, Vineet Goel wrote:
> Hi,
>
> I get an Error (Code 41) when sending a CreateTopicRequest to any of the
> brokers except 1. Why might this be? Does this request need to be
> > [ant:checkstyle] [ERROR]
>> > > C:\Users\User\Downloads\kafka-0.11.0.0-src\clients\src\main\
>> > > java\org\apache\kafka\common\protocol\Errors.java:89:1:
>> > > Class Fan-Out Complexity is 60 (max allowed is 40).
>> > > [ClassFa
rformance tests run across cloud instances where there might
> be contention and variability, we typically do a multiple runs on different
> clusters with each setup before reporting results.
>
> Thanks
>
> Tom Crayford
> Heroku Kafka
>
> On Thu, Jun 22, 2017 at 4:08 PM, Ismae
k though.
>
> Given that the blockers fixed between RC0 and RC1 haven't changed much in
> the areas we tested, I think the positive results here still apply.
>
> Thanks
>
> Tom Crayford
> Heroku Kafka
>
> On Thu, Jun 8, 2017 at 2:55 PM, Ismael Juma wrote
Thanks for the KIP, Edoardo. A few comments:
1. Have you considered extending RequestMetadata with the additional
information you need? We could add Cluster to it, which has topic
assignment information, for example. This way, there would be no need for a
V2 interface.
2. Something else that coul
[
https://issues.apache.org/jira/browse/KAFKA-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4059.
Resolution: Fixed
Fix Version/s: 0.11.0.0
> Documentation still refers to AsyncProducer
Thanks Damian. I think both options have pros and cons. And both are better
than overload abuse.
The fluent API approach reads better, no mention of builder or build
anywhere. The main downside is that the method signatures are a little less
clear. By reading the method signature, one doesn't nece
Ismael Juma created KAFKA-5486:
--
Summary: org.apache.kafka logging should go to server.log
Key: KAFKA-5486
URL: https://issues.apache.org/jira/browse/KAFKA-5486
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2465.
Resolution: Fixed
> Need to document replica.fetcher.backoff
don't remember the details).
Ismael
On Tue, Jun 20, 2017 at 12:52 AM, Jeff Widman wrote:
> On Thu, Jun 8, 2017 at 5:00 PM, Ismael Juma wrote:
>
> > One of the reasons why some PRs remain open even if they should be
> > closed is that we have no way to close PRs oursel
Ismael Juma created KAFKA-5470:
--
Summary: Replace -XX:+DisableExplicitGC with
-XX:+ExplicitGCInvokesConcurrent in kafka-run-class
Key: KAFKA-5470
URL: https://issues.apache.org/jira/browse/KAFKA-5470
ested the exactly once features, because various core
> committers said that they didn't expect this feature to be perfect in this
> release. We expect to test this this week though.
>
> Given that the blockers fixed between RC0 and RC1 haven't changed much in
> the areas we t
> > >
> > > +1 (non-binding)
> > >
> > > Passes librdkafka integration tests (v0.9.5 and master)
> > >
> > >
> > > 2017-06-19 0:32 GMT+02:00 Ismael Juma :
> > >
> > >> Hello Kafka users, developers and client-develo
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka 0.11.0.0.
This is a major version release of Apache Kafka. It includes 32 new KIPs. See
the release notes and release plan (https://cwiki.apache.org/conf
luence/display/KAFKA/Release+Plan
[
https://issues.apache.org/jira/browse/KAFKA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5336.
Resolution: Fixed
Even though this was fixed by KAFKA-5292, it's a worth tracking th
[
https://issues.apache.org/jira/browse/KAFKA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-5336:
> ListGroup requires Describe on Cluster, but the command-line AclCommand tool
> does not allo
[
https://issues.apache.org/jira/browse/KAFKA-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5463.
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3358
[https
[
https://issues.apache.org/jira/browse/KAFKA-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5457.
Resolution: Fixed
Issue resolved by pull request 3355
[https://github.com/apache/kafka/pull/3355
[
https://issues.apache.org/jira/browse/KAFKA-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5449.
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 3348
[https
[
https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5020:
---
Fix Version/s: (was: 0.11.0.0)
0.11.0.1
> Update protocol documentation
[
https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5032:
---
Fix Version/s: (was: 0.11.0.0)
0.11.0.1
> Think through implications
[
https://issues.apache.org/jira/browse/KAFKA-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5417:
---
Fix Version/s: (was: 0.11.0.0)
0.11.0.1
> Clients get inconsistent connect
[
https://issues.apache.org/jira/browse/KAFKA-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4879:
---
Fix Version/s: 0.11.1.0
> KafkaConsumer.position may hang forever when deleting a to
[
https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5272:
---
Summary: Improve validation for Alter Configs (KIP-133) (was: Improve
validation for Describe/Alter
[
https://issues.apache.org/jira/browse/KAFKA-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reassigned KAFKA-4680:
--
Assignee: Ismael Juma
> min.insync.replicas can be set higher than replication fac
[
https://issues.apache.org/jira/browse/KAFKA-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050067#comment-16050067
]
Ismael Juma commented on KAFKA-5453:
Is this a regression in 0.11.0.0?
> Con
[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5275:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049406#comment-16049406
]
Ismael Juma commented on KAFKA-5445:
Sounds good.
> Document exceptions th
[
https://issues.apache.org/jira/browse/KAFKA-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5443:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5443:
---
Status: Patch Available (was: Open)
> Consumer should use last offset from batch to set next fe
[
https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5272:
---
Fix Version/s: (was: 0.11.0.0)
0.11.0.1
> Improve validation for Descr
[
https://issues.apache.org/jira/browse/KAFKA-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5276:
---
Fix Version/s: (was: 0.11.0.0)
0.11.0.1
> Support derived and prefixed conf
[
https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5275:
---
Status: Patch Available (was: Open)
> Review and potentially tweak AdminClient API for the init
[
https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5431:
---
Priority: Major (was: Critical)
> LogCleaner stopped due
[
https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5413:
---
Priority: Critical (was: Major)
> Log cleaner fails due to large offset in segment f
[
https://issues.apache.org/jira/browse/KAFKA-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5447:
---
Labels: needs-kip (was: )
> AdminClient metrics
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049216#comment-16049216
]
Ismael Juma commented on KAFKA-5447:
cc [~cmccabe]
> AdminClient
Ismael Juma created KAFKA-5447:
--
Summary: AdminClient metrics
Key: KAFKA-5447
URL: https://issues.apache.org/jira/browse/KAFKA-5447
Project: Kafka
Issue Type: Improvement
Reporter
[
https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5431:
---
Priority: Critical (was: Major)
> LogCleaner stopped due
1301 - 1400 of 5488 matches
Mail list logo
