IO speed -> check -> throttle (sleep
> to reach desired rate) -> run 300ms with full speed -> done
>
> So, when printing the log, you will see the rate is higher than you
> expected.
> At least I ran in kafka v3.3.1 and it works well.
>
> Thank you.
> Luke
>
&g
r/fr?xtatc=INT-149>
*Nicolas Carlot*
*Lead dev*Direction des Systèmes d'Information
3 boulevard Romain Rolland
75014 Paris
[image: img] <https://mailsign.chronopost.fr/linkc/K0ppSHlnPT0-L3A4PQ> [image:
img] <https://mailsign.chronopost.fr/linkc/K0ppSHlnPT0-L1pzPQ> [image: img]
"client" side.
> I think the broker side log will have more info.
> Also, which Kafka version are you using?
>
> Thank you.
> Luke
>
> On Tue, May 10, 2022 at 8:17 PM Nicolas Carlot
> wrote:
>
> > Not a single line regarding this topic, but at creatio
), 9 -> ArrayBuffer(3, 2, 1))
(kafka.zk.AdminZkClient)
Le mar. 10 mai 2022 à 05:15, Luke Chen a écrit :
> Hi Nicolas,
>
> Could you check the logs in broker side?
> There must be some errors while electing leaders or something.
>
> Thank you.
> Luke
>
> On Mon, May
happening ?
--
[image: img] <https://www.chronopost.fr/fr?xtatc=INT-149>
*Nicolas Carlot*
*Lead dev*Direction des Systèmes d'Information
3 boulevard Romain Rolland
75014 Paris
[image: img] <https://mailsign.chronopost.fr/linkc/K0ppSHlnPT0-L3A4PQ> [image:
img] <https://ma
pening, and why it's only for this perculiar topic ?
--
[image: img] <https://www.chronopost.fr/fr?xtatc=INT-149>
*Nicolas Carlot*
*Lead dev*Direction des Systèmes d'Information
3 boulevard Romain Rolland
75014 Paris
[image: img] <https://mailsign.chronopost.fr/linkc/K0ppS
ays
> restore the state if all does not go well.
>
> This could be due to Zookeeper version incompatibility or bad state of data
> in Zookeeper before the upgrade.
>
> Israel Ekpo
> Lead Instructor, IzzyAcademy.com
> https://www.youtube.com/c/izzyacademy
> https://izzyacademy
kafka log or server.log ?
> ____
> From: Nicolas Carlot
> Sent: Tuesday, January 25, 2022 6:20 AM
> To: users@kafka.apache.org
> Subject: Upgrade from 2.0 to 2.8.1 failed
>
> [External]
>
>
> Hello everyone,
>
> I just had a major fa
er: 3 Replicas:
2,3,1 Isr: 3
Topic: PARCEL360.LT Partition: 8Leader: 3 Replicas:
3,1,2 Isr: 3
Topic: PARCEL360.LT Partition: 9Leader: 3 Replicas:
1,2,3 Isr: 3
Any idea what's happening here ?
--
<https://www.chronopost.fr/fr?xtatc=INT-149>
gt;
> Can you share your feedback, please?
>
> Also is there some better way to implement this? Like for example
> using Streaming API?
>
>
> BR,
> Peter
>
--
*Nicolas Carlot*
| | nicolas.car...@chronopost.fr
[image: Logo Chronopost]
| chronopost.fr <http://www.chr
resulting in 1
to 3 of the ZK nodes to be used.
Now, I have a ZK node that loses connection with the ZK ensemble, but is
still alive.
If some brokers were using that node, they also end up being isolated from
the other brokers ?
--
*Nicolas Carlot*
Lead dev
| | nicolas.car...@chronopost.f
. Commit interval is 1 second and
> we have caching enabled and the max cache size is 512MB. We have 5
> instances (6 CPU, 30 GB RAM).
>
> Thank you!
>
>
>
--
*Nicolas Carlot*
Lead dev
| | nicolas.car...@chronopost.fr
*Veuillez noter qu'à partir du 20 mai, le siège
m the input topic).
> >
> >
> >
> > Thanks
> >
> >
> >
> > *Pirow Engelbrecht*
> > System Engineer
> >
> > *E.* pirow.engelbre...@etion.co.za
> > *T.* +27 12 678 9740 (ext. 9879)
> > *M.* +27 63 148 3376
> >
> > 76 R
57] INFO Notification: 1 (message format version), 3
(n.leader), 0x820e000c (n.zxid), 0x2 (n.round), LOOKING (n.state), 1
(n.sid), 0x820e (n.peerEpoch) LEADING (my state)
(org.apache.zookeeper.server.quorum.Fast
LeaderElection)
--
*Nicolas Carlot*
Lead dev
| | nicolas.car...@chronopost.fr
*Ve
d value as
> java's ArrayList in the kafka topic. Kafka has by default provided a
> StringSerializer and StringDeserializer, however for java ArrayList, how
> can get serializer. Do I need to write my own? Can someone share if someone
> already has written one?
>
--
*Nic
tamp
> >> > > > > > mismatch error that didn't lose messages immediately after the
> >> > > > > deployment.
> >> > > > > > After the deployment being done and after the cluster being
> >> already
> >> > > > > running
> >> > > > > > both changed to permission denied and* all the messages insid
ot using kafka connect due to restrictions from database team.
>
> Is there any other good approach to develop in kstreams. Utilize JDBC or
> something else with kstreams?
>
> Thanks,
> Asmath
>
--
*Nicolas Carlot*
Lead dev
| | nicolas.car...@chronopost.fr
*Veuillez noter q
he
> > ones that are properly deleted have a valid timestamp in there. From what
> > we read from documentation and code it looks like the largestTime is used
> > to calculate if a given segment reached the time breach or not.
> >
> > Since we can observe this in multiple
>
> Since we can observe this in multiple versions of Kafka, we think this
> might be related to anything external to Kafka. E.g Zookeeper.
>
> Does anyone have any ideas of why this could be happening?
> For the record, we are using Zookeeper 3.6.0.
>
--
*Nicolas Carlot*
Le
resolve.
>
> Thanks and regards,
> Naveen
>
> On Fri, Apr 17, 2020 at 5:32 PM Nicolas Carlot <
> nicolas.car...@chronopost.fr>
> wrote:
>
> > Logs say to build it.
> > Have you done that ?
> >
> > ./gradlew jarAll
> >
> > Le ven.
Please build the project first e.g. by running 'gradlew
> jarAll'
>
> Could you please help me to resolve this issue and run Kafka server on
> windows?
>
> This will be great help:)
>
> Thanks and regards,
> Naveen
>
--
*Nicolas Carlot*
Lead dev
| | nico
I've opened a Jira issue on the subject
https://issues.apache.org/jira/browse/KAFKA-9880
Le jeu. 16 avr. 2020 à 13:14, Bruno Cadonna a écrit :
> Hi Nicolas,
>
> Yeah, I meant "doesn't". Sorry for that!
>
> Best,
> Bruno
>
> On Thu, Apr 16, 2020 at
ould you be interested in contributing?
>
> If you cannot assign the ticket to yourself, ask to be added to the list of
> contributors on the dev mailing list.
>
> Best,
> Bruno
>
> On Thu, Apr 16, 2020 at 11:06 AM Nicolas Carlot <
> nicolas.car...@chronopost.fr> wrote
# Bump #
So is this a bug ? Should I file a ticket ?
Any idea ? I don't like the idea of having to patch Kafka libraries...
Le mer. 1 avr. 2020 à 16:33, Nicolas Carlot
a écrit :
> Added some nasty code in kafka 2.4.1. Seems to work fine for now... From
> my understanding, the compact
ka.common.record.Record.recordSize([B[B)I
>
>
> Thanks and regards,
> Gowtham S, MCA
>
>
>
> On Wed, 15 Apr 2020 at 19:32, Nicolas Carlot
> wrote:
>
>> What do you mean by communication between Kafka Clients ?
>> A Client is either a producer or a consumer, th
it
> necessary to move the topics to a single Kafka?
> If necessary to upgrade the clients, suggest the best practices for the
> same.
>
>
> With regards,
> Gowtham S, MCA
>
--
*Nicolas Carlot*
Lead dev
| | nicolas.car...@chronopost.fr
*Veuillez noter qu'à p
mmed, <
> mdkhajaasm...@gmail.com>
> >> wrote:
> >>
> >> Hi,
> >>
> >> We have lost some data while processing and would like to reprocess it.
> >> May I know the procedure to do it . I have offsets numbers that I need
> to
> &g
roperties while sending
> messages to consumer and consumer can read the same. I am looking for
> similar functionality in Kafka.
>
> Thanks and regards,
> Naveen
>
> On Fri, Apr 10, 2020, 7:22 PM Nicolas Carlot >
> wrote:
>
> > Hello,
> >
> > Messa
essage
> > expiration while sending message to Kafka topic and how to read customer
> > properties in consumer end?
> >
> > Thanks and regards,
> > Naveen
> >
>
--
*Nicolas Carlot*
Lead dev
| | nicolas.car...@chronopost.fr
*Veuillez noter qu'à par
Added some nasty code in kafka 2.4.1. Seems to work fine for now... From my
understanding, the compaction process when restoring a store is only done
to speed up things.
So I guess this kind of "hack" isn't such a big deal ?
[image: image.png]
Le mer. 1 avr. 2020 à 10:44, Nicolas
Here is the full configuration of Rocks.
[image: image.png]
Le mer. 1 avr. 2020 à 10:41, Nicolas Carlot
a écrit :
> It's not that I cannot turn on compaction.
> Compaction works fine.
> The issue is with the restoration process of the state store, which tries
> to compact the
using FIFO compaction.
Le mer. 1 avr. 2020 à 10:26, Nicolas Carlot
a écrit :
> My current workaround is to completely delete the state store and rebuild
> it from scratch.
>
> Le mar. 31 mars 2020 à 21:39, Boyang Chen a
> écrit :
>
>> Thanks Nicolas for the report, so ar
>
> On Tue, Mar 31, 2020 at 9:54 AM Nicolas Carlot <
> nicolas.car...@chronopost.fr>
> wrote:
>
> > After some more testing and debugging, it seems that it is caused by the
> > compaction option I've configured for RocksDB. When removed ever
xSize);
fifoOptions.setAllowCompaction(true);
options.setCompactionOptionsFIFO(fifoOptions);
options.setCompactionStyle(CompactionStyle.FIFO);
Le mar. 31 mars 2020 à 16:27, Nicolas Carlot
a écrit :
> Hello everyone,
>
> I'm currently facing an issue with RocksDb internal compaction process,
Hello everyone,
I'm currently facing an issue with RocksDb internal compaction process,
which occurs when the local state store of several of my KafkaStream
applications are being restored. This is sadly a huge concern as it
completely discard resiliency over node failure as those often lead to a
35 matches
Mail list logo
