cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7433) Improve information for Unknown table/cf error message
Date Mon, 30 Jun 2014 10:34:24 GMT

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

Brandon Williams commented on CASSANDRA-7433:
---------------------------------------------

bq, System should just notify the user that cf/table does not exist for whatever reason. 

That's exactly what the error does, doesn't it?  We could add  a warning about it being possibly
'normal', but in the end it's still an error and we have to throw to signal to nodetool that
it should exit non-zero, so no one gets the impression it worked when in fact, it did not.

bq. On the OS level, if I try to delete or edit a non-existent file I do not expect the kernel
to panic and log an error in the syslog

Not in the syslog, but it does error right in your face, to stderr.

> 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)

Mime
View raw message