Re: Issues with JMX monitoring -- v0.8.7

2011-11-23 Thread Edward Capriolo
Wiki documentation will probably never be able to keep pace with the actual JMX objects. The tend to get renamed, move, properties get added removed, etc. It happens with active projects. Edward On Wed, Nov 23, 2011 at 12:22 PM, David McNelis wrote: > In that case, I think that the documentation

Issues with JMX monitoring -- v0.8.7

2011-11-23 Thread David McNelis
In that case, I think that the documentation is incorrect, as it has Service listed as the package related to the StorageService. I apologize for the lack of the rest of the thread, everything is getting bounced when I try to send it for some reason. -- *David McNelis* Lead Software Engineer Age

Re: Issues with JMX monitoring -- v0.8.7

2011-11-23 Thread Nick Bailey
Oh I was thinking of StorageProxy. StorageService should exist you just have the path wrong. It should be "org.apache.cassandra.db:type=StorageService".(you had org.apache.cassandra.service) JMX should be lightweight enough for this. On Wed, Nov 23, 2011 at 9:06 AM, David McNelis wrote: > But if

Re: Issues with JMX monitoring -- v0.8.7

2011-11-23 Thread David McNelis
But if the StorageService bean is only created once a transaction has occurred, is there another location, i.e. the CommitLog, that I could check just to see if the node is 'live'. Or do you think I'd be better served trying to execute something on the node (i.e. read a record using Hector)? Idea

Re: Issues with JMX monitoring -- v0.8.7

2011-11-22 Thread Nick Bailey
There are quite a few attributes in the org.apace.cassandra.db.StorageServiceMBean that could serve that purpose. Initialized, RPCServerRunning, OperationMode, Joined, and perhaps others Note that some of those may not exist depending on your version of cassandra, pick one appropriate for your ve

Re: Issues with JMX monitoring -- v0.8.7

2011-11-22 Thread David McNelis
Would there be a better bean to look at to ascertain the status that would be created when the server starts up? On Tue, Nov 22, 2011 at 11:47 AM, Nick Bailey wrote: > The StorageServiceMBean is only created once some reads/writes > actually go to that node. Do a couple reads/writes from the CLI

Re: Issues with JMX monitoring -- v0.8.7

2011-11-22 Thread Nick Bailey
The StorageServiceMBean is only created once some reads/writes actually go to that node. Do a couple reads/writes from the CLI and you should see the MBean afterwards. This also means your monitoring application should handle this error in the case of nodes restarting. On Tue, Nov 22, 2011 at 7:5

Issues with JMX monitoring -- v0.8.7

2011-11-22 Thread David McNelis
Good morning, I'm trying to set up a simple monitoring application (that is a plugin to Nagios), code can be found here: https://github.com/so-net-developer/Cassandra/blob/master/nagios/CheckNode.java However, when I try to run the CheckNode.java program I get an error that: Exception in thread "