Hi,
Can you be a bit more specific about what you're looking for?
thanks, Robin.
--
Robin Moffatt | Senior Developer Advocate | ro...@confluent.io | @rmoff
On Tue, 18 Feb 2020 at 00:28, Ajith Kumar Rajendran wrote:
> Hi team,
>
> Need a kafka compatibility metrics details
>
> *Thanks and
Hi Anjith
Might the be what you referring to:
https://docs.confluent.io/current/installation/versions-interoperability.html
G
On Tue, Feb 18, 2020 at 11:54 AM Robin Moffatt wrote:
> Hi,
>
> Can you be a bit more specific about what you're looking for?
>
> thanks, Robin.
>
>
> --
>
> Robin Mo
Hi,
Say I want to fetch all the keys for
store.fetchAll(8, 12)
+---+
| key | start time | end time |
+---++--+
| A | 10 |20|
+---++--+
| A | 15 |25|
+---++-
Hello Gowtham,
You need to include the size of offset and time index files in your
calculations, plus potentially transaction indexes.
If you use default values, that means 10 MB each for every log
segment, which default size is itself 1 GB.
Alexandre
Le lun. 27 janv. 2020 à 08:51, Gowtham S a
Good afternoon,
I work for a small, federally-focused value added reseller based in McLean, VA.
Do you offer an sort of support contracts for your Apache Kafka product? I have
a customer who is a classified Government end-user and they are hoping to get a
quotation.
Let me know if you have any
Kia ora,
You'll want to contact Confluent: https://www.confluent.io/subscription
Kind regards,
Liam Clarke
On Wed, 19 Feb. 2020, 11:32 am Doug Zellers,
wrote:
> Good afternoon,
>
> I work for a small, federally-focused value added reseller based in
> McLean, VA. Do you offer an sort of suppor
Hi Ivan,
This is probably by design, since just because the broker 0 has gone down does
not mean that it won't come back up in the future. That is why the data
structures keep track of dead brokers too.
As far as ISR is concerned, broker 0 is still probably in ISR for "foo" topic's
0th partiti
Hello folks,
This is a kind reminder of the Bay Area Kafka® meetup this Thursday (Feb.
20th) 5:30pm, at Confluent's Mountain View HQ office.
*RSVP and Register* (if you intend to attend in person):
https://www.meetup.com/KafkaBayArea/events/268427599/
*Date*
5:30pm, Thursday, February 20th, 2019
hmm Math here doe snot look right
> > Retention Period = Retention period + (log.retention.check.interval.ms +
> > log.segment.delete.delay.ms ) / 1000
> > = 86400 + (3 + 6000)/1000
> > = 86400 + 360
> > = 86760 Seconds
Asking as I also need to do some of this math.
How did you get to 90MB/s, the RAM size and CPU count ?
You missing some dedicated SSD's for the ZK's
Assume you doing licensing for 6 brokers...
I'd suggest maybe rather go with 5 x 1TB drives, you provisioning 24TB for
a 23.4 TB sizing, cutting it v
Thanks, George and Alexandre for the reply.
George, to answer your question
> How did you get to 90MB/s - this is our expected throughput.
For the RAM size and CPU count?
> Can you please suggest me how to calculate this!
With regards,
Gowtham S, MCA
PH: 9597000673
On Wed, 19 Feb 2020 at
Hi there
with regard to "> Can you please suggest me how to calculate this!"
No I can't thats why I asked, getting idea only way you going to figure
this out is by building 6 servers, with say 12-16 vCPU's assigned and then
run test/volume load and see what Prometheus shows you from a CPU/memory
12 matches
Mail list logo
