[jira] [Comment Edited] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories

2013-01-31 Thread Aleksey Yeschenko (JIRA)

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

Aleksey Yeschenko edited comment on CASSANDRA-5196 at 1/31/13 11:27 PM:


The exception is thrown by this method:

{noformat}
public static void createDirectory(File directory)
{
if (!directory.exists())
{
if (!directory.mkdirs())
throw new FSWriteError(new IOException("Failed to mkdirs " + 
directory), directory);
}
}
{noformat}

So it seems like the directory didn't exist, it tried to create one, but failed 
(I assume it had something to do with permissions).

Can't reproduce. Can you, [~rstrickland]?

  was (Author: iamaleksey):
The exception is thrown by this method:

{noformat}
public static void createDirectory(File directory)
{
if (!directory.exists())
{
if (!directory.mkdirs())
throw new FSWriteError(new IOException("Failed to mkdirs " + 
directory), directory);
}
}
{noformat}

So it seems like the directory didn't exist, it tried to create one, but failed 
(I assume it had something to do with permissions).

Can't reproduce. Can you, [~ipv6guru]?
  
> IllegalStateException thrown when running new installation with old data 
> directories
> 
>
> Key: CASSANDRA-5196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.1
> Environment: CentOS 5.5
>Reporter: Robbie Strickland
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> If you install 1.2.1 when there are existing data directories, the scrub 
> operation fails, throwing this exception:
> ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
> gossiper and the RPC server
> ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
> Exception encountered during startup
> java.lang.IllegalStateException: No configured daemon
>   at 
> org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
>   at 
> org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
>   at org.apache.cassandra.db.Directories.(Directories.java:113)
>   at org.apache.cassandra.db.Directories.create(Directories.java:91)
>   at 
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
>   at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
>   at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
>   at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
> This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Comment Edited] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories

2013-02-04 Thread Haifeng Wang (JIRA)

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

Haifeng Wang edited comment on CASSANDRA-5196 at 2/5/13 3:44 AM:
-

RHEL 6.2, 64bit.
All operations were done by root user.
/mnt/storage/cassandra not removed. data and commitlog folders removed.
{quote}

drwxr-xr-x 4 root root  4096 Feb  4 22:18 cassandra
{quote}

  was (Author: haifeng):
RHEL 6.2, 64bit.
All operations were done by root user.
  
> IllegalStateException thrown when running new installation with old data 
> directories
> 
>
> Key: CASSANDRA-5196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.1
> Environment: CentOS 5.5
>Reporter: Robbie Strickland
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> If you install 1.2.1 when there are existing data directories, the scrub 
> operation fails, throwing this exception:
> ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
> gossiper and the RPC server
> ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
> Exception encountered during startup
> java.lang.IllegalStateException: No configured daemon
>   at 
> org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
>   at 
> org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
>   at org.apache.cassandra.db.Directories.(Directories.java:113)
>   at org.apache.cassandra.db.Directories.create(Directories.java:91)
>   at 
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
>   at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
>   at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
>   at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
> This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Comment Edited] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories

2013-02-04 Thread Haifeng Wang (JIRA)

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

Haifeng Wang edited comment on CASSANDRA-5196 at 2/5/13 6:29 AM:
-

The workaround is do not create the folder "data" manually. Let Cassandra 
create it. Then start Cassandra. If create the "data" folder manually, will get 
the error.
All these operations are about the first time to run Cassandra. 
{quote}
Stop Cassandra. Remove /mnt/storage/cassandra/data/* - all the sstable 
directories inside data, but NOT /mnt/storage/cassandra/data/ itself. Then 
start Cassandra again ant tell me if it works all right or fails as if you 
created it manually. Thanks.
{quote}
Run Cassandra successfully, then stop it, remove 
"/mnt/storage/cassandra/data/*" and run Cassandra again, the Cassandra started 
without error.

  was (Author: haifeng):
The workaround is do not create the folder "data" manually. Let Cassandra 
create it. Then start Cassandra. If create the "data" folder manually, will get 
the error.
All these operations are about the first time to run Cassandra. 
  
> IllegalStateException thrown when running new installation with old data 
> directories
> 
>
> Key: CASSANDRA-5196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.1
> Environment: CentOS 5.5
>Reporter: Robbie Strickland
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> If you install 1.2.1 when there are existing data directories, the scrub 
> operation fails, throwing this exception:
> ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
> gossiper and the RPC server
> ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
> Exception encountered during startup
> java.lang.IllegalStateException: No configured daemon
>   at 
> org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
>   at 
> org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
>   at org.apache.cassandra.db.Directories.(Directories.java:113)
>   at org.apache.cassandra.db.Directories.create(Directories.java:91)
>   at 
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
>   at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
>   at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
>   at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
> This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Comment Edited] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories

2013-02-04 Thread Haifeng Wang (JIRA)

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

Haifeng Wang edited comment on CASSANDRA-5196 at 2/5/13 6:33 AM:
-

Issue reproduced on my machine.
Environment:
Redhat Linux, Cassandra 1.2.1 unzipped to a NFS mounted folder 
(/mnt/storage/cassandra). 
Create data/commitlog folder manually in the NFS folder(mkdir -p 
/mnt/storage/cassandra/data, mkdir -p /mnt/storage/cassandra/commitlog).
config file updated.
Start Cassandra, "bin/cassandra -f", same error found.
{quote}
 INFO 22:15:06,283 Found table data in data directories. Consider using the CLI 
to define your schema.
ERROR 22:15:06,495 Stopping the gossiper and the RPC server
ERROR 22:15:06,505 Exception in thread Thread[OptionalTasks:1,5,main]
java.lang.IllegalStateException: No configured daemon
at 
org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
at 
org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
at org.apache.cassandra.db.Directories.(Directories.java:113)
at org.apache.cassandra.db.Directories.create(Directories.java:91)
at 
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:379)
at 
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:364)
at org.apache.cassandra.db.Table.initCf(Table.java:337)
at org.apache.cassandra.db.Table.(Table.java:280)
at org.apache.cassandra.db.Table.open(Table.java:110)
at org.apache.cassandra.db.Table.open(Table.java:88)
at org.apache.cassandra.db.Table$1.apply(Table.java:82)
at org.apache.cassandra.db.Table$1.apply(Table.java:79)
at com.google.common.collect.Iterators$9.transform(Iterators.java:893)
at 
com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
at 
org.apache.cassandra.db.ColumnFamilyStore.all(ColumnFamilyStore.java:1664)
at 
org.apache.cassandra.db.MeteredFlusher.countFlushingBytes(MeteredFlusher.java:114)
at org.apache.cassandra.db.MeteredFlusher.run(MeteredFlusher.java:41)
at 
org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor$UncomplainingRunnable.run(DebuggableScheduledThreadPoolExecutor.java:75)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
 INFO 22:15:06,560 No commitlog files found; skipping replay
{quote}

Remove above folders(data/commitlog) and restart Cannandra, issue resolved.

  was (Author: haifeng):
Issue reproduced on my machine.
Environment:
Redhat Linux, Cassandra 1.2.1 unzipped to a NFS mounted folder 
(/mnt/storage/cassandra). 
Create data/commitlog folder manually in the NFS folder(mkdir -p 
/mnt/storage/cassandra/data, mkdir -p /mnt/storage/cassandra/commitlog).
config file updated.
Start Cassandra, "bin/cassandra -f", same error found.
{quote}
 INFO 22:15:06,283 Found table data in data directories. Consider using the CLI 
to define your schema.
ERROR 22:15:06,495 Stopping the gossiper and the RPC server
ERROR 22:15:06,505 Exception in thread Thread[OptionalTasks:1,5,main]
java.lang.IllegalStateException: No configured daemon
at 
org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
at 
org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
at org.apache.cassandra.db.Directories.(Directories.java:113)
at org.apache.cassandra.db.Directories.create(Directories.java:91)
at 
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:379)
at 
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:364)
at org.apache.cassandra.db.Table.initCf(Table.java:337)
at org.apache.cassandra.db.Table.(Table.java:280)
at org.apache.cassandra.db.Table.open(Table.java:110)
at org.apache.cassandra.db.Table.open(Table.java:88)
at org.apache.cassandra.db.Table$1.apply(Table.java:82)
at org.apache.cassandra.db.Table$1.apply(Table.java:79)
at com.google.common.collect.Iterators$9.transform(

[jira] [Comment Edited] (CASSANDRA-5196) IllegalStateException thrown when running new installation with old data directories

2013-02-04 Thread Haifeng Wang (JIRA)

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

Haifeng Wang edited comment on CASSANDRA-5196 at 2/5/13 6:39 AM:
-

{quote}
Stop Cassandra. Remove /mnt/storage/cassandra/data/* - all the sstable 
directories inside data, but NOT /mnt/storage/cassandra/data/ itself. Then 
start Cassandra again ant tell me if it works all right or fails as if you 
created it manually. Thanks.
{quote}
Run Cassandra successfully, then stop it, remove 
"/mnt/storage/cassandra/data/*" and run Cassandra again, the Cassandra started 
without error.

Then I did following test, no error found.
Remove all folders/files under /mnt/storage/cassandra/, create data folder 
manually, start Cassandra. 



  was (Author: haifeng):
The workaround is do not create the folder "data" manually. Let Cassandra 
create it. Then start Cassandra. If create the "data" folder manually, will get 
the error.
All these operations are about the first time to run Cassandra. 
{quote}
Stop Cassandra. Remove /mnt/storage/cassandra/data/* - all the sstable 
directories inside data, but NOT /mnt/storage/cassandra/data/ itself. Then 
start Cassandra again ant tell me if it works all right or fails as if you 
created it manually. Thanks.
{quote}
Run Cassandra successfully, then stop it, remove 
"/mnt/storage/cassandra/data/*" and run Cassandra again, the Cassandra started 
without error.
  
> IllegalStateException thrown when running new installation with old data 
> directories
> 
>
> Key: CASSANDRA-5196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.1
> Environment: CentOS 5.5
>Reporter: Robbie Strickland
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> If you install 1.2.1 when there are existing data directories, the scrub 
> operation fails, throwing this exception:
> ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the 
> gossiper and the RPC server
> ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387) 
> Exception encountered during startup
> java.lang.IllegalStateException: No configured daemon
>   at 
> org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
>   at 
> org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
>   at org.apache.cassandra.db.Directories.(Directories.java:113)
>   at org.apache.cassandra.db.Directories.create(Directories.java:91)
>   at 
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
>   at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
>   at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
>   at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
> This condition should produce a more reasonable exception.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira