ve an opt-in way of returning an error, if people feel
strongly. But honestly #2 is much less of an issue in practice.
best,
Colin
>
> Ryanne
>
> On Tue, Jun 1, 2021 at 12:31 PM Colin McCabe wrote:
>
> > On Tue, Jun 1, 2021, at 07:00, Nakamura wrote:
> > > Hi Colin,
&
Hi all,
I have posted a KIP about updating the KRaft metadata records for 3.0.
Check it out at : https://cwiki.apache.org/confluence/x/34zOCg
best,
Colin
Colin McCabe created KAFKA-12877:
Summary: Fix KRPC files with missing flexibleVersions annotation
Key: KAFKA-12877
URL: https://issues.apache.org/jira/browse/KAFKA-12877
Project: Kafka
/O.)
best,
Colin
> I think there's something I'm missing here. Would you mind helping me
> figure out what it is?
>
> Best,
> Moses
>
> On Sun, May 30, 2021 at 5:35 PM Colin McCabe wrote:
>
> > On Tue, May 25, 2021, at 11:26, Nakamura wrote:
> > > Hey Colin,
o you describe of kafka clients producing too many messages,
> as you said buffering is what should be done but I wouldn't classify this
> as blocking.
>
> On Mon, May 24, 2021 at 7:54 PM Colin McCabe wrote:
>
> > Hi all,
> >
> > I agree that we should give use
ork
communication in the producer and consumer.
best,
Colin
> Best,
> Moses
>
> On Mon, May 24, 2021 at 1:54 PM Colin McCabe wrote:
>
> > Hi all,
> >
> > I agree that we should give users the option of having a fully async API,
> > but I don't think external thre
Colin McCabe created KAFKA-12864:
Summary: Move KafkaEventQueue and timeline data structures into
server-common
Key: KAFKA-12864
URL: https://issues.apache.org/jira/browse/KAFKA-12864
Project: Kafka
Colin McCabe created KAFKA-12853:
Summary: Implement broker-side KRaft snapshots
Key: KAFKA-12853
URL: https://issues.apache.org/jira/browse/KAFKA-12853
Project: Kafka
Issue Type
On Wed, May 26, 2021, at 07:18, Ismael Juma wrote:
> Hi Konstantine,
>
> Looking at the schedule and some of the ongoing work in KIP-500 (one of the
> KIPs that is important to land in 3.0), I think we'll need a bit more time.
> We definitely do not want to cause a disruption to our time-based
Hi all,
I agree that we should give users the option of having a fully async API, but I
don't think external thread pools or queues are the right direction to go here.
They add performance overheads and don't address the root causes of the problem.
There are basically two scenarios where we
; On Fri, Apr 2, 2021 at 10:48 AM Colin McCabe wrote:
>
> > Hi Ryanne,
> >
> > Thanks for the response. It would be good to have a PR for KIP-382, I
> > agree.
> >
> > Perhaps one possible compromise for KIP-712 would be to make the changes
> > in MM2
Colin McCabe created KAFKA-12803:
Summary: Support reassigning partitions when in KRaft mode
Key: KAFKA-12803
URL: https://issues.apache.org/jira/browse/KAFKA-12803
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12788.
--
Fix Version/s: 3.0.0
Reviewer: Jun Rao
Resolution: Fixed
> Improve KR
Colin McCabe created KAFKA-12792:
Summary: Fix metrics bug and introduce TimelineInteger
Key: KAFKA-12792
URL: https://issues.apache.org/jira/browse/KAFKA-12792
Project: Kafka
Issue Type
Colin McCabe created KAFKA-12788:
Summary: Improve KRaft replica placement
Key: KAFKA-12788
URL: https://issues.apache.org/jira/browse/KAFKA-12788
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12471.
--
Fix Version/s: 3.0.0
Resolution: Fixed
> Implement createPartitions in KIP-500 m
[
https://issues.apache.org/jira/browse/KAFKA-12334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12334.
--
Fix Version/s: 2.8.0
Resolution: Fixed
Added in 2.8
> Add the KIP-631 metadata sh
[
https://issues.apache.org/jira/browse/KAFKA-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12275.
--
Fix Version/s: 2.8.0
Assignee: Colin McCabe
Resolution: Fixed
Colin McCabe created KAFKA-12783:
Summary: Remove the deprecated ZK-based partition reassignment API
Key: KAFKA-12783
URL: https://issues.apache.org/jira/browse/KAFKA-12783
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-1676.
-
Fix Version/s: 2.5.0
Assignee: Colin McCabe
Resolution: Fixed
> Abil
[
https://issues.apache.org/jira/browse/KAFKA-9520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-9520.
-
Fix Version/s: 2.5.0
Assignee: Colin McCabe
Resolution: Fixed
We deprecated ZK
[
https://issues.apache.org/jira/browse/KAFKA-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-4712.
-
Resolution: Cannot Reproduce
This seems to be related to overall load on the cluster as a result
Colin McCabe created KAFKA-12778:
Summary: QuorumController should honor request timeouts
Key: KAFKA-12778
URL: https://issues.apache.org/jira/browse/KAFKA-12778
Project: Kafka
Issue Type
consider this an
> implementation detail and defer the decision?
>
> Thanks to all who have voted so far!
> -David
>
> On Thu, May 6, 2021 at 4:01 PM Colin McCabe wrote:
>
> > Sorry, I meant to write "AllocateProducerIdsRecord" in the previous
> > messag
Sorry, I meant to write "AllocateProducerIdsRecord" in the previous message.
-C.
On Thu, May 6, 2021, at 12:58, Colin McCabe wrote:
> Hi David,
>
> Thanks for the KIP -- it looks good.
>
> It seems like we should be clear that the new RPC should be used for
> bot
Hi David,
Thanks for the KIP -- it looks good.
It seems like we should be clear that the new RPC should be used for both the
ZK and KRaft cases. I think that is implied, but it would be good to spell it
out just to be clear. As the KIP explains, this is needed for the bridge
release.
I
Colin McCabe created KAFKA-12755:
Summary: Add server-common, server-tools gradle modules
Key: KAFKA-12755
URL: https://issues.apache.org/jira/browse/KAFKA-12755
Project: Kafka
Issue Type
Colin McCabe created KAFKA-12733:
Summary: KRaft: always bump leader epoch when changing the ISR for
a controlled shutdown
Key: KAFKA-12733
URL: https://issues.apache.org/jira/browse/KAFKA-12733
d `FaultyRecordException` (don't like this name
> >> too much
> >> > > > >>> >> honestly, but don't have a better idea for it anyway).
> >> > > > >>> >>
> >> > > > >>> >> Side remark. If we introduce class
>
Hi feyman2009,
Thanks for the PR. I pinged a few people about reviewing it. I don't know if
anyone will be able to look at it this week, but probably next week we can.
The good news is that this field is optional (tagged) so the protocol will
still work with older clients.
best,
Colin
On
Hi John,
+1 (binding) from me.
I performed the following:
1. Built the project from the source code tar file, kafka-2.8.0-src.tgz
2. Ran all of the junit tests locally via "./gradlew test
-PignoreFailures=true". I had one failure in
SocketServerTest#testIdleConnection, which I was not able
[
https://issues.apache.org/jira/browse/KAFKA-9119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-9119.
-
Fix Version/s: 2.8.0
Resolution: Done
> KIP-500: Replace ZooKeeper with a Metadata Quo
[
https://issues.apache.org/jira/browse/KAFKA-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-9125.
-
Fix Version/s: 2.8.0
Assignee: Ron Dagostino (was: Viktor Somogyi-Vass
[
https://issues.apache.org/jira/browse/KAFKA-9166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-9166.
-
Fix Version/s: 2.8.0
Resolution: Duplicate
Closing as duplicate of KAFKA-10435
[
https://issues.apache.org/jira/browse/KAFKA-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-9124.
-
Fix Version/s: 2.7.0
Resolution: Fixed
> KIP-497: ISR changes should be propagated
[
https://issues.apache.org/jira/browse/KAFKA-12345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12345.
--
Fix Version/s: 2.8.0
Assignee: Boyang Chen
Resolution: Fixed
> KIP-
[
https://issues.apache.org/jira/browse/KAFKA-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12282.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> KIP-500: Reconcile configuration variab
[
https://issues.apache.org/jira/browse/KAFKA-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12276.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> Add KIP-500 controller c
Colin McCabe created KAFKA-12670:
Summary: KRaft support for unclean.leader.election.enable
Key: KAFKA-12670
URL: https://issues.apache.org/jira/browse/KAFKA-12670
Project: Kafka
Issue Type
interfaces/classes.
> > >
> > >
> > >
> > https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/record/Records.java
> > > and
> > >
> > >
> > https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/a
Hi Soumyajit,
I believe we've had discussions about proposals similar to this before,
although I'm having trouble finding one right now. The issue here is that
Record is a private class -- it is not part of any public API, and may change
at any time. So we can't expose it in public APIs.
eality is that MM1 has been sort of unofficially deprecated
> for a long time, so people are understandably disinterested in landing new
> features there. But let's have that debate in the KIP-712 thread. I believe
> we'd be having the same discussion there with or without KIP-720 passing.
&
+1 (binding). Thanks for the KIP.
Colin
On Tue, Mar 30, 2021, at 20:36, Chia-Ping Tsai wrote:
> Thanks for this KIP. +1 (binding)
>
> On 2021/03/29 15:34:55, Tom Bentley wrote:
> > Hi,
> >
> > I'd like to start a vote on KIP-707, which proposes to add
> > KafkaFuture.toCompletionStage(),
On Thu, Apr 1, 2021, at 09:45, Jun Rao wrote:
> Hi, Henry,
>
> Thanks for the response.
>
> 1. I agree with Tom that it's worth thinking about a separate class for
> shallow iteration instead of trying to add more complexity into the
> existing producer/consumer API. We could potentially make
Thanks for bringing this up, Ismael. I agree that we need to figure this out
before we accept this KIP.
If MM1 is deprecated, then that means we are telling users they need to migrate
away from it as soon as they can. I think that rules out adding big new
features to MM1, unless those
Hi Andrei,
Kafka intentionally sets TCP_NODELAY in order to disable Nagle's algorithm.
The reason is because Nagle's algorithm can cause to long latencies in Kafka
RPC.
Wikipedia explains the problem:
> [Nagle's] algorithm interacts badly with TCP delayed acknowledgments
> (delayed ACK),
Congratulations, Tom!
Colin
On Fri, Mar 19, 2021, at 08:09, Viktor Somogyi-Vass wrote:
> Congrats Tom! :)
>
> On Wed, Mar 17, 2021 at 3:47 PM Chia-Ping Tsai wrote:
>
> > Congratulations!!!
> >
> > On 2021/03/15 17:59:56, Mickael Maison wrote:
> > > Hi all,
> > >
> > > The PMC for Apache
[
https://issues.apache.org/jira/browse/KAFKA-12376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12376.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> Use scheduleAtomicAppend for reco
[
https://issues.apache.org/jira/browse/KAFKA-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12382.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> Create KIP-500 README for the 2.8 rele
Colin McCabe created KAFKA-12471:
Summary: Implement createPartitions in KIP-500 mode
Key: KAFKA-12471
URL: https://issues.apache.org/jira/browse/KAFKA-12471
Project: Kafka
Issue Type: New
Colin McCabe created KAFKA-12439:
Summary: When in KIP-500 mode, we should be able to assign new
partitions to nodes that are fenced
Key: KAFKA-12439
URL: https://issues.apache.org/jira/browse/KAFKA-12439
Colin McCabe created KAFKA-12432:
Summary: AdminClient will not honor connection setup or request
timeouts in some cases
Key: KAFKA-12432
URL: https://issues.apache.org/jira/browse/KAFKA-12432
Colin McCabe created KAFKA-12383:
Summary: Get RaftClusterTest.java and other KIP-500 junit tests
working
Key: KAFKA-12383
URL: https://issues.apache.org/jira/browse/KAFKA-12383
Project: Kafka
Colin McCabe created KAFKA-12382:
Summary: Create KIP-500 README for the 2.8 rleease
Key: KAFKA-12382
URL: https://issues.apache.org/jira/browse/KAFKA-12382
Project: Kafka
Issue Type: Bug
Colin McCabe created KAFKA-12381:
Summary: Incompatible change in verifiable_producer.log in 2.8
Key: KAFKA-12381
URL: https://issues.apache.org/jira/browse/KAFKA-12381
Project: Kafka
Issue
Colin McCabe created KAFKA-12349:
Summary: Follow up on PartitionEpoch in KIP-500
Key: KAFKA-12349
URL: https://issues.apache.org/jira/browse/KAFKA-12349
Project: Kafka
Issue Type
Colin McCabe created KAFKA-12334:
Summary: Add the KIP-631 metadata shell
Key: KAFKA-12334
URL: https://issues.apache.org/jira/browse/KAFKA-12334
Project: Kafka
Issue Type: Improvement
PI that matches,
> to avoid more confusion).
>
> Any objections?
>
> On Fri, Dec 18, 2020 at 10:08 AM Jun Rao wrote:
> >
> > Hi, Colin,
> >
> > Thanks for the reply. The KIP looks good to me now. Thanks for your
> > diligence.
> >
> > Jun
> >
Hi Gaurav,
There will be a preview of KIP-500 in Apache Kafka 2.8, like we discussed
earlier. Hope this helps.
best,
Colin
On Wed, Jan 27, 2021, at 22:57, gaurav chhabra wrote:
> Hi Team,
>
> Can you please help on the timelines of the below?
>
> Is it confirmed for Apache Kafka version
Colin McCabe created KAFKA-12276:
Summary: Add KIP-500 controller code
Key: KAFKA-12276
URL: https://issues.apache.org/jira/browse/KAFKA-12276
Project: Kafka
Issue Type: Improvement
Hi Manojbvn,
Thanks for the question. It's good to know that people are enthusiastic about
this work!
We're hoping to have an alpha version of ZK-free operation in the next Apache
Kafka release. The alpha version will not be suitable for production, and will
not implement all Kafka
Colin McCabe created KAFKA-12214:
Summary: Generated code does not include UUID or struct fields in
its toString output
Key: KAFKA-12214
URL: https://issues.apache.org/jira/browse/KAFKA-12214
Project
[
https://issues.apache.org/jira/browse/KAFKA-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12208.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> Rename AdminManager to ZkAdminMana
Colin McCabe created KAFKA-12209:
Summary: Add the timeline data structures for the KIP-631
controller
Key: KAFKA-12209
URL: https://issues.apache.org/jira/browse/KAFKA-12209
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12183.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> Add the KIP-631 metadata record definiti
Colin McCabe created KAFKA-12208:
Summary: Rename AdminManager to ZkAdminManager
Key: KAFKA-12208
URL: https://issues.apache.org/jira/browse/KAFKA-12208
Project: Kafka
Issue Type
Colin McCabe created KAFKA-12206:
Summary: o.a.k.common.Uuid should implement Comparable
Key: KAFKA-12206
URL: https://issues.apache.org/jira/browse/KAFKA-12206
Project: Kafka
Issue Type
Colin McCabe created KAFKA-12183:
Summary: Add the KIP-631 metadata record definitions
Key: KAFKA-12183
URL: https://issues.apache.org/jira/browse/KAFKA-12183
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-12180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-12180.
--
Fix Version/s: 2.8.0
Resolution: Fixed
> Implement the KIP-631 message genera
,
Colin
On Tue, Jan 5, 2021, at 17:03, Colin McCabe wrote:
> Hi all,
>
> Addendum: some of the port types in this KIP were specified as int16 in
> the wire protocol. But this does not gracefully handle ports like
> 33,000, which shows up as negative when using a signed 16 bit numb
Colin McCabe created KAFKA-12180:
Summary: Implement the KIP-631 message generator changes
Key: KAFKA-12180
URL: https://issues.apache.org/jira/browse/KAFKA-12180
Project: Kafka
Issue Type
int32. This is
consistent with what we do in MetadataResponse and a few other places.
best,
Colin
On Mon, Dec 21, 2020, at 14:42, Colin McCabe wrote:
> Hi all,
>
> With non-binding +1 votes from Ron Dagostino, Tom Bentley and Unmesh
> Joshi, and binding +1 votes from David Arthur,
Hi all,
With non-binding +1 votes from Ron Dagostino, Tom Bentley and Unmesh Joshi, and
binding +1 votes from David Arthur, Boyang Chen, Jason Gusafson, Ismael Juma,
David Jacot, Jun Rao, the KIP passes.
thanks, all!
cheers,
Colin
On Fri, Dec 18, 2020, at 12:42, Colin McCabe wrote:
> Hi
e new API and to
> > add new information with separate KIPs. There might be more information
> > that we want to add as part of KIP-500.
> >
> > I will be happy to hear what other members of the community think about
> > this.
> >
> > Best,
>
this KIP, Colin. The KIP is really well written. This is
> > so exciting!
> >
> > +1 (binding)
> >
> > Best,
> > David
> >
> > On Wed, Dec 16, 2020 at 11:51 PM Colin McCabe wrote:
> >
> > > On Wed, Dec 16, 2020, at 13:08, Ismael Ju
t; the sasl mechanism for the communication between the broker and the
> controller.
>
Hi Jun,
Yeah... sounds like we could use a new configuration key for this. I added
sasl.mechanism.controller.protocol for this.
regards,
Colin
> Jun
>
> On Thu, Dec 17, 2020 at 2:29 PM Colin
d port, the
client would have no way to connect since it doesn't know what security
settings to use.
regards,
Colin
> Jun
>
> On Wed, Dec 16, 2020 at 9:13 PM Colin McCabe wrote:
>
> > On Wed, Dec 16, 2020, at 18:13, Jun Rao wrote:
> > > Hi, Colin,
> > >
&g
on't appear in the MetadataResponses returned to clients,
since clients can't access them. I should have been more clear about that in
the KIP-- I added a sentence to "Networking" describing this.
best,
Colin
>
> Thanks,
>
> Jun
>
> On Wed, Dec 16, 2020 at 4:23 PM Col
Hi David,
This seems reasonable. It would be nice to have an API specifically for
describeCluster, so that we could extend this API without adding more fields to
the already large MetadataRequest.
As you mention in the KIP, KIP-700 would allow us to deprecate
end to a
controller that has just recently become inactive. In that case NOT_CONTROLLER
would be returned. (A standby controller returns NOT_CONTROLLER for most APIs).
> 221. Could we add the required ACL for the new requests?
>
Good point. I added the required ACL for each new RPC.
be
.
> 11. Broker metrics typically have a PerSec suffix, should we stick with
> that for the `MetadataCommitRate`?
Added.
> 12. For the lag metrics, would it be clearer if we included "Offset" in the
> name? In theory, we could have time based lag metrics too. Having said
> t
t; > > > > -David
> > > > >
> > > > > On Sat, Dec 12, 2020 at 7:46 AM Ron Dagostino
> > > wrote:
> > > > >
> > > > > > Thanks for shepherding this KIP through the extended discussion,
> > > Co
tells you partition X is on nodes A, B, and C. If you don't have the ZK
registration for one or more of A, B, or C then you don't know whether we are
following the policy of "two replicas on one rack, one replica on another." Or
any other more complex rack placement policy that you might
tup process. After the
startup process is finished, it ignores this boolean.
The broker uses fence / unfence records in the metadata log to determine which
brokers should appear in its MetadataResponse.
best,
Colin
> Jun
>
> On Tue, Dec 15, 2020 at 8:51 AM Colin McCabe wrote:
is a good fit. So it would be good to understand about how
> you're making this backward compatible for clients.
>
> Many thanks,
>
> Tom
>
> On Tue, Dec 15, 2020 at 1:42 AM Colin McCabe wrote:
>
> > On Fri, Dec 11, 2020, at 17:07, Jun Rao wrote:
> >
Heartbeat still references currentState and targetState.
>
Thanks. I've made these sections clearer and removed the obsolete references
to sending states.
best,
Colin
> Jun
>
> On Fri, Dec 11, 2020 at 1:33 PM Colin McCabe wrote:
>
> > On Wed, Dec 9, 2020, at 10:10, Jun Rao wro
Hi all,
I'd like to restart the vote on KIP-631: the quorum-based Kafka Controller.
The KIP is here:
https://cwiki.apache.org/confluence/x/4RV4CQ
The original DISCUSS thread is here:
, but this hasn't been implemented
yet.
best,
Colin
>
> Jun
>
>
>
>
> On Tue, Dec 8, 2020 at 5:27 PM Colin McCabe wrote:
>
> > On Thu, Dec 3, 2020, at 16:37, Jun Rao wrote:
> > > Hi, Colin,
> > >
> > > Thanks for the updated KIP.
ges or
> streams.
> Therefore I'd expect them to use these plug-in point implementations
> with due care, or else they risk extinction by survival of the fittest ...
> :-)
>
> cheers
> Edoardo
>
> On Wed, 2 Dec 2020 at 18:46, Colin McCabe wrote:
>
> > Hi Mickae
ast step, that scrubs all metadata about the topic. In
order to get to that last step, the topic data needs to removed from all
brokers (after each broker notices that the topic is being deleted).
best,
Colin
> Jun
>
> On Wed, Dec 2, 2020 at 2:50 PM Colin McCabe wrote:
>
> >
ry. Similarly with the
> controller.id value on controllers -- it would allow the same type of
> sanity check for quorum controllers.
>
That's a good point. I will add broker.id back, and also add controller.id as
a possibility.
cheers,
Colin
>
> On Mon, Nov 30, 2020 at 7:41 PM C
Hi Mickael,
To be honest, I think it would be better not to make replica placement
pluggable.
When I worked on the Hadoop Distributed Filesystem, we supported pluggable
replica placement policies, and it never worked out well. Users would write
plugin code that ran in a very sensitive
on every log append.
>
Given that the new broker epoch won't be visible until the commit has happened,
I have changed this to "the next available offset in the log"
> 104. REGISTERING(1) : It says "Otherwise, the broker moves into the FENCED
> state.". It seems
Colin McCabe created KAFKA-10703:
Summary: Document that default configs are not supported for TOPIC
entities
Key: KAFKA-10703
URL: https://issues.apache.org/jira/browse/KAFKA-10703
Project: Kafka
Yes, KafkaAdminClient is thread-safe.
best,
Colin
On Wed, Oct 7, 2020, at 12:38, Efe Gencer wrote:
> Hi All,
>
> Other than a Stack Overflow comment (see
> https://stackoverflow.com/a/61738065) by Colin Patrick McCabe (CC'd),
> there is no source that verifies the thread-safety of
Colin McCabe created KAFKA-10656:
Summary: NetworkClient.java: print out the feature flags received
at DEBUG level, as well as the other version information
Key: KAFKA-10656
URL: https://issues.apache.org/jira
On Wed, Oct 21, 2020, at 05:51, Tom Bentley wrote:
> Hi Colin,
>
> On Mon, Oct 19, 2020, at 08:59, Ron Dagostino wrote:
> > > Hi Colin. Thanks for the hard work on this KIP.
> > >
> > > I have some questions about what happens to a broker when it becomes
> > > fenced (e.g. because it can't send
current plan, might it be better to
> > include a Boolean value within FencedBrokerRecord and specify true
> > when the broker becomes fenced and false when it is no longer fenced?
> >
> > Also, is a fenced broker considered Offline for partition metadata
> > purposes? I
ded a rejected alternatives section about sharing IDs between multiple
nodes.
Colin
> Thanks,
>
> Jun
>
> On Mon, Oct 12, 2020 at 11:14 AM Colin McCabe wrote:
>
> > On Tue, Oct 6, 2020, at 16:09, Jun Rao wrote:
> > > Hi, Colin,
> > >
> >
following
> > are some potential reasons. (a) We can guard duplicated brokerID, but it's
> > hard to guard against duplicated controllerId. (b) brokerID can be auto
> > assigned in the future, but controllerId is hard to be generated
> > automatically.
> >
> >
501 - 600 of 1581 matches
Mail list logo
