Comments (7)
@kikicarbonell Can you also attache cassandra-mesos.log from the sandbox that contains the actual logs from the scheduler process.
from cassandra-mesos-deprecated.
@BenWhitehead please, can you read all logs from: http://stackoverflow.com/questions/32830901/cassandra-mesos-health-check-fail-when-deploy-with-marathon
from cassandra-mesos-deprecated.
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.
from cassandra-mesos-deprecated.
@BenWhitehead well I was opening port: 7000,7001,9042,9160,7199,22 but not work? if possible that made some problem around mesos framework?
from cassandra-mesos-deprecated.
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.
- Cassandra-Mesos framework scheduler need to communicate with zk
2181
to persist it's state, locate the leading mesos-master. Needs to be able to communicate with the mesos master at port5050
. - The mesos-master then needs to be able to communicate back with the scheduler on a random port selected by libmesos at runtime (it's in the random port range the kernel reserves).
- marathon will need to be able to communicate with the scheduler on
$PORT0
in order to issue health checks against the http api. - The Custom Executor needs to be able to connect to
5051
to communicate with the mesos-agent - The mesos-agent will need to be able to communicate back with the executor on a random port selected by libmesos at runtime (it's in the random port range the kernel reserves).
- Each Server task will bind against
7000,7001,7199,9042,9160
. Port7000
is used by cassandra for it's internode gossip communication. - Each Custom Executor will need to be able to communicate with
localhost:7199
in order to connect to the JMX MBeans for nodetool commands (health checks, cluster jobs, shutdown, etc.) - Each Custom Executor will need to be able to communicate with the random scheduler port bound in note 2 above. (this is for Framework Messages sent from the custom executor to the scheduler with information about health check and a couple other things that don't necessitate a task.)
- Then each client will need to be able to access
9042/9160
of each node running a server so that it can interact with cassandra itself.
Hopefully this can help you track down the packet breakdown. I'd be interested in knowing what ends up working for you.
from cassandra-mesos-deprecated.
@BenWhitehead thks for your detailed explanation about process and port used on
cassandra-mesos fremework, after this I suppouse that the problem will be
the random port used by mesos (step 5 in your description), then I create a
rule on iptable to allow tcp traffic betwen al mesos nodes, it' s a
temporal solution but it work.
The iptable command to do it:
iptable -A INPUT -p tcp -s <hostname> -j ACCEPT;
from cassandra-mesos-deprecated.
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.
from cassandra-mesos-deprecated.
Related Issues (20)
- Can't stand up Cassandra Ring with firewalld enabled on node that runs Cassandra Cluster HOT 4
- Node instance is failing to come up after the reboot and scheduler restart HOT 10
- Support for Cassandra 2.2.x HOT 5
- Launch on Mesos/Marathon created with docker compose HOT 2
- No seed nodes launched HOT 1
- Cassandra-Mesos and SSL? HOT 1
- Tutorial of using vagrant and/or virtualbox to setup dev cluster HOT 1
- Scheduler fails trying to increase the number of nodes HOT 1
- Adjust resources(memory, cpu etc) allocated to each cassandra node after cassandra-mesos gets deployed. HOT 1
- Trouble with starting Cassandra cluster HOT 1
- Allow cassandra scheduler to inject a java agent into cassandra jvm. HOT 2
- Issues replacing dead node HOT 2
- Unresolveable build extension: maven-protoc-plugin:0.4.0 HOT 2
- Adding Nodes to a cluster HOT 2
- Use persistent volumes for data storage HOT 1
- Suggested URI for a 2.1.5 or newer version of cassandra? HOT 2
- Logs not clearing
- Support for production Workload DC OS and DataStax Cassandra latest Versions HOT 1
- cassandra-mesos installed question HOT 1
- Co locating spark and cassandra on mesos.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cassandra-mesos-deprecated.