t timeouts to stabilize the consumer group.
Fortunately, our target cluster for most of our mirrormakers is the last one we
will upgrade to 1.x, at which point we can just upgrade the mirrormakers to 1.x
as well.
On 4/6/18, 1:09 PM, "Jeff Field" wrote:
I'm hitting the same p
I'm hitting the same problem, even with the new consumer, on MirrorMaker 0.9
reading from a 0.9 Kafka cluster and producing to a 0.11 Kafka cluster.
On 3/30/18, 3:56 PM, "Andrew Otto" wrote:
I’m currently stuck on MirrorMaker version 0.9, and I’m not sure when the
new consumer client b
pen+0x20/0x30
[] system_call_fastpath+0x16/0x1b
So it wasn't the array, or Kafka but rather an interaction between SELinux and
XFS (at least, that is my initial thought). SELinux is now off, we'll likely
file a bug against RHEL/CentOS after more investigating.
Thanks!
-Jeff
-Original Message-
ame options you're running kafka with
it should succeed but if it fails with the same error that is the address
space limit for 32 bits kicking in.
-Jay
From: Jeff Field
Sent: Wednesday, May 13, 2015 4:25 PM
To: users@kafka.apache.org
Subject: OutOfMemory error on broker when rolling logs
Hell
Hello,
We are doing a Kafka POC on our CDH cluster. We are running 3 brokers with 24TB
(48TB Raw) of available RAID10 storage (XFS filesystem mounted with
nobarrier/largeio) (HP Smart Array P420i for the controller, latest firmware)
and 48GB of RAM. The broker is running with "-Xmx4G -Xms4G -ser
If you don't mind venturing further south, http://www.meetup.com/OCBigData/
could be a good meetup to discuss Kafka at as well.
-Original Message-
From: Alex Toth [mailto:a...@purificator.net]
Sent: Friday, April 24, 2015 9:55 AM
To: Jon Bringhurst; users@kafka.apache.org
Subject: Re: ka
