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
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
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
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
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
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
