cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-1409) What should happen when cassandra loses permissions to it's data directory and unable to compact?
Date Tue, 15 May 2012 17:36:09 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-1409.
---------------------------------------

    Resolution: Duplicate

this is effectively the same as CASSANDRA-809
                
> What should happen when cassandra loses permissions to it's data directory and unable
to compact?
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1409
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1409
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Ran Tavory
>
> Due to administrative error one of the hosts in the cluster lost permission to write
to it's data directory.
> So I started seeing errors in the log, however, the server continued serving traffic.
It wasn't able to compact and do other write operations but it didn't crash.
> I was wondering wether that's by design and if so, is this a good one... I guess I want
to know if really bad things happen to my cluster...
> logs look like that...
>  INFO [FLUSH-TIMER] 2010-08-11 07:53:14,683 ColumnFamilyStore.java (line 357) KvAds has
reached its threshold; switching in a fresh Memtable at CommitLogContext(file='/outbrain/cassandra/commitlog/Commi
> tLog-1281505164614.log', position=88521163)
>  INFO [FLUSH-TIMER] 2010-08-11 07:53:14,683 ColumnFamilyStore.java (line 609) Enqueuing
flush of Memtable(KvAds)@851225759
>  INFO [FLUSH-WRITER-POOL:1] 2010-08-11 07:53:14,684 Memtable.java (line 148) Writing
Memtable(KvAds)@851225759
> ERROR [FLUSH-WRITER-POOL:1] 2010-08-11 07:53:14,688 DebuggableThreadPoolExecutor.java
(line 94) Error in executor futuretask
> java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.io.FileNotFoundException:
/outbrain/cassandra/data/outbrain_kvdb/KvAds-tmp-249-Data.db (Permission denied)
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
>         at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.afterExecute(DebuggableThreadPoolExecutor.java:86)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: /outbrain/cassandra/data/outbrain_kvdb/KvAds-tmp-249-Data.db
(Permission denied)
>         at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:34)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         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)
> ... more
> Jonathan Ellis:
> That's a tough call -- you can also come up with scenarios where you'd
> rather have it read-only than completely dead.
> Benjamin Black:
> Useful config option, perhaps?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message