I have tried changing the port to no avail. You can also see in the first
email running a: `netstat -tulpn` produces output saying that nothing is
using port . Also seeing as how 90% of the time it works it really
doesn't seem like other software would sometimes be booted, and sometimes
not.
O
Have you tried changing the configured JMX port? After all, it's possible
the conflict is between kafka and some other software running on the same
server.
On 28 June 2017 at 21:06, Eric Coan wrote:
> Hello,
>
>
> Unfortunately Kafka does indeed startup and run for a little bit before
> crashing
Hello,
Unfortunately Kafka does indeed startup and run for a little bit before
crashing with the above exception, so doing one simple check wouldn't work.
I could theoretically keep this script running forever, and constantly
checking for it being up. However that's really a hacky solution, and I
Can you not put a service wrapper for startup? It will attempt a restart if
the executable isn't up and running successfully.
I am not familiar with Unix side, but in Windows you can use a powershell
to utilise such thing. It's a better approach.
Let me know what you think.
On 28 Jun 2017 8:34 p
I am using the same configuration for all brokers. However, each broker is
running on a completely separate host (I'm not running all three brokers on
the same host). I can get all three running if I manually start kafka
again, however it's just occasionally on boot one fails to start with this
err
Aren't u using the same JMX port for all brokers? I dont think it will
work for more than 1 broker.
On 28 Jun 2017 8:22 pm, "Eric Coan" wrote:
> Hey,
>
> No worries. I'm starting the brokers with a script yes (that ends up
> generating the command I pasted:
>
> ```
>
> KAFKA_JMX_OPTS="-Dc
Hey,
No worries. I'm starting the brokers with a script yes (that ends up
generating the command I pasted:
```
KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=$FQDN
-Djava.n
Please forgive my autocorrect options :(
On 28 Jun 2017 8:06 pm, "M. Manna" wrote:
Hi,
OS is not an issue, I have a 3 broker setup and I have experienced this too.
How are toy atarting the brokers? Is this a concurrent start or have you
got some startup scriptto bring up all the brokers?
KR,
Hi,
OS is not an issue, I have a 3 broker setup and I have experienced this too.
How are toy atarting the brokers? Is this a concurrent start or have you
got some startup scriptto bring up all the brokers?
KR,
On 28 Jun 2017 6:47 pm, "Eric Coan" wrote:
> Hello,
>
> I've recently been doing re
Hello,
I've recently been doing research into getting our Kafka cluster running
outside of Mesos (for a couple of reasons). However I'm noticing about 10%
of the time Kafka fails to start on boot (or more accurately starts, and
immediately exits). I find it weird since all brokers are using the ex
10 matches
Mail list logo
