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.

Sign up for GitHub

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

Jump to bottom

Cant retrieve Datacenter name ERROR #34

Closed
bamartos opened this issue Nov 14, 2018 · 2 comments
Closed

Cant retrieve Datacenter name ERROR #34

bamartos opened this issue Nov 14, 2018 · 2 comments

Comments

@bamartos
Copy link

Hi,

When I am trying to run the exporter (v2.0.3) I receive:
ERROR com.criteo.nosql.cassandra.exporter.JmxScraper - Cannot retrieve the datacenter name information for the node
javax.management.AttributeNotFoundException: No such attribute: Datacenter

In the config.yml file we tried to blacklist the node - org:apache:cassandra:db:.* but it didnt help.

It seems that the error is related with the code on JmxScraper.java:373. We tried to use and older (v1.0.1) which is not parsing the Datacenter name and it worked fine.

We are using Cassandra 3.0.6,

Cheers
erebe pushed a commit that referenced this issue Nov 15, 2018
#34 Use a different approach to retrieve datacenter name
033ca74 
 - Older version of cassandra do not expose the jmx attribute "datacenter"
   We are suppose to use the method getDatacenter which need to recieve as
   parameter the public ip of the node
@erebe
Copy link
Contributor

erebe commented Nov 15, 2018 •
edited
Loading

Hello,
Thanks for reporting. It should be good with the release 2.1.0
https://github.com/criteo/cassandra_exporter/releases/tag/2.1.0

Let me know if it is ok or not for you

@bamartos
Copy link
Author

Yes, it works now,

Thanks for your super fast response, you can close the issue.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@erebe @bamartos