You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2014/06/27 19:06:27 UTC
[jira] [Commented] (CASSANDRA-7433) Improve information for Unknown
table/cf error message
[ https://issues.apache.org/jira/browse/CASSANDRA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046151#comment-14046151 ]
Brandon Williams commented on CASSANDRA-7433:
---------------------------------------------
What kind of info were you looking to have added? It seems pretty clear to me: repair failed because it tried to repair an unknown table/cf.
> Improve information for Unknown table/cf error message
> ------------------------------------------------------
>
> Key: CASSANDRA-7433
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7433
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Adam Hattrell
> Priority: Minor
>
> Could we add some further details to the following types of error:
> {code:none}
> ERROR [Thread-11235] 2014-06-20 11:08:20,278 StorageService.java (line 2436) Repair session failed:
> java.lang.IllegalArgumentException: Unknown table/cf pair (counterpartyrisk.deals20140602HPCE_OFFICIAL)
> at org.apache.cassandra.db.Table.getColumnFamilyStore(Table.java:165)
> at org.apache.cassandra.service.StorageService.getValidColumnFamilies(StorageService.java:2293)
> at org.apache.cassandra.service.StorageService.forceTableRepair(StorageService.java:2485)
> at org.apache.cassandra.service.StorageService$5.runMayThrow(StorageService.java:2432)
> at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.lang.Thread.run(Thread.java:744)
> {code}
> Specifically that this is expected if you have recently dropped the associated column family. I don't think this should be dropped to a WARN as if you haven't changed your schema recently then this probably indicates a significant problem. In the majority of cases though - it can probably be safely ignored.
--
This message was sent by Atlassian JIRA
(v6.2#6252)