Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Framework API Does Not Retreive Active Frameworks #52

Open
TomDaviesUK opened this issue Jun 22, 2016 · 3 comments
Open

Framework API Does Not Retreive Active Frameworks #52

TomDaviesUK opened this issue Jun 22, 2016 · 3 comments

Comments

@TomDaviesUK
Copy link

TomDaviesUK commented Jun 22, 2016

When cleaning up a Cassandra un-install, the framework ID in Mesos is required.

But, using the Mantl-API, an empty JSON is returned, though I can see four active frameworks in the Mesos UI.

curl -sku username:password https://<my-mantl-control-01/api/1/frameworks

Further, when copying the Active Framework ID manually out of the Mesos UI and attempting to delete the framework using that ID via the API, this fails as the framework corresponding to the ID is reported as 'not found'.

curl -X DELETE -sku username:password https://<my-mantl-control-01/api/1/frameworks/{My_Framework_ID}
Cloud not shutdown framework {ID}: 400 No framework found with specified ID

Is this a real issue, or user error in some way?

I'm running Mantl 1.1.0 on Openstack.

@ryane
Copy link
Contributor

ryane commented Jun 22, 2016

can you check the stderr logs in mantl-api while you run curl -sku username:password https://<my-mantl-control-01/api/1/frameworks? assuming you are in debug mode (the default until mantl/mantl#1531), you should see a line that looks like this: GET http://mantl-control-01:15050/master/state.json. can you check to see if the host in that line matches the leader that you see in the mesos UI (labeled Server on the left sidebar of the mesos ui home page)?
you may have to translate between hostname and ip (mantl-api will report the hostname but mesos ui will report the ip addr).

@TomDaviesUK
Copy link
Author

TomDaviesUK commented Jun 22, 2016

Update / Additional information: Discussed in Gitter with @ryane.

The Mantl-API was not pointing to the lead Mesos server. A re-start of the Mantl-API application resolved the immediate problem.

This might be resolved in Mantl-API 0.2.2. Will leave open for confirmation.

@ryane
Copy link
Contributor

ryane commented Jun 22, 2016

mantl-api can end up caching the mesos leader and not refreshing after mesos leadership changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants