You can do this without exposing the JMX port, e.g. by using a Prometheus
exporter as javaagent (https://github.com/prometheus/jmx_exporter).
Metricsreporters, such as the one from Confluent, also don't require you to
open ports, because metrics will be pushed out of the broker (
Hi XinYi,
All consumer instances using the same group.id will share the data
(partitions) of a certain topic. The consumer group.id is not bound to a
topic.
If you want to share data on 1 topic, and parallel process data on another,
you have to change the group.id.
best regards,
Joris
On
Hi Sachin,
If you check kafka-run-class.bat you can see that when environment variable
KAFKA_LOG4J_OPTS is not provided, a default log4j configuration under
"tools" will be loaded. So setting the environment variable to something
like
Hi Senthil,
You can just try it yourself, using kafka-consumer-perf-test.sh bundled
with Apache Kafka. You can start 2 in parallel with different groups and
see what happens if you tune some parameters.
Joris
On Wed, Jan 25, 2017, 08:38 Senthil Kumar wrote:
> Thanks
Why would you want to use the benefit of ACLs without mutual SSL? I think
that as soon as you decided you need ACLs, you also should add encryption.
It's relatively easy to configure.
On Thu, Jan 26, 2017, 05:35 Manikumar wrote:
> Yes, we can use Kafka ACL's with
Hi,
You might want to take a look at the setting for "request.timeout.ms" for
the consumer (see
http://kafka.apache.org/documentation.html#newconsumerconfigs). The default
timeout is about 5 minutes). For the producer this timeout is around 30
seconds, so that possibly explains why it works for