[
https://issues.apache.org/jira/browse/CASSANDRA-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904518#action_12904518
]
Jonathan Ellis commented on CASSANDRA-1448:
-------------------------------------------
I don't think this is the right fix -- the point of the mbean is so you can
tell PFEPS to reload its config, which obviously doesn't work if you have
multiple snitch objects but only one is connected to the mbean.
(0.7 makes the snitch global, among other changes.)
> PropertyFileEndPointSnitch can only be used once per configuration
> ------------------------------------------------------------------
>
> Key: CASSANDRA-1448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1448
> 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 DatabaseDescriptor.java (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.
