nal.id.expiration.ms, the new timeout just needs to cover the
> longest duration that a producer might be retrying the same Produce
> request. 7 days seems too high. Although I think it could go a fair even
> lower, perhaps 1 day is a reasonable place to start?
>
> Thanks,
&
at we should try our best to keep backward
> > > compatibility, although our intention is to have lower producer id
> > > expiration timeout.
> > > So, I think we should keep default to -1 IMO.
> > > Maybe we change the default to 1 day in next major release (4.0)
> > > > Thanks for the KIP.
> > > > I agree with you that we should try our best to keep backward
> > > > compatibility, although our intention is to have lower producer id
> > > > expiration timeout.
> > > > So, I think we should ke
t.ms. Is that what we want? We could say it should
> be
> > higher than delivery.timeout.ms but indicate that the default is usually
> > fine. The main reason to reduce it would be to save memory, I guess.
> > 2. Each config has a priority, we should specify it for this one. I'm
>
tent", since it does not cover the transactional case. (I would
> > suggest "idempotent.pid.expiration.ms" (c.f.
> > transactional.id.expiration.ms),
> > but the distinction between "id" and "pid" is easily missed–even if it's
> > te
Hey Jose.
I found a gap in handling ISR changes in ZK mode. We just need to prevent
brokers that are offline from being added to ISR. Since KIP-841 is part of
this release and the fix should be small (a few lines), I propose adding
https://issues.apache.org/jira/browse/KAFKA-14140 to the 3.3 releas
, 3 Aug 2022 at 19:14, Justine Olshan
> wrote:
>
> > Hi Tom and Ismael,
> >
> > 1. Yes, there are definitely many ways to improve this issue and I plan
> to
> > write followup KIPs to address some of the larger changes.
> > Just wanted to get this simple fix
Hi all,
I'd like to start a vote for KIP-854: Separate configuration for producer
ID expiry.
KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-854+Separate+configuration+for+producer+ID+expiry
JIRA: https://issues.apache.org/jira/browse/KAFKA-14097
Discussion thread:
https://lists.apache.
ing)
> > > >
> > > > Sagar.
> > > >
> > > > On Tue, Aug 9, 2022 at 1:13 PM David Jacot
> > >
> > > > wrote:
> > > >
> > > > > Thanks for the KIP, Justine. The proposal makes sense to me. I am
> +1
Congratulations Lucas!
Thanks for your mentorship on some of my KIPs as well :)
On Thu, Feb 16, 2023 at 1:56 PM Jun Rao wrote:
> Hi, Everyone,
>
> The PMC of Apache Kafka is pleased to announce a new Kafka committer Lucas
> Bradstreet.
>
> Lucas has been a long time Kafka contributor since Oct.
Feb 3, 2023 at 8:40 AM Justine Olshan wrote:
> Thanks everyone! I'm going to close the vote.
> The KIP is accepted with five binding votes from Jason, Guozhang,
> Matthias, David (and me), and two non-binding votes from Colt and Artem.
>
> Thanks again,
> Justine
>
> On
longer have any top-level primitive fields.
> 2) Add a top-level `errorCode` field in the response.
>
> Is that summary right?
>
>
> Guozhang
>
> On Wed, Feb 22, 2023 at 4:51 PM Justine Olshan
> wrote:
> >
> > Hey all,
> >
> > I've updated th
e are any
questions.
Thanks,
Justine
On Thu, Feb 23, 2023 at 10:55 AM Justine Olshan
wrote:
> Yup -- those are the main changes!
>
> On Thu, Feb 23, 2023 at 9:44 AM Guozhang Wang
> wrote:
>
>> Thanks Justine. I checked the diff between the two versions on wiki,
>> seem
ould/will depends on the
> performance results that we get.
>
> Thanks,
> David
>
> Le sam. 18 mars 2023 à 00:53, Justine Olshan >
> a écrit :
>
> > Hey all. I've updated the kip to include a configuration change. This
> will
> > allow users to disable
Hey Jeff and David,
Thanks for the KIP! I was also looking into this a bit since I may want to
change the record format for KIP-890 as well (finally implementing the
record change from KIP-360 to better support the epoch bump. This will
potentially be helpful for me to implement that work.
I disc
ue record
> > > > version to
> > > > > > > > make it flexible along with the changes to parse with the
> > highest
> > > > known
> > > > > > > > version? I'm not sure I understand why we cannot make both
> > changes
> > > > >
;
> > > > > > > > > > David,
> > > > > > > > > >
> > > > > > > > > > 1. That makes sense. I revised the "Reading new fields"
> > > section
> > > >
+1 (binding) as well.
Thanks!
On Thu, Mar 30, 2023 at 9:32 AM Jason Gustafson
wrote:
> +1. Thanks Jeff.
>
> On Thu, Mar 30, 2023 at 7:41 AM Alexandre Dupriez <
> alexandre.dupr...@gmail.com> wrote:
>
> > Thanks for the KIP and clarifications, Jeff.
> >
> > +1 (non binding)
> >
> > Le jeu. 30 ma
Hi,
I'm also a bit unsure of the motivation here. Is there a need to change the
number of partitions for this topic?
Justine
On Tue, Apr 4, 2023 at 10:07 AM David Jacot wrote:
> Hi,
>
> I am not very comfortable with the proposal of this KIP. The main issue is
> that changing the number of par
Hey Ismael -- thanks for bringing this up.
I've filed https://issues.apache.org/jira/browse/KAFKA-14904 and am working
on it now.
I hope the other tests get fixed soon.
On Fri, Apr 14, 2023 at 6:47 AM Ismael Juma wrote:
> Hi team,
>
> It looks like there are a lot of test failures in the master
I've tried the script, but it's not quite complete.
I've had issues finding folks -- if they haven't reviewed in kafka, we can
not find an email for them. I also had some issues with finding folks who
had reviewed before.
Right now, my strategy is to use GitHub to search previous commits for
folks
Hey Mickael,
I've just opened a blocker to revert KAFKA-14561 in 3.5. There are a few
blocker bugs that I don't think I can fix before the code freeze, so I
think for the quality of the release, we should just revert the commit.
Thanks,
Justine
On Fri, Apr 21, 2023 at 1:23 PM Josep Prat
wrote:
I'm also a bit concerned by the 20 active collaborators rule. How do we
pick the 20 people?
Justine
On Fri, Apr 28, 2023 at 8:36 AM Matthias J. Sax wrote:
> In general I am +1
>
> The only question I have is about
>
> > You may only have 20 active collaborators at any given time per
> repositor
Hey Luke,
I was taking a quick pass over the KIP and saw this line:
>It looks perfect. But there's a caveat here. Like the doc said, acks=all
will "wait for the *full set of in-sync replicas *to acknowledge the
record", so if there's only 1 replica in in-sync replicas, it will have the
same effec
Yash,
When I rebuild, I go to the CloudBees CI page and I have to log in with my
apache account.
Not sure if the change in the build system or the need to sign in is part
of the problem.
On Wed, May 24, 2023 at 4:54 AM Federico Valeri
wrote:
> +1 on Divij suggestions
>
>
> On Wed, May 24, 2023
s builds?
>
> Thanks,
> Yash
>
> On Wed, May 24, 2023 at 9:30 PM Justine Olshan
>
> wrote:
>
> > Yash,
> >
> > When I rebuild, I go to the CloudBees CI page and I have to log in with
> my
> > apache account.
> > Not sure if the change in th
Hi Mehari,
This is an interesting KIP! I've seen my fair share of issues due to future
timestamps, so this is definitely an area that could be improved.
I noticed in the compatibility section it says:
> There are no changes to public interfaces that will impact clients.
However, this change is co
good as an initial solution I can put start a KIP and see
>> what the wider community feels about this. *
>>
>> *Also, I noticed that at some point one of us hit "Replay" instead of
>> "Replay to All" :) So here are the previous conversations*
>>
>&g
FYI -- I just saw this PR regarding a dependency for ARM. We may want to
get this in for 3.5 as well. It should be quick.
https://issues.apache.org/jira/browse/KAFKA-15044
https://github.com/apache/kafka/pull/13786
Justine
On Wed, May 31, 2023 at 9:28 AM David Arthur
wrote:
> Mickael,
>
> Coli
Hey Mickael --
This is done. Thanks!
On Wed, May 31, 2023 at 11:24 AM Mickael Maison
wrote:
> Hi Justine,
>
> Yes you can merge that into 3.5.
>
> Thanks,
> Mickael
>
> On Wed, May 31, 2023 at 7:56 PM Justine Olshan
> wrote:
> >
> > FYI -- I just saw thi
Hey Mehari,
Thanks for adding that section. I think one other thing folks have
considered is including two timestamps in the message format -- one for the
client side timestamp and one for the server side. Of course, this would
require a bump to the message format, and that hasn't happened in a whi
it right
> now?
>
> [1] https://lists.apache.org/thread/rxnps10t4vrsor46cx6xdj6t03qqxosh
> [2]
>
> https://cwiki.apache.org/confluence/display/KAFKA/ideas+for+kafka+message+format+v.3
>
>
> --
> Divij Vaidya
>
>
>
> On Mon, Jun 5, 2023 at 6:42 PM Justine Olshan >
> wrote:
Hey Mehari,
I was just getting annoyed looking at logs of kafka clusters with timestamp
issues. Let me take final look at the KIP.
Thanks,
Justine
On Wed, Jun 21, 2023 at 11:13 AM Beyene, Mehari
wrote:
> Hi Justine,
>
> I have initiated the voting process for this KIP here:
> https://lists.apac
Hey Mehari,
Thanks for the KIP. One minor change is now that we have the before and
after configs does this error make sense?
> we will return error code 32 (INVALID_TIMESTAMP) with the error message
"Timestamp of the message with offset [record offset] is ahead of the
broker's current time."
I
Hey Mehari,
Yes. The KIP looks good to me. +1 (binding)
Justine
On Tue, Jun 27, 2023 at 12:13 PM Beyene, Mehari
wrote:
> Hi Justine/All,
>
> I want to wrap up this voting process in the next day or so. Justine,
> since you gave a conditional binding vote regarding updating the error
> message,
Congrats Greg!
On Mon, Jul 10, 2023 at 9:40 AM Tom Bentley wrote:
> Congratulations!
>
> On Mon, 10 Jul 2023 at 17:32, wrote:
>
> > Congrats Greg!
> >
> > -
> > Gaurav
> >
> > > On 10 Jul 2023, at 17:25, Hector Geraldino (BLOOMBERG/ 919 3RD A) <
> > hgerald...@bloomberg.net> wrote:
> > >
> > >
.org/confluence/display/KAFKA/KIP-516%3A+Topic+Identifiers#KIP516:TopicIdentifiers-LeaderAndIsrRequestv5
Please let me know if you have any thoughts or concerns with this change.
Thanks,
Justine
On Mon, Oct 19, 2020 at 8:50 AM Justine Olshan wrote:
> Thanks everyone for the votes. KIP-516
Let me know if there are any questions,
Justine
On Thu, Feb 18, 2021 at 10:16 AM Justine Olshan
wrote:
> Hi all,
> I realized that the DISCUSS thread got very long, so I'll be posting
> updates to this thread from now on.
> Just a quick update to the KIP. As a part of
> https://iss
Hi Alyssa,
Are you asking to be added to JIRA? If so, can you provide your jira
username?
Thanks,
Justine
On Fri, Apr 30, 2021 at 9:48 AM Alyssa Huang
wrote:
> Hello,
>
> I'm interested in contributing to Kafka! Can I be added to the project?
>
> Best,
> Alyssa
>
16%3A+Topic+Identifiers#KIP516:TopicIdentifiers-AdminClientSupport
Thanks,
Justine
On Tue, Mar 30, 2021 at 2:38 PM Justine Olshan wrote:
> Hi all,
> Another quick update. After some offline discussion with KIP-500 folks,
> I'm making a small tweak to one of the configs in KI
Hi Konstantine,
I've discovered a bug with topic IDs that can be encountered when upgrading
from IBP versions below 2.8.
Since 2.8, when handling leader and isr requests, the request topic IDs are
compared to the log IDs and partitions with inconsistent IDs are skipped.
With a change introduced i
Hi Artem,
Thanks for working on improving the Sticky Partitioner!
I had a few questions about this portion:
*The batching will continue until either an in-flight batch completes or we
hit the N bytes and move to the next partition. This way it takes just 5
records to get to batching mode, not 5
Hi Mason,
Thanks for the KIP. I had a few questions.
Are you saying that we will be keeping the original (untagged) offline
partitions count metric? I was a little confused by the wording in the KIP>
I'm also curious about potential performance impacts. Have you looked into
this?
Thanks,
Justine
Hi all,
I've filed a bug for an extra map allocation that is used in the fetch
path. https://issues.apache.org/jira/browse/KAFKA-13512
I think it qualifies as a blocker since this path is used pretty frequently
and it looks to be a regression.
I also have a PR open to fix the issue. With this chan
eedback.
Thanks,
Justine
On Mon, Sep 28, 2020 at 11:38 AM Justine Olshan
wrote:
> Hello all,
>
> I just wanted to follow up on this discussion. Did we come to an
> understanding about the directory structure?
>
> I think the biggest question here is what is acceptable to leave o
he issue seems unfixed.
>
> 40. Since UUID is public facing, could you include its definition?
>
> 41. StopReplicaResponse still includes the topic field.
>
> 42. "It is unnecessary to include the name of the topic in the following
> Request/Response calls" It wo
r the update. The KIP looks good to me now. Just a minor comment
> below.
>
> 30. Perhaps "option[UUID]" can be put in the doc.
>
> Jun
>
> On Thu, Oct 1, 2020 at 3:28 PM Justine Olshan
> wrote:
>
> > Hi Jun,
> > Thanks for the response!
> >
/7efa8cd169cadc7dc9cf86a7c0dbbab1836ddb5024d310fcebacf80c@%3Cdev.kafka.apache.org%3E
Please take a look and vote if you have a chance.
Thanks,
Justine
On Tue, Sep 22, 2020 at 8:52 AM Justine Olshan wrote:
> Hi all,
>
> I'd like to call a vote on KIP-516: Topic Identifiers. Here is the KIP:
>
> http
topReplicaResponse below?
> > > > > > > StopReplica Response (Version: 4) => error_code [topics]
> > > > > > > error_code => INT16
> > > > > > > topics => topic topic_id* [partitions]
> > > > > > >
> >
Hi Evelyn,
Thanks for taking a look at improving the sticky partitioner! These edge
cases seem like they would cause quite a bit a trouble.
I think the idea to check for max.in.flight.requests.per.connection is a
good one, but one concern I have is how this information will be available
to the par
Hi George,
I've been looking at the discussion on improving the sticky partitioner,
and one of the potential issues we discussed is how we could get
information to the partitioner to tell it not to choose certain partitions.
Currently, the partitioner can only use availablePartitionsForTopic. I too
The user has been blocked. https://issues.apache.org/jira/browse/INFRA-21268
On Tue, Jan 5, 2021 at 2:52 PM Brandon Brown
wrote:
> Is there any way to block Tim van der Kooi from making issues? I’m getting
> about 10 new email issues created a minute.
>
> Brandon Brown
>
>
+1 (binding) from me
Justine
On Mon, Sep 16, 2024 at 7:36 PM TengYao Chi wrote:
> Hi Kirk
> Thanks for pointing out. I have updated the description of KAFKA-17087.
>
> Sincerely,
> TengYao
>
> Kirk True 於 2024年9月16日 週一 下午11:45寫道：
>
> > Hi TengYao,
> >
> > +1 (non-binding).
> >
> > Using KAFKA-
+1 and thanks!
On Mon, Sep 23, 2024 at 6:36 AM Chia-Ping Tsai wrote:
> +1 and thanks David for volunteering!
>
> Best,
> Chia-Ping
>
> Josep Prat 於 2024年9月23日 週一 下午9:13寫道：
>
> > Thanks David for volunteering!
> > +1
> >
> > On Mon, Sep 23, 2024 at 3:11 PM David Jacot >
> > wrote:
> >
> > > Hi
ggestions.
>
> Best regards,
> Jiunn-Yang
>
>
> > Justine Olshan 於 2024年9月16日 晚上10:39 寫道：
> >
> > Hey there Jiunn-Yang,
> >
> > Thanks for taking the time to update the KIP. I noticed the section now
> has
> > some crossed out components. I am a l
Justine Olshan created KAFKA-8601:
-
Summary: Producer Improvement: Sticky Partitioner
Key: KAFKA-8601
URL: https://issues.apache.org/jira/browse/KAFKA-8601
Project: Kafka
Issue Type
Justine Olshan created KAFKA-8657:
-
Summary: Automatic Topic Creation on Producer
Key: KAFKA-8657
URL: https://issues.apache.org/jira/browse/KAFKA-8657
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-8601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-8601.
---
Resolution: Fixed
> Producer Improvement: Sticky Partitio
Justine Olshan created KAFKA-10496:
--
Summary: Create an in-memory DNS server for ClientUtilsTest and
ClusterConnectionStatesTest
Key: KAFKA-10496
URL: https://issues.apache.org/jira/browse/KAFKA-10496
[
https://issues.apache.org/jira/browse/KAFKA-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-14920.
Resolution: Fixed
> Address timeouts and out of order sequen
Justine Olshan created KAFKA-15380:
--
Summary: Try complete actions after callback
Key: KAFKA-15380
URL: https://issues.apache.org/jira/browse/KAFKA-15380
Project: Kafka
Issue Type: Sub-task
Justine Olshan created KAFKA-15404:
--
Summary: Failing Test
DynamicBrokerReconfigurationTest#testThreadPoolResize
Key: KAFKA-15404
URL: https://issues.apache.org/jira/browse/KAFKA-15404
Project
[
https://issues.apache.org/jira/browse/KAFKA-14984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-14984.
Resolution: Duplicate
> DynamicBrokerReconfigurationTest.testThreadPoolResize() test
Justine Olshan created KAFKA-15424:
--
Summary: Make verification a dynamic configuration
Key: KAFKA-15424
URL: https://issues.apache.org/jira/browse/KAFKA-15424
Project: Kafka
Issue Type
Justine Olshan created KAFKA-15449:
--
Summary: Verify Offset Commits too
Key: KAFKA-15449
URL: https://issues.apache.org/jira/browse/KAFKA-15449
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15424.
Resolution: Fixed
> Make verification a dynamic configurat
[
https://issues.apache.org/jira/browse/KAFKA-15380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15380.
Resolution: Fixed
> Try complete actions after callb
Justine Olshan created KAFKA-15459:
--
Summary: Convert coordinator retriable errors to a known producer
response error.
Key: KAFKA-15459
URL: https://issues.apache.org/jira/browse/KAFKA-15459
Project
[
https://issues.apache.org/jira/browse/KAFKA-15459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15459.
Resolution: Fixed
> Convert coordinator retriable errors to a known producer respo
Justine Olshan created KAFKA-15468:
--
Summary: Prevent transaction coordinator reloads on already loaded
leaders
Key: KAFKA-15468
URL: https://issues.apache.org/jira/browse/KAFKA-15468
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15449.
Resolution: Fixed
> Verify transactional offset commits (KIP-890 par
Justine Olshan created KAFKA-15545:
--
Summary: Update Request metrics in ops.html to reflect all the APIs
Key: KAFKA-15545
URL: https://issues.apache.org/jira/browse/KAFKA-15545
Project: Kafka
Justine Olshan created KAFKA-15546:
--
Summary: Transactions tool duration field confusing for completed
transactions
Key: KAFKA-15546
URL: https://issues.apache.org/jira/browse/KAFKA-15546
Project
Justine Olshan created KAFKA-15589:
--
Summary: Flaky kafka.server.FetchRequestTest
Key: KAFKA-15589
URL: https://issues.apache.org/jira/browse/KAFKA-15589
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-15589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15589.
Resolution: Duplicate
Duplicate of https://issues.apache.org/jira/browse/KAFKA-15566
Justine Olshan created KAFKA-15626:
--
Summary: Replace verification guard object with an specific type
Key: KAFKA-15626
URL: https://issues.apache.org/jira/browse/KAFKA-15626
Project: Kafka
Justine Olshan created KAFKA-15654:
--
Summary: Address Transactions Errors
Key: KAFKA-15654
URL: https://issues.apache.org/jira/browse/KAFKA-15654
Project: Kafka
Issue Type: Sub-task
Justine Olshan created KAFKA-15655:
--
Summary: Consider making transactional apis more compatible with
topic IDs
Key: KAFKA-15655
URL: https://issues.apache.org/jira/browse/KAFKA-15655
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-15626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15626.
Resolution: Fixed
> Replace verification guard object with an specific t
Justine Olshan created KAFKA-15674:
--
Summary: Consider making RequestLocal thread safe
Key: KAFKA-15674
URL: https://issues.apache.org/jira/browse/KAFKA-15674
Project: Kafka
Issue Type
Justine Olshan created KAFKA-15757:
--
Summary: Do not advertise v4 AddPartitionsToTxn to clients
Key: KAFKA-15757
URL: https://issues.apache.org/jira/browse/KAFKA-15757
Project: Kafka
Issue
Justine Olshan created KAFKA-15758:
--
Summary: Always schedule wrapped callbacks
Key: KAFKA-15758
URL: https://issues.apache.org/jira/browse/KAFKA-15758
Project: Kafka
Issue Type: Sub-task
Justine Olshan created KAFKA-15784:
--
Summary: Ensure atomicity of in memory update and write when
transactionally committing offsets
Key: KAFKA-15784
URL: https://issues.apache.org/jira/browse/KAFKA-15784
Justine Olshan created KAFKA-15797:
--
Summary: Flaky test
EosV2UpgradeIntegrationTest.shouldUpgradeFromEosAlphaToEosV2[true]
Key: KAFKA-15797
URL: https://issues.apache.org/jira/browse/KAFKA-15797
Justine Olshan created KAFKA-15798:
--
Summary: Flaky Test
NamedTopologyIntegrationTest.shouldAddAndRemoveNamedTopologiesBeforeStartingAndRouteQueriesToCorrectTopology()
Key: KAFKA-15798
URL: https
[
https://issues.apache.org/jira/browse/KAFKA-15653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-15653.
Fix Version/s: 3.7.0
3.6.1
Resolution: Fixed
> NPE
[
https://issues.apache.org/jira/browse/KAFKA-16513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-16513.
Resolution: Fixed
> Allow WriteTxnMarkers API with Alter Cluster Permiss
[
https://issues.apache.org/jira/browse/KAFKA-16692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-16692.
Fix Version/s: 3.6.3
Resolution: Fixed
> InvalidRequestExcept
Justine Olshan created KAFKA-16841:
--
Summary: ZKIntegrationTests broken
Key: KAFKA-16841
URL: https://issues.apache.org/jira/browse/KAFKA-16841
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-16841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-16841.
Resolution: Fixed
fixed by
https://github.com/apache/kafka/commit
Justine Olshan created KAFKA-16866:
--
Summary: RemoteLogManagerTest.testCopyQuotaManagerConfig failing
Key: KAFKA-16866
URL: https://issues.apache.org/jira/browse/KAFKA-16866
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-16990.
Resolution: Fixed
> Unrecognised flag passed to kafka-storage.sh in system t
[
https://issues.apache.org/jira/browse/KAFKA-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan reopened KAFKA-16990:
> Unrecognised flag passed to kafka-storage.sh in system t
[
https://issues.apache.org/jira/browse/KAFKA-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-16990.
Fix Version/s: 3.9.0
Resolution: Fixed
> Unrecognised flag passed to ka
Justine Olshan created KAFKA-17050:
--
Summary: Revert group.version for 3.8 and 3.9
Key: KAFKA-17050
URL: https://issues.apache.org/jira/browse/KAFKA-17050
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-17011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-17011.
Resolution: Fixed
> SupportedFeatures.MinVersion incorrectly blocks
Justine Olshan created KAFKA-17250:
--
Summary: Many system tests failing with
org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write
a non-default replicaDirectoryId at version 13
Key: KAFKA-17250
Justine Olshan created KAFKA-17355:
--
Summary: Update TestFeatureVersion 2 to always be based on
MetadataVersion.latestTesting
Key: KAFKA-17355
URL: https://issues.apache.org/jira/browse/KAFKA-17355
Justine Olshan created KAFKA-15957:
--
Summary:
ConsistencyVectorIntegrationTest.shouldHaveSamePositionBoundActiveAndStandBy
broken
Key: KAFKA-15957
URL: https://issues.apache.org/jira/browse/KAFKA-15957
Justine Olshan created KAFKA-15975:
--
Summary: Update kafka quickstart guide to no longer list ZK start
first
Key: KAFKA-15975
URL: https://issues.apache.org/jira/browse/KAFKA-15975
Project: Kafka
301 - 400 of 503 matches
Mail list logo
