Hi There,
What is the process to recover from a scenario where Kafka service is
down due to one of the logs dir disk is full? We can delete the topic
partitions on the directory since many of the topics are not required. Any
input is much appreciated.
Thanks,
Biju
Hi There,
We see spikes in the metadata request calls when a broker machine
specified in the broker list goes down i.e server not reachable. Is there a
property which can be set in the Java client to control the timeout when a
broker is not reachable and try another one in the list. We are seei
KAFKA-1092 (https://issues.apache.org/jira/browse/KAFKA-1092) provided the
answer to the query. Thanks all.
On Tue, Oct 7, 2014 at 8:26 AM, Biju N wrote:
> Hello There,
>I have the following in my server.properties on a two node kafka test
> cluster
>
> ….
> port=6667
>
Hello There,
I have the following in my server.properties on a two node kafka test
cluster
….
port=6667
host.name=f-bcpc-vm3.bcpc.example.com
advertised.host.name=f-bcpc-vm3.bcpc.example.com
advertised.port=9092
…
When I bring up Kafka, there is no process listening on port 9092 but Kafka
list