Jason Gustafson created KAFKA-9145:
--
Summary: AbstractCoordinator should respect retry backoff between
rebalances
Key: KAFKA-9145
URL: https://issues.apache.org/jira/browse/KAFKA-9145
Project: Kafka
Jason Gustafson created KAFKA-9144:
--
Summary: Early expiration of producer state can cause coordinator
epoch to regress
Key: KAFKA-9144
URL: https://issues.apache.org/jira/browse/KAFKA-9144
Project
[
https://issues.apache.org/jira/browse/KAFKA-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9102.
Resolution: Fixed
> Increase default zk session timeout and max
[
https://issues.apache.org/jira/browse/KAFKA-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9105.
Resolution: Fixed
> Truncate producer state when incrementing log start off
[
https://issues.apache.org/jira/browse/KAFKA-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8992.
Resolution: Fixed
> Don't expose Errors in `RemoveMemberFromGro
[
https://issues.apache.org/jira/browse/KAFKA-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9038.
Fix Version/s: 2.4.0
Resolution: Fixed
> Allow creating partitions while partit
[
https://issues.apache.org/jira/browse/KAFKA-9089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9089.
Resolution: Fixed
> Reassignment should be resilient to unexpected err
Jason Gustafson created KAFKA-9102:
--
Summary: Increase default zk session timeout and max lag
Key: KAFKA-9102
URL: https://issues.apache.org/jira/browse/KAFKA-9102
Project: Kafka
Issue Type
gt; Thanks,
> > Harsha
> >
> > On Tue, Oct 22, 2019 at 3:20 PM Colin McCabe wrote:
> >
> > > +1 (binding).
> > >
> > > Thanks, Jason.
> > >
> > > best,
> > > Colin
> > >
> > >
> > > On Mon, Oct 21
Jason Gustafson created KAFKA-9099:
--
Summary: Reassignments should be retried after unexpected errors
Key: KAFKA-9099
URL: https://issues.apache.org/jira/browse/KAFKA-9099
Project: Kafka
Jason Gustafson created KAFKA-9089:
--
Summary: Reassignment should be resilient to unexpected errors
Key: KAFKA-9089
URL: https://issues.apache.org/jira/browse/KAFKA-9089
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-9056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9056.
Fix Version/s: 2.5.0
Resolution: Fixed
> Selector outbound byte metric does
+1 Thanks Colin.
On Tue, Oct 22, 2019 at 12:42 AM Tom Bentley wrote:
> +1 (non-binding). Thanks!
>
> On Tue, Oct 22, 2019 at 1:03 AM Gwen Shapira wrote:
>
> > +1
> >
> > Thanks for leading this :)
> >
> > On Mon, Oct 21, 2019 at 3:43 PM Colin McCabe wrote:
> > >
> > > Hi all,
> > >
> > > I'd l
+1
I ran the basic quickstart on the 2.12 artifact and verified
signatures/checksums.
I also looked over the release notes. I see that KAFKA-8950 is included, so
maybe they just need to be refreshed.
Thanks for running the release!
-Jason
On Fri, Oct 18, 2019 at 5:23 AM David Arthur wrote:
>
Jason Gustafson created KAFKA-9081:
--
Summary: Loosen reassignment completion to handle existing URPs
Key: KAFKA-9081
URL: https://issues.apache.org/jira/browse/KAFKA-9081
Project: Kafka
I'd like to start a vote for KIP-537:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-537%3A+Increase+default+zookeeper+session+timeout
.
+1 from me
Thanks,
Jason
+1 Looks reasonable to me. Tracking this per-processor is probably not that
useful, but I agree it simplifies the implementation.
-Jason
On Wed, Oct 16, 2019 at 11:58 AM Colin McCabe wrote:
> Hi all,
>
> I wrote a short KIP about adding a metric to track the number of open
> connections with a
[
https://issues.apache.org/jira/browse/KAFKA-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8962.
Fix Version/s: 2.4.0
Resolution: Fixed
> KafkaAdminClient#describeTopics alw
batch (and practically the deltas will be all negative)?
> > >
> > > If that's case, could we do some back of the envelope calculation on
> > what's
> > > the possible smallest case of deltas? Note that since we use varInt for
> >
[
https://issues.apache.org/jira/browse/KAFKA-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9004.
Resolution: Fixed
> Fetch from follower unintentionally allowed for old consum
+1. Thanks Richard.
On Wed, Oct 16, 2019 at 10:04 AM Richard Yu
wrote:
> Hi all,
>
> Want to try to get this KIP wrapped up. So it would be great if we can get
> some votes.
>
> Cheers,
> Richard
>
> On Tue, Oct 15, 2019 at 12:58 PM Jun Rao wrote:
>
> > Hi, Richard,
> >
> > Thanks for the updat
Jason Gustafson created KAFKA-9056:
--
Summary: Selector outbound byte metric does not count partial sends
Key: KAFKA-9056
URL: https://issues.apache.org/jira/browse/KAFKA-9056
Project: Kafka
Jason Gustafson created KAFKA-9047:
--
Summary: AdminClient group operations may not respect backoff
Key: KAFKA-9047
URL: https://issues.apache.org/jira/browse/KAFKA-9047
Project: Kafka
Issue
Hi All,
I have a short KIP to raise the default zk session timeout:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-537%3A+Increase+default+zookeeper+session+timeout.
Please take a look.
Thanks,
Jason
[
https://issues.apache.org/jira/browse/KAFKA-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9033.
Fix Version/s: 2.4.0
Resolution: Fixed
> Change default client-id in consu
[
https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8813.
Fix Version/s: 2.4.0
2.3.2
Resolution: Fixed
> Race condit
Jason Gustafson created KAFKA-9040:
--
Summary: Implement --all option when describing configs
Key: KAFKA-9040
URL: https://issues.apache.org/jira/browse/KAFKA-9040
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8725.
Fix Version/s: 2.4.0
Resolution: Fixed
> Improve LogCleaner error handling w
; exception hierarchy.
> >>> >>
> >>> >>
> >>> >> -Matthias
> >>> >>
> >>> >> On 8/8/18 2:57 AM, Stanislav Kozlovski wrote:
> >>> >> >> If you are inheriting from SerializationException, your derived
> >>&g
gt; > > +1 (binding)
> > >
> > > Regards,
> > >
> > > Rajini
> > >
> > > On Wed, Sep 25, 2019 at 4:41 PM Colin McCabe
> wrote:
> > >
> > > > Looks good. +1 (binding)
> > > >
> > > &g
Hi All,
I wrote a short KIP to address a longstanding issue with timeout behavior
in the AdminClient:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-533%3A+Add+default+api+timeout+to+AdminClient
.
Take a look and let me know what you think.
Thanks,
Jason
Jason Gustafson created KAFKA-9004:
--
Summary: Fetch from follower unintentionally enabled for old
consumers
Key: KAFKA-9004
URL: https://issues.apache.org/jira/browse/KAFKA-9004
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-7190.
Fix Version/s: 2.4.0
Assignee: Bob Barrett (was: Guozhang Wang)
Resolution
[
https://issues.apache.org/jira/browse/KAFKA-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8983.
Fix Version/s: 2.4.0
Resolution: Fixed
> AdminClient deleteRecords should not f
Jason Gustafson created KAFKA-8992:
--
Summary: Don't expose Errors in Admin result objects
Key: KAFKA-8992
URL: https://issues.apache.org/jira/browse/KAFKA-8992
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-8985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8985.
Fix Version/s: 2.4.0
Assignee: Jason Gustafson (was: Colin McCabe
[
https://issues.apache.org/jira/browse/KAFKA-8885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8885.
Fix Version/s: 2.4.0
Resolution: Fixed
> The Kafka Protocol should Support Optio
Jason Gustafson created KAFKA-8983:
--
Summary: AdminClient deleteRecords should not fail all partitions
unnecessarily
Key: KAFKA-8983
URL: https://issues.apache.org/jira/browse/KAFKA-8983
Project
Jason Gustafson created KAFKA-8976:
--
Summary: AdminClient deleteRecords should not fetch metadata
unnecessarily
Key: KAFKA-8976
URL: https://issues.apache.org/jira/browse/KAFKA-8976
Project: Kafka
Hi David,
Thanks for running the release. I think we should consider getting this bug
fixed: https://issues.apache.org/jira/browse/KAFKA-8896. The impact of this
bug is that consumer groups cannot commit offsets or rebalance. The patch
should be ready shortly.
Thanks,
Jason
On Fri, Sep 13, 201
o I created this KIP only
> with resolving the problem regarding tombstones.
> Whats your thoughts? If the problem regarding transaction markers is a
> little too complex, then we can we just leave it out of the KIP and fix the
> tombstones issue.
>
> Cheers,
> Richard
>
Hi All,
I'm starting a vote for KIP-524, which is a small change to the config
tool:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-524%3A+Allow+users+to+choose+config+source+when+describing+configs
.
+1 from me.
Thanks,
Jason
Thanks David for the clarification. That sounds good.
On Mon, Sep 23, 2019 at 12:35 AM David Jacot wrote:
> Hi all,
>
> The vote has passed with +3 binding votes (Colin McCabe, Gwen Shapira,
> Jason Gustafson) and +3 non binding votes (Mickael Maison, Konstantine
> Karantasis
+1 from me. This is a clever solution. Kind of a pity we couldn't work
flexible version support into the response, but I understand why it is
difficult.
One minor nitpick: the INVALID_REQUEST error already exists. Are you
intending to reuse it?
Thanks,
Jason
On Fri, Sep 20, 2019 at 3:50 PM Konst
+1 Thanks!
On Thu, Sep 19, 2019 at 11:22 PM Tom Bentley wrote:
> +1 (non-binding).
>
> On Fri, Sep 20, 2019 at 7:00 AM Maulin Vasavada >
> wrote:
>
> > +1 (non-binding). Thanks for the KIP.
> >
> > On Thu, Sep 19, 2019 at 10:38 PM Manikumar
> > wrote:
> >
> > > +1 (binding), Thanks for the KIP
rios.
> > > > >
> > > > > I have added this to the KIP:
> > > > > * - poll-idle-ratio*: The fraction of time the consumer spent
> waiting
> > > for
> > > > > the user to process records from poll.
> > > > >
> >
Hi Richard,
Just reposting my comment from the JIRA:
The underlying problem here also impacts the cleaning of transaction
markers. We use the same delete horizon in order to tell when it is safe to
remove the marker. If all the data from a transaction has been cleaned and
the delete horizon has p
[
https://issues.apache.org/jira/browse/KAFKA-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8841.
Resolution: Fixed
> Optimize Partition.maybeIncrementLeade
rote:
>
> > Ah, great idea.
> >
> > On Fri, Sep 13, 2019 at 8:47 AM Jason Gustafson
> > wrote:
> > >
> > > Hi All,
> > >
> > > I have a minor KIP to improve the config tool:
> > >
> >
> https://cwiki.apache.org/
Jason Gustafson created KAFKA-8908:
--
Summary: Use ApiVersion API for inter-broker communication
Key: KAFKA-8908
URL: https://issues.apache.org/jira/browse/KAFKA-8908
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8474.
Resolution: Fixed
> Improve configuration layout on webs
Late here, but I am a big +1. Great to see this finally happening.
-Jason
On Fri, Sep 13, 2019 at 11:43 AM Colin McCabe wrote:
> Hi all,
>
> With 3 binding +1 votes from Gwen Shapira, Ismael Juma, and Bill Bejeck
> and 5 non-binding +1 votes from Tom Bentley, Ron Dagostino, David Jacot,
> Dhruv
Hi Kevin,
This looks reasonable to me. I'd also +1 Radai's suggestion if you're
willing. Something like an idle ratio for the consumer would be helpful.
Thanks,
Jason
On Fri, Sep 13, 2019 at 10:08 AM radai wrote:
> while youre at it another metric that we have found to be useful is %
> time sp
Hi All,
I have a minor KIP to improve the config tool:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-524%3A+Allow+users+to+choose+config+source+when+describing+configs.
Let me know what you think.
-Jason
. I'll also modify the kip to make
> > > these clear.
> > >
> > > On Fri, Sep 6, 2019 at 4:01 PM Jason Gustafson
> wrote:
> > >
> > >> Hi Arjun,
> > >>
> > >> The updated KIP looks good. Just a couple questions:
&g
gt; > > On Tue, Sep 10, 2019 at 10:18 AM Matthias J. Sax <
> > > matth...@confluent.io>
> > > > > > wrote:
> > > > > >
> > > > > >> Thanks for the KIP Guozhang.
> > > > > >>
> > > > > >>> Another reason i
[
https://issues.apache.org/jira/browse/KAFKA-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8875.
Fix Version/s: 2.4.0
Resolution: Fixed
> CreateTopic API should check to
[
https://issues.apache.org/jira/browse/KAFKA-8747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8747.
Resolution: Fixed
> Flaky Test ControllerEventManagerTest#testEventQueueT
Jason Gustafson created KAFKA-8896:
--
Summary: NoSuchElementException after coordinator move
Key: KAFKA-8896
URL: https://issues.apache.org/jira/browse/KAFKA-8896
Project: Kafka
Issue Type
breaking compatibility
just for aesthetics.
-Jason
On Tue, Sep 10, 2019 at 9:41 AM Guozhang Wang wrote:
> Thanks Jason!
>
> On Tue, Sep 10, 2019 at 9:07 AM Jason Gustafson
> wrote:
>
> > Hi Guozhang,
> >
> > I think the motivation for the new API makes sense. I've wa
Hi Guozhang,
I think the motivation for the new API makes sense. I've wanted something
like this in the past. That said, do you think there is a substantial
benefit from deprecating the old API? I can still see it being convenient
in some cases and it's no real cost to maintain.
Also, just a mino
;). Anyway, I'm satisfied if
we just document the recommended approach and explain the risk if users
don't follow it.
-Jason
On Mon, Sep 9, 2019 at 12:52 PM Boyang Chen
wrote:
> Thanks Jason for the vote!
>
> On Mon, Sep 9, 2019 at 12:07 PM Jason Gustafson
> wrote:
>
+1 Thanks for the KIP. Just a couple comments below:
1. Kafka APIs traditionally leave off `get` from API names. How about
`groupMetadata` instead of `getMetadata`?
2. I am guessing memberId and groupInstanceId should be nullable in the
TxnOffsetCommit schema?
3. Just to clarify on the upgrade pro
ew endpoint.
>
> If this works with you all, I can update the KIP. Please let me know what
> you think.
>
> Thanks everyone.
>
> Best,
>
> On Thu, Aug 29, 2019 at 10:14 AM Colin McCabe wrote:
>
> > On Mon, Aug 26, 2019, at 14:03, Jason Gustafson wrote:
> &
+1 Thanks Colin. This is really going to help with compatibility.
-Jason
On Wed, Sep 4, 2019 at 1:34 PM Colin McCabe wrote:
> On Wed, Sep 4, 2019, at 13:01, Jason Gustafson wrote:
> > Hi Colin,
> >
> > Just a couple questions.
> >
> > 1. I think we discusse
[
https://issues.apache.org/jira/browse/KAFKA-8590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8590.
Resolution: Fixed
> Replace TxnOffsetCommitRequest request/response with automa
[
https://issues.apache.org/jira/browse/KAFKA-8822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8822.
Resolution: Fixed
> Remove CompletedFetch type from Fetc
[
https://issues.apache.org/jira/browse/KAFKA-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8724.
Resolution: Fixed
> log cleaner thread dies when attempting to clean a __consumer_offs
Jason Gustafson created KAFKA-8875:
--
Summary: CreateTopic API should check topic existence before
replication factor
Key: KAFKA-8875
URL: https://issues.apache.org/jira/browse/KAFKA-8875
Project
Hi Colin,
Just a couple questions.
1. I think we discussed that we would do a lazy version bump of all
protocols in order to get flexible version support. Can you add that to the
KIP?
2. The doc mentions a bump to the request and response header formats to
version 1. Currently there is no formal
Jason Gustafson created KAFKA-8845:
--
Summary: Detect and abort stalled transactions
Key: KAFKA-8845
URL: https://issues.apache.org/jira/browse/KAFKA-8845
Project: Kafka
Issue Type
Jason Gustafson created KAFKA-8844:
--
Summary: Add max lso lag metric
Key: KAFKA-8844
URL: https://issues.apache.org/jira/browse/KAFKA-8844
Project: Kafka
Issue Type: Improvement
Jason Gustafson created KAFKA-8841:
--
Summary: Optimize Partition.maybeIncrementLeaderHW
Key: KAFKA-8841
URL: https://issues.apache.org/jira/browse/KAFKA-8841
Project: Kafka
Issue Type
rted; some others (INVALID_PRODUCER_EPOCH) would cause the producer to
> enter the FATAL_ERROR state, plus it would cause all future txns to be
> aborted.
>
> Is that right?
>
>
> Guozhang
>
>
> On Wed, Aug 21, 2019 at 3:52 PM Matthias J. Sax
> wrote:
> >
>
to it. It will
> give brokers multiple ways of changing log levels. and there is still a
> consistent way of achieving cross component goals of the KIP.
>
> Best,
>
>
> On Fri, Aug 23, 2019 at 4:12 PM Jason Gustafson
> wrote:
>
> > Let me elaborate a little bit. W
Jason Gustafson created KAFKA-8836:
--
Summary: Add inter-broker protocol to alter ISR
Key: KAFKA-8836
URL: https://issues.apache.org/jira/browse/KAFKA-8836
Project: Kafka
Issue Type
Jason Gustafson created KAFKA-8835:
--
Summary: Update documentation for URP changes in KIP-352
Key: KAFKA-8835
URL: https://issues.apache.org/jira/browse/KAFKA-8835
Project: Kafka
Issue Type
Jason Gustafson created KAFKA-8834:
--
Summary: Distinguish URPs caused by reassignment plus other metrics
Key: KAFKA-8834
URL: https://issues.apache.org/jira/browse/KAFKA-8834
Project: Kafka
Closing this vote. The final result is +9 with 4 binding votes.
@Satish Sorry, I missed your question above. Good point about updating
documentation. I will create a separate jira to make sure this gets done.
-Jason
On Fri, Aug 23, 2019 at 11:23 AM Jason Gustafson wrote:
> Thanks Stan, g
lly turn off in Kafka. Now that we have a proper API with support
in the AdminClient, we can deprecate and eventually remove the JMX endpoint.
Thanks,
Jason
On Fri, Aug 23, 2019 at 10:49 AM Jason Gustafson wrote:
> Hi Arjun,
>
> Thanks for the KIP. Do we really need a JMX-based API? Is
[
https://issues.apache.org/jira/browse/KAFKA-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8753.
Fix Version/s: 2.4.0
Resolution: Fixed
> Add JMX for number of topics marked
, and calculate the URPs based
> on that. +1 for this. (I assume Jason will update the KIP...)
>
> best,
> Colin
>
>
> >
> > Taking that into account, +1 from me! (non-binding)
> >
> > On Fri, Aug 23, 2019 at 7:00 PM Colin McCabe wrote:
> >
> &g
Hi Arjun,
Thanks for the KIP. Do we really need a JMX-based API? Is there literally
anyone in the world that wants to use JMX if they don't have to? I thought
one of the major motivations of KIP-412 was how much of a pain JMX is.
Thanks,
Jason
On Mon, Aug 19, 2019 at 5:28 PM Arjun Satish wrote:
[
https://issues.apache.org/jira/browse/KAFKA-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8325.
Fix Version/s: 2.3.1
Resolution: Fixed
> Remove from the incomplete set fai
e exposed to users) for
> future
> >> developers, how about rename it to "required_epoch" and if it is set to
> >> "-1" it means "not required, hence not checks"?
> >>
> >> Guozhang
> >>
> >> On T
-1.
> 2. Epoch and producerId are provided
>a) the provided producerId/epoch matches the current producerId/epoch:
> i) if the epoch is not exhausted, bump the epoch
> ii) if the epoch is exhausted, create a new PID with epoch=0
>b) the provided producerId/epoch m
Jason Gustafson created KAFKA-8825:
--
Summary: Add option to reset consumer offset by relative time
Key: KAFKA-8825
URL: https://issues.apache.org/jira/browse/KAFKA-8825
Project: Kafka
Issue
ng AlterIsrRequest from a broker to the controller (at least for a
> given partition) in order to set CurrentZkVersion properly?
>
> Jun
>
> On Tue, Aug 20, 2019 at 10:07 AM Jason Gustafson
> wrote:
>
> > I'm going to close this vote. The final result is +5 with 3 bind
+1 Thanks for the KIP!
-Jason
On Thu, Aug 15, 2019 at 4:01 AM Jakub Scholz wrote:
> +1 (non-binding)
>
> Jakub
>
> On Sat, Aug 10, 2019 at 8:34 PM Stanislav Kozlovski <
> stanis...@confluent.io>
> wrote:
>
> > Awesome KIP, +1 (non-binding)
> >
> > Thanks,
> > Stanislav
> >
> > On Fri, Aug 9, 20
Hi All,
I'd like to start a vote on KIP-352, which is a follow-up to KIP-455 to fix
a long-known shortcoming of URP reporting and to improve reassignment
monitoring:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-352%3A+Distinguish+URPs+caused+by+reassignment
.
Note that I have added one n
, I'm actually fine to name it
> more
> > > generally and leave a note that at the moment its value is defined as
> the
> > > zk version.
> > >
> > >
> > > Guozhang
> > >
> > >
> > > On Mon, Aug 12, 2019 at 2:22 PM Ja
t this?
>
> +1 (binding)
>
> best,
> Colin
>
>
> On Mon, Aug 12, 2019, at 10:57, Guozhang Wang wrote:
> > +1 (binding).
> >
> > Thanks Jason!
> >
> > On Wed, Aug 7, 2019 at 11:18 AM Jason Gustafson
> wrote:
> >
> > > Hi All,
>
to call
> OnPartitionsAssigned()
> > or
> > > OnPartitionsRevoked() with each rebalance. Our requirement is to be
> > > up-to-date with group metadata such as generation information, so
> > callback
> > > like onGroupJoined() would make more sense as
ual work)
Yeah, that makes sense. Maybe we can include the version bump for all RPCs
in this KIP, but we can implement it lazily as the protocols are converted.
-Jason
On Mon, Aug 12, 2019 at 7:16 PM Colin McCabe wrote:
> On Mon, Aug 12, 2019, at 11:22, Jason Gustafson wrote:
> &
new protocol we could perhaps rename
> CurrentZkVersion to something like "IsrEpoch" or "IsrVersion". I think
> that'd reflect its purpose better.
>
> Best,
> Viktor
>
> On Wed, Aug 7, 2019 at 8:37 PM Jason Gustafson wrote:
>
> > Hi All,
> >
> &
e
> `onGroupMetadataUpdated(ConsumerGroupMetadata metadata)`
>
> To simplify the code logic, we believe option 3 & 4 are better solutions,
> and of which I slightly prefer option 4 as it is the most clean solution
> with less intrusion to both consumer and producer APIs.
&g
Hi Colin,
Thanks for the KIP! This is a significant improvement. One of my personal
interests in this proposal is solving the compatibility problems we have
with the internal schemas used to define consumer offsets and transaction
metadata. Currently we have to guard schema bumps with the inter-br
@Dongjin Thanks, you raise some good points. I think the intent here is to
try and fix one of the more egregious inconsistencies without increasing
the scope too much. We tried the big KIP approach with KIP-14 before and I
don't think we made much progress. I think it's reasonable to do this on a
c
could cause confusion. Just adding a new metric sounds good to me!
>
> The throttle follow-up is mentioned as part of future work in KIP-455 and I
> agree that it is way out of scope for this one.
>
>
> On Thu, Aug 8, 2019 at 8:03 PM Jason Gustafson wrote:
>
> > Hi St
c to
> distringuish between reassigning/non-reassigning traffic, or do you prefer
> to keep this KIP nice and small?
>
> On Thu, Aug 8, 2019 at 12:08 AM Jason Gustafson
> wrote:
>
> > Hi All,
> >
> > Since KIP-455 is passed, I would like to revive this proposal. I ha
701 - 800 of 3206 matches
Mail list logo
