cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1843) Indexes: CF MBeans for automatic indexes are never unregistered when they are deleted.
Date Mon, 13 Dec 2010 20:17:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971017#action_12971017
] 

Hudson commented on CASSANDRA-1843:
-----------------------------------

Integrated in Cassandra #625 (See [https://hudson.apache.org/hudson/job/Cassandra/625/])
    

> Indexes: CF MBeans for automatic indexes are never unregistered when they are deleted.
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1843
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1843
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0 rc 1
>            Reporter: Jon Hermes
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: 1843.txt
>
>
> Add, delete, and add the same index and you should get a stacktrace to this effect:
> {noformat}
> java.lang.RuntimeException: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=Keyspace1,columnfamily=Standard1.616765
>   at org.apache.cassandra.db.ColumnFamilyStore.<init>(ColumnFamilyStore.java:259)
>   at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:447)
>   at org.apache.cassandra.db.ColumnFamilyStore.addIndex(ColumnFamilyStore.java:304)
>   at org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:193)
>   at org.apache.cassandra.db.migration.UpdateColumnFamily.applyModels(UpdateColumnFamily.java:80)
>   at org.apache.cassandra.db.migration.Migration.apply(Migration.java:171)
>   at org.apache.cassandra.thrift.CassandraServer$2.call(CassandraServer.java:663)
>   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>   at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=Keyspace1,columnfamily=Standard1.616765
>   at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
>   at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
>   at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
>   at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
>   at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
>   at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
>   at org.apache.cassandra.db.ColumnFamilyStore.<init>(ColumnFamilyStore.java:255)
>   ... 11 more{noformat}
> CFS.reload() manages index deletion, but never unregisters the MBeans it creates during
initialization.

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


Mime
View raw message