for this
> purpose.
>
> Ryanne
>
> On Wed, Aug 28, 2019, 6:09 PM Will Weber wrote:
>
> > Apologies for piggybacking on a thread, figured the discussion was pretty
> > relevant to a thought I had kicking around my brain.
> >
> > In the event of complete fai
Apologies for piggybacking on a thread, figured the discussion was pretty
relevant to a thought I had kicking around my brain.
In the event of complete failure or sustained loss of connectivity of the
first cluster, could the secondary cluster act as a failover for a given
configuration?
Assuming
Hey all!
I was wondering how you all might recommend expanding your log.dirs
settings safely.
Specifically, when you add new entries to your log.dirs setting on your
brokers, and execute a rolling restart to have the brokers take the new
configuration, how do you spread out your partitions into t
Hey all,
Working on a tool for Kafka lifecycle management and one of the features
we're keen to try to wrap is user quotas.
This capability definitely exists through sets of scripts included with
Kafka, case and point: https://kafka.apache.org/documentation/#quotas
For context:
> bin/kafka-conf
"Thirding" the use of prometheus, recommend reading this blog post as well:
https://www.robustperception.io/monitoring-kafka-with-prometheus
On Wed, Apr 25, 2018 at 11:39 PM, Jonathan Bethune <
jonathan.beth...@instaclustr.com> wrote:
> I also recommend Prometheus. Works great with JMX for Kafka
