Hey everyone. Regarding the status of KIP-125, just a heads up: I have an
implementation of KIP-125 (KAFKA-4513) here:
https://github.com/onurkaraman/kafka/commit/3b5448006ab70ba2b0b5e177853d191d0f777452
The code might need to be rebased. The steps described in the KIP are a bit
involved. Other th
; > >
> > > Hi, everyone,
> > >
> > > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> Onur
> > > Karaman.
> > >
> > > Onur's most significant work is the improvement of Kafka controller,
> > which
> &g
2017 at 3:05 PM, Ismael Juma wrote:
> >>
> >> > Thanks for the KIP, +1 (binding).
> >> >
> >> > On 27 Oct 2017 6:15 pm, "Onur Karaman"
> >> > wrote:
> >> >
> >> > > I'd like to start t
I'd like to start the vote for KIP-214: Add
zookeeper.max.in.flight.requests config to the broker
https://cwiki.apache.org/confluence/display/KAFKA/KIP-214%3A+Add+zookeeper.max.in.flight.requests+config+to+the+broker
- Onur
Done. I changed my KIP to KIP-214. So this KIP doesn't need to change.
On Wed, Oct 25, 2017 at 10:33 PM, Onur Karaman wrote:
> Looks like Jan technically made his KIP wiki page first so I'll just
> change my KIP number.
>
> On Wed, Oct 25, 2017 at 4:59 PM, Matthias J. Sax
2017 at 4:17 PM, Ted Yu wrote:
> This is for KAFKA-5894, right ?
> Please fill out the JIRA link.
>
> +1 on this proposal.
>
> On Wed, Oct 25, 2017 at 4:11 PM, Onur Karaman <
> onurkaraman.apa...@gmail.com>
> wrote:
>
> > Hey everyone.
> >
> >
Hey everyone.
Giving this another shot since it looks like there was a KIP number
collision on the wiki page.
I made a config kip, KIP-214: Add zookeeper.max.in.flight.requests config
to the broker:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-214%3A+Add+zookeeper.max.in.flight.requests+
Looks like Jan technically made his KIP wiki page first so I'll just change
my KIP number.
On Wed, Oct 25, 2017 at 4:59 PM, Matthias J. Sax
wrote:
> Thanks a lot for the KIP. Can we please move the discussion to the dev
> list?
>
> Thus, after fixing the KIP collision, just start a new DISCUSS t
Hey everyone.
I made a config kip, KIP-213: Add zookeeper.max.in.flight.requests config
to the broker:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-213%3A+Add+zookeeper.max.in.flight.requests+config+to+the+broker
Comments are welcome.
- Onur
Onur Karaman created KAFKA-6082:
---
Summary: consider fencing zookeeper updates with controller epoch
zkVersion
Key: KAFKA-6082
URL: https://issues.apache.org/jira/browse/KAFKA-6082
Project: Kafka
Onur Karaman created KAFKA-6081:
---
Summary: response error code checking
Key: KAFKA-6081
URL: https://issues.apache.org/jira/browse/KAFKA-6081
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman resolved KAFKA-5083.
-
Resolution: Fixed
This has been fixed in KAFKA-5642.
> always leave the last surviving member
Onur Karaman created KAFKA-6065:
---
Summary: Add zookeeper metrics to ZookeeperClient as in KIP-188
Key: KAFKA-6065
URL: https://issues.apache.org/jira/browse/KAFKA-6065
Project: Kafka
Issue
Onur Karaman created KAFKA-6014:
---
Summary: new consumer mirror maker halts after committing offsets
to a deleted topic
Key: KAFKA-6014
URL: https://issues.apache.org/jira/browse/KAFKA-6014
Project
Onur Karaman created KAFKA-5894:
---
Summary: add the notion of max inflight requests to async
ZookeeperClient
Key: KAFKA-5894
URL: https://issues.apache.org/jira/browse/KAFKA-5894
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman resolved KAFKA-4747.
-
Resolution: Won't Fix
[~junrao] pointed out that the distinction between tim-in-poll and
ti
[
https://issues.apache.org/jira/browse/KAFKA-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman resolved KAFKA-5703.
-
Resolution: Fixed
Woops. Looks like [~ijuma] already fixed this 3 days ago
Onur Karaman created KAFKA-5703:
---
Summary: allow debug-level logging for RequestChannel's request
logger
Key: KAFKA-5703
URL: https://issues.apache.org/jira/browse/KAFKA-5703
Project:
[
https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman resolved KAFKA-5501.
-
Resolution: Fixed
> introduce async ZookeeperCli
Onur Karaman created KAFKA-5642:
---
Summary: use async ZookeeperClient everywhere
Key: KAFKA-5642
URL: https://issues.apache.org/jira/browse/KAFKA-5642
Project: Kafka
Issue Type: Sub-task
In other words, I think the default should be the exact behavior we have
today plus the remaining group information from DescribeGroupResponse.
On Fri, Jul 14, 2017 at 11:36 AM, Onur Karaman wrote:
> I think if we had the opportunity to start from scratch, --describe would
> have be
I think if we had the opportunity to start from scratch, --describe would
have been the following:
--describe --offsets: shows all offsets committed for the group as well as
lag
--describe --state (or maybe --members): shows the full
DescribeGroupResponse output (including things like generation id
Onur Karaman created KAFKA-5502:
---
Summary: read current brokers from zookeeper upon processing
broker change
Key: KAFKA-5502
URL: https://issues.apache.org/jira/browse/KAFKA-5502
Project: Kafka
Onur Karaman created KAFKA-5501:
---
Summary: use async zookeeper apis everywhere
Key: KAFKA-5501
URL: https://issues.apache.org/jira/browse/KAFKA-5501
Project: Kafka
Issue Type: Sub-task
+1
On Thu, Jun 22, 2017 at 10:05 AM, Dong Lin wrote:
> Thanks for the KIP. +1 (non-binding)
>
> 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/dis
This metric sounds simple and useful.
+1
On Fri, Jun 16, 2017 at 9:09 AM, Abhishek Mendhekar <
abhishek.mendhe...@gmail.com> wrote:
> Hi Kafka Dev,
>
> I created KIP-168 to propose adding a metric to emit total topic count
> in a cluster. The metric will be emited by the controller.
>
> The KIP
[
https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035465#comment-16035465
]
Onur Karaman commented on KAFKA-4595:
-
[~ijuma] Yeah I think KAFKA-5028 solved
[
https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035365#comment-16035365
]
Onur Karaman commented on KAFKA-1595:
-
Sounds good.
> Remove deprecated and
[
https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032276#comment-16032276
]
Onur Karaman edited comment on KAFKA-1595 at 6/1/17 12:5
[
https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032276#comment-16032276
]
Onur Karaman commented on KAFKA-1595:
-
I think [~ijuma]'s PR (https://g
@Colin checkout kafka.admin.ZkSecurityMigrator. This is what I meant in my
earlier comment on "acl off zookeeper"
On Tue, May 30, 2017 at 3:39 PM Colin McCabe wrote:
> It seems like, to make it really secure, we need the enforcement to be
> done at the ZooKepeer level. Any broker or client-side
Just for completeness, I think one option is to:
1. Upgrade broker-side auto topic creation to send CreateTopicsRequest.
This is just to unify the topic creation flow and policy enforcement.
2. Migrate all clients away from topic creation from zookeeper and instead
send CreateTopicsRequest
3. ACL o
Would it make sense to resolve KAFKA-4893 before enabling it by default, as
fixing the ticket would likely involve changing the log directory structure?
On Fri, May 26, 2017 at 3:24 PM, Guozhang Wang wrote:
> I'd say just remove those two lines.
>
> On Fri, May 26, 2017 at 7:55 AM, Gwen Shapira
[
https://issues.apache.org/jira/browse/KAFKA-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027086#comment-16027086
]
Onur Karaman commented on KAFKA-5328:
-
I copied the topic assignment znodes
Onur Karaman created KAFKA-5328:
---
Summary: consider switching json parser from scala to jackson
Key: KAFKA-5328
URL: https://issues.apache.org/jira/browse/KAFKA-5328
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5323:
Status: Patch Available (was: Open)
> AdminUtils.createTopic should check topic existence upfr
[
https://issues.apache.org/jira/browse/KAFKA-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024223#comment-16024223
]
Onur Karaman commented on KAFKA-5323:
-
This can have a larger impact than one m
Onur Karaman created KAFKA-5323:
---
Summary: AdminUtils.createTopic should check topic existence
upfront
Key: KAFKA-5323
URL: https://issues.apache.org/jira/browse/KAFKA-5323
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5310:
Status: Patch Available (was: Open)
> reset ControllerContext during resignat
[
https://issues.apache.org/jira/browse/KAFKA-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5310:
Description:
This ticket is all about ControllerContext initialization and teardown. The key
Onur Karaman created KAFKA-5310:
---
Summary: reset ControllerContext during resignation
Key: KAFKA-5310
URL: https://issues.apache.org/jira/browse/KAFKA-5310
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020447#comment-16020447
]
Onur Karaman commented on KAFKA-4896:
-
handleGroupImmigration only gets called
[
https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5258:
Description:
Today the PartitionStateMachine and ReplicaStateMachine defines and asserts the
valid
[
https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5258:
Description:
Today the PartitionStateMachine and ReplicaStateMachine defines and asserts the
valid
[
https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5258:
Summary: move all partition and replica state transition rules into their
states (was: move all
[
https://issues.apache.org/jira/browse/KAFKA-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013665#comment-16013665
]
Onur Karaman commented on KAFKA-5261:
-
Would one alternative be to just ma
[
https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5258:
Status: Patch Available (was: In Progress)
> move all partition and replica state transition ru
[
https://issues.apache.org/jira/browse/KAFKA-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5258 started by Onur Karaman.
---
> move all partition and replica state transition rules into a
Onur Karaman created KAFKA-5258:
---
Summary: move all partition and replica state transition rules
into a map
Key: KAFKA-5258
URL: https://issues.apache.org/jira/browse/KAFKA-5258
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011851#comment-16011851
]
Onur Karaman edited comment on KAFKA-5175 at 5/16/17 7:0
[
https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011851#comment-16011851
]
Onur Karaman commented on KAFKA-5175:
-
Cool. I can steadily reproduce thi
[
https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011500#comment-16011500
]
Onur Karaman commented on KAFKA-5175:
-
Thanks [~ijuma]. I've been staring at
[
https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010823#comment-16010823
]
Onur Karaman commented on KAFKA-3356:
-
I agree with [~jeffwidman].
>
[
https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5180:
Status: Patch Available (was: In Progress)
> Transient fail
[
https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5180 started by Onur Karaman.
---
> Transient fail
[
https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman resolved KAFKA-5120.
-
Resolution: Fixed
KAFKA-5028 has been checked in so this should no longer be an issue.
> Seve
[
https://issues.apache.org/jira/browse/KAFKA-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman resolved KAFKA-3107.
-
Resolution: Fixed
This problem should no longer exist after KAFKA-5028.
> Error when trying
e expect.
> >> 6. EventAckTime: The time waiting for all the corresponding responses.
> >> 7. EventHandlingTotalTime: sum of 2-6
> >>
> >> Note that all the metrics are from the event and cluster wide state
> >> transition point of view, but not from a si
I had a similar comment to Becket but accidentally posted it on the vote
thread last Friday. From that thread:
"I noticed that both the ControllerState metric and the *RateAndTimeMs metrics
only cover a subset of the controller event types. Was this intentional?"
I think it makes most sense to jus
[
https://issues.apache.org/jira/browse/KAFKA-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5197:
Status: Patch Available (was: In Progress)
> add a tool analyzing zookeeper client performa
[
https://issues.apache.org/jira/browse/KAFKA-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5197 started by Onur Karaman.
---
> add a tool analyzing zookeeper client performance across its various a
Onur Karaman created KAFKA-5197:
---
Summary: add a tool analyzing zookeeper client performance across
its various apis
Key: KAFKA-5197
URL: https://issues.apache.org/jira/browse/KAFKA-5197
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000261#comment-16000261
]
Onur Karaman commented on KAFKA-5099:
-
By the way, I reran the file descri
[
https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999250#comment-15999250
]
Onur Karaman commented on KAFKA-5099:
-
I ran the file descriptor experiment aga
I noticed that both the ControllerState metric and the *RateAndTimeMs
metrics only cover a subset of the controller event types. Was this
intentional?
On Fri, May 5, 2017 at 6:03 PM, Gwen Shapira wrote:
> +1
>
> On Thu, May 4, 2017 at 7:34 PM, Ismael Juma wrote:
>
> > Hi everyone,
> >
> > It se
[
https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999200#comment-15999200
]
Onur Karaman commented on KAFKA-5099:
-
Hi [~junrao]. Thanks for figuring it ou
Looks good. Thanks!
On Fri, May 5, 2017 at 4:44 PM, Roger Hoover wrote:
> Very helpful. Thank you, Jun.
>
> On Fri, May 5, 2017 at 4:42 PM, Guozhang Wang wrote:
>
> > Jun,
> >
> > Thanks for the KIP, LGTM.
> >
> > Guozhang
> >
> > On Fri, May 5, 2017 at 3:38 PM, Ismael Juma wrote:
> >
> > > T
[
https://issues.apache.org/jira/browse/KAFKA-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman reassigned KAFKA-5180:
---
Assignee: Onur Karaman
> Transient fail
[
https://issues.apache.org/jira/browse/KAFKA-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman reassigned KAFKA-5175:
---
Assignee: Onur Karaman
> Transient fail
Regarding the ControllerState and the potential for overlap, I think it
depends on our definition of controller state. While KAFKA-5028 allows only
a single ControllerEvent to be processed at a time, it still allows
interleavings for long-lasting actions like partition reassignment and
topic deleti
[
https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5107:
Status: Patch Available (was: In Progress)
> remove preferred replica election state f
[
https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5107 started by Onur Karaman.
---
> remove preferred replica election state from ControllerCont
[
https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987101#comment-15987101
]
Onur Karaman commented on KAFKA-5028:
-
Shortly after check-in, I noticed a bug:
[
https://issues.apache.org/jira/browse/KAFKA-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982118#comment-15982118
]
Onur Karaman commented on KAFKA-5120:
-
This will be fixed in KAFKA-5028. It cho
[
https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5107:
Summary: remove preferred replica election state from ControllerContext
(was: investigate removing
Onur Karaman created KAFKA-5107:
---
Summary: investigate removing preferred replica leader election
state from ControllerContext
Key: KAFKA-5107
URL: https://issues.apache.org/jira/browse/KAFKA-5107
[
https://issues.apache.org/jira/browse/KAFKA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977902#comment-15977902
]
Onur Karaman commented on KAFKA-5099:
-
My initial guess is that the new e
Onur Karaman created KAFKA-5099:
---
Summary: Replica Deletion Regression from KIP-101
Key: KAFKA-5099
URL: https://issues.apache.org/jira/browse/KAFKA-5099
Project: Kafka
Issue Type: Bug
Onur Karaman created KAFKA-5083:
---
Summary: always leave the last surviving member of the ISR in ZK
Key: KAFKA-5083
URL: https://issues.apache.org/jira/browse/KAFKA-5083
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5069:
Status: Patch Available (was: In Progress)
> add controller integration te
[
https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5028:
Status: Patch Available (was: In Progress)
> convert kafka controller to a single-threaded ev
[
https://issues.apache.org/jira/browse/KAFKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5069 started by Onur Karaman.
---
> add controller integration te
Onur Karaman created KAFKA-5069:
---
Summary: add controller integration tests
Key: KAFKA-5069
URL: https://issues.apache.org/jira/browse/KAFKA-5069
Project: Kafka
Issue Type: Sub-task
Hi Damian.
Can you copy the point Becket made earlier that you say isn't addressed?
On Thu, Apr 6, 2017 at 2:51 AM, Damian Guy wrote:
> Thanks all, the Vote is now closed and the KIP has been accepted with 9 +1s
>
> 3 binding::
> Guozhang,
> Jason,
> Ismael
>
> 6 non-binding:
> Bill,
> Eno,
> M
Onur Karaman created KAFKA-5029:
---
Summary: cleanup javadocs and logging
Key: KAFKA-5029
URL: https://issues.apache.org/jira/browse/KAFKA-5029
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5028 started by Onur Karaman.
---
> convert kafka controller to a single-threaded event queue mo
[
https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-5028:
Summary: convert kafka controller to a single-threaded event queue model
(was: Convert Kafka
Onur Karaman created KAFKA-5028:
---
Summary: Convert Kafka Controller to a single-threaded event queue
model
Key: KAFKA-5028
URL: https://issues.apache.org/jira/browse/KAFKA-5028
Project: Kafka
Onur Karaman created KAFKA-5027:
---
Summary: Kafka Controller Redesign
Key: KAFKA-5027
URL: https://issues.apache.org/jira/browse/KAFKA-5027
Project: Kafka
Issue Type: Improvement
bably safer than letting the
> group members to guess the state of a group. Can you elaborate a little bit
> on your idea?
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
> On Mon, Apr 3, 2017 at 8:16 AM, Onur Karaman >
> wrote:
>
> > Hi Damian.
> >
> > After
Hi Damian.
After reading the discussion thread again, it still doesn't seem like the
thread discussed the option I mentioned earlier.
>From what I had understood from the broker-side vs. client-side config
debate was that the client-side config from the discussion would cause a
wire format change
It seems like there generally has been the assumption that the broker needs
to know about this delay either from its own config or provided over the
wire from clients. Is this actually true?
One alternative I don't think was mentioned was to make this delay concept
be completely client-side.
What
[
https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-4959:
Status: Patch Available (was: In Progress)
> remove controller concurrent access to non-threads
[
https://issues.apache.org/jira/browse/KAFKA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-4959 started by Onur Karaman.
---
> remove controller concurrent access to non-threadsafe NetworkClient,
> Se
Onur Karaman created KAFKA-4959:
---
Summary: remove controller concurrent access to non-threadsafe
NetworkClient, Selector, and SSLEngine
Key: KAFKA-4959
URL: https://issues.apache.org/jira/browse/KAFKA-4959
[
https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943568#comment-15943568
]
Onur Karaman commented on KAFKA-4900:
-
[~nickt] Do you think it makes sense for m
[
https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941296#comment-15941296
]
Onur Karaman commented on KAFKA-4900:
-
I haven't figured out some of
[
https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929447#comment-15929447
]
Onur Karaman commented on KAFKA-4900:
-
Okay yeah with bad znode data, I could see
[
https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927298#comment-15927298
]
Onur Karaman commented on KAFKA-4893:
-
Also [~vahid] while I agree reducing the l
[
https://issues.apache.org/jira/browse/KAFKA-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927200#comment-15927200
]
Onur Karaman commented on KAFKA-4900:
-
I hadn't yet investigated why so
1 - 100 of 508 matches
Mail list logo
