-
Notifications
You must be signed in to change notification settings - Fork 68
problem deploying cassandra-mesos with marathon #144
Comments
@kikicarbonell Can you also attache cassandra-mesos.log from the sandbox that contains the actual logs from the scheduler process. |
@BenWhitehead please, can you read all logs from: http://stackoverflow.com/questions/32830901/cassandra-mesos-health-check-fail-when-deploy-with-marathon |
Hi @kikicarbonell The ports used by cassandra can be found here in the official documentation. We don't start OpsCenter so you can disregard those ports. |
@BenWhitehead well I was opening port: 7000,7001,9042,9160,7199,22 but not work? if possible that made some problem around mesos framework? |
Possibly, I thought you were saying that the farmwork tried to start the tasks but cassandra wasn't able to ever form the ring. I'll try and outline all of the network connections I know about in play here.
Hopefully this can help you track down the packet breakdown. I'd be interested in knowing what ends up working for you. |
@BenWhitehead thks for your detailed explanation about process and port used on The iptable command to do it:
|
This repository is deprecated. Please use the latest supported framework here: https://github.com/mesosphere/dcos-cassandra-service, and provide feedback for us here: https://dcosjira.atlassian.net/browse/CASSANDRA. |
I'm trying cassandra-mesos on my private cluster os mesos. I'm using Readme instruction to deploy with marathon but some error occure on wake up task:
Stderr output:
and Stdout output:
My cluster has:
mesos masters: 1
mesos slaves: 3
marathon
docker
The text was updated successfully, but these errors were encountered: