Hi Matthias,
We faced the issue again. The logs are below.
16:13:16.527 [StreamThread-7] INFO o.a.k.c.c.i.AbstractCoordinator -
Marking the coordinator broker-05:6667 (id: 2147483642 rack: null) dead for
group grp_id
16:13:16.543 [StreamThread-3] INFO o.a.k.c.c.i.AbstractCoordinator -
Discovered
I am using Kafka for Event Sourcing and I am interested in implementing Sagas
(or in general long-running distributed flows) using Kafka.
I did some research but I could not find anything on the topic.
There is plenty of information on Sagas but I feel an implementation using
Kafka might i
If you confirm it's the reason, then try to increase `num.replica.fetchers` to
speed up the replication.
发件人: 蔡高年 <838199...@qq.com>
发送时间: 2017年5月11日 11:45
收件人: users
主题: 0.10.1.0 version kafka replica syn slow
hello
recently ,our prod environment have a proplem,
Hi All,
We're using kafka 0.10.0.0 and just encountered a weird issue I'd be happy
to get some help with.
Seems like we can't query active consumer groups using the
kafka-consumer-groups.sh script. Even more, listing all the active consumer
groups usually results in empty response (or a very part
Request to Join Kafka user group
Hi,
I'm trying to understand the behavior of consumer poll function when
subscribed to multiple topics using a RegEx topic pattern. I was under the
assumption the poll function would pull messages from each of the topics I
was subscribed to, but from a test program I wrote it looks like it will
pu
Hello William,
You have overriden KafkaConsumer's max.poll.records configuration, to
return only up to 10 records in single call to poll, so it does that.
Fetcher iterates over completed fetch responses and in first one(s) from
single topic finds enough of records to satisfy max limit.
See
https:/
Hi
I am trying to dabble with secure Kafka, and I have a small setup which I
created by reading this:
http://docs.confluent.io/current/kafka/ssl.html
My question is - If I have a CA cert, that I add in Kafka broker's
truststore and keystore, and also client's (Producer and Consumer)
truststore
When creating a new topic, why do I need to specify the replication factor
and number of partitions?
I'd rather than when omitted, Kafka defaults to the value set in
server.properties.
Was this an explicit design decision?
To further clarify:
I'm trying to create topics programmatically.
We want to run our code against dev/staging/production clusters. In dev,
they are often single-broker clusters. In production, we default to
replication factor of 3.
So that's why it'd make life easier if it defaulted to the value
If you enable auto topic creation that that is exactly what will happen.
There are pros and cons to creating topics with defaults values but if you fell
strongly that is the way that you want Kafka to work it is entire possible to
setup the system to work that way.
-hans
> On May 11, 2017,
Jeff,
I'm not sure if this is an option for you. However, I have been faced with
a similar problem before and we handled it by putting all of the
information needed to connect and use the Kafka API's in a config file. In
our case we were using Typesafe config [1] for lots of configuration in our
se
12 matches
Mail list logo