cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Viner (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1448) PropertyFileEndPointSnitch can only be used once per configuration
Date Tue, 31 Aug 2010 06:00:54 GMT


David Viner commented on CASSANDRA-1448:

Happy to make that change... although that would require a list (somewhere) of the set of
mbean names in use... is that available to the callers of the mbean -> reload()?

Also, in the snitch constructor, how would I determine what keyspace is being used?  The constructor
doesn't appear to get any parameters.  Is there a global config object that I could access
or some such?

Or, since this whole point is moot for 0.7.x in the PropertyFileEndPointSnitch, is this really
a moot issue?  It might impact other areas, per the discussion on the irc channel (e.g., dynamic
eps).  But that's an issue for a separate bug.

> PropertyFileEndPointSnitch can only be used once per configuration
> ------------------------------------------------------------------
>                 Key: CASSANDRA-1448
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Contrib
>    Affects Versions: 0.6.4, 0.6.5, 0.7 beta 1
>         Environment: Debian
>            Reporter: David Viner
>            Assignee: Brandon Williams
>             Fix For: 0.6.6
>         Attachments: patch-for-mbean-error.patch
> When a user configures a node to have more than one keyspace, and two keyspaces uses
PropertyFileEndPointSnitch as the EndpointSnitch, Cassandra throws an error on startup saying:
> ERROR [main] 2010-08-30 23:55:23,402 (line 536) Fatal error:
Invalid endpointsnitch class org.apache.cassandra.locator.PropertyFileEndPointSnitch null
> This appears to be directly tied to the use of MBeanServer.registerMBean().  If more
than one instance is tied to the mbean server, it will return an InstanceAlreadyExistsException.
 Since this appears to be a valid exception, but causes no errors in operation, the snitch
should catch it and continue on.
> Patch file to follow.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message