It seems there are many different symptoms you see...
Maybe we can start from leader flapping issue. Any findings in controller
log?
Jiangjie (Becket) Qin
On 4/16/15, 12:09 PM, "Kyle Banker" wrote:
>Hi,
>
>I've run into a pretty serious production issue with Kafka 0.8.2, and I'm
>wondering w
Hi,
I've run into a pretty serious production issue with Kafka 0.8.2, and I'm
wondering what my options are.
ReplicaFetcherThread Error
I have a broker on a 9-node cluster that went down for a couple of hours.
When it came back up, it started spewing constant errors of the following
form:
INFO
Hi,
@Manoj/@Pete: Thanks for the inputs. I am already aware of the parallelism
provided by kafka. My use case needed single topic per user, but I came up
with a workaround for that and so the problem is solved.
@Guozhang: I agree, kafka stores data related to partitions and topics(
https://cwiki.
Hi,
Earliest and Latest are like Enums that denote the first and last messages
in the partition. (Or the offsets for those positions)
My understanding is the you can only based on offsets . Not on timestamps.
regards
On Thu, Apr 16, 2015 at 7:35 AM, Alexey Borschenko <
aborsche...@elance-odesk.
Siva,
For Kafka brokers as long as the total #.partitions is not too much I think
it should be fine (we have been hosting 600+ partitions on a single node).
You have to pay some attention on your ZK nodes though since with #.topics
increasing its metadata storage will take more and more space.
Gu
We have a 6 broker cluster running in AWS in 3 availability zones. A few
times while under slight load (40k messages/second, roughly) we have seen a
replica try to request a message from the leader by an index that is
slightly in the future, 3-6 messages usually. When this happens the
replica thr
Hi All,
I came across a problem, If we use broker IP which is not reachable or out
of network. Then it takes more than configured time(request.timeout.ms).
After checking the log got to know that it is trying to fetch topic
meta-data three times by changing correlation id.
Due to this even though
Hi all!
I need to read offsets closing to specified timestamp.
As I can see this can be achieved by using SImpleConsumer API.
To test things I use SimpleConsumer example provided on site:
https://cwiki.apache.org/confluence/display/KAFKA/0.8.0+SimpleConsumer+Example
I use Kafka 8.2.1
When I pass
