cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1448) PropertyFileEndPointSnitch can only be used once per configuration
Date Wed, 15 Sep 2010 21:09:34 GMT


Brandon Williams commented on CASSANDRA-1448:

I'm going to table this issue.  There are only a few options I see for this: special casing
the PFEPS instantiation, or changing the endpoint interface so that there is a method we can
pass the keyspace to (which could possibly break any other custom snitches people are using
in 0.6)  There is a compromise where we could add something unique to the mbean name, but
you wouldn't be able to tell which snitch belonged to a keyspace.  None of these seem very
attractive, and this issue does not affect 0.7, so anything we do here will just add pain
to merges.

> 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