Try throwing
JMX_PORT=9998
In front of the command. Anything other than 9994
Foo
On Friday, September 11, 2015, allen chan
wrote:
> Hi all,
>
> First time testing kafka with brand new cluster.
>
> Running into an issue that i do not understand.
>
> Server started up fine but I get error when
Hi all,
I think I know the answer but just wanted to verify with others..
If I have producers writing into topic X in one cluster A, I can run Mirror
Maker to write into the same topic X from another cluster B. They are all
producers after all, right? Any complications?
Thanks,
Foo
t the files that had been previously
> configured to be retained for 168 hours? Thanks again!
>
> On Thu, Jul 16, 2015 at 4:35 PM, Foo Lim wrote:
>
> > You can set the retention.ms to something really small, i.e. 60
> seconds, &
> > kafka will delete everything older th
You can set the retention.ms to something really small, i.e. 60 seconds, &
kafka will delete everything older than 60 seconds (eventually).
bin/kafka-topics.sh --zookeeper zookeeper.yoursite.com --alter --topic
your-topic --config retention.ms=6
Remember to set it back to something sane after
nally, your best bet might be to bring up a new broker with the same
> broker ID as your failed broker. It'll join the cluster and carry on,
> though I'm not sure what effect having a now-empty partition is going to
> have.
>
> On Thu, May 28, 2015 at 12:38 PM, Foo Lim >
Hi,
I'm using kafka 0.8.2 & one of my kafka servers died (no way to recover the
data on the disks). There is a topic, with replication of 1, with one of
the partitions on the dead server. I thought a reassignment would move the
metadata for that partition to a new server without needing the data,
