cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Pastuchov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7347) JMX StorageService bulkload
Date Wed, 04 Jun 2014 12:39:01 GMT


Alexei Pastuchov commented on CASSANDRA-7347:

Many thanks for your reply. But the dot in the path doesn't seem to be causal for the problem.
After moving sstables into other directory named according your suggestion I've got the same

Exception in thread "main" java.lang.RuntimeException: java.lang.IllegalArgumentException:
Invalid directory /home/palik/workspace/datastax-analytics-example/datastax_bulkload_demo/transactions
	at org.apache.cassandra.service.StorageService.bulkLoad(

The problem occurs by using cassandra installed via debian package as described here:

In next step I've removed installed cassandra and switched to cassandra git repository. So
bulkload to via ant built cassandra (git tag cassandra-2.0.7) work well. 
Now I'll start look for any differences in debian installation and git stand.  

> JMX StorageService bulkload
> ---------------------------
>                 Key: CASSANDRA-7347
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>         Environment: Ubuntu 13.10 x86_64
>            Reporter: Alexei Pastuchov
>             Fix For: 2.0.7
> My attempt to load sstables via JMX StorageService throws exception:
> Caused by: java.lang.IllegalArgumentException: Invalid directory /home/palik/workspace/datastax-analytics-example/datastax_analytics_demo/datastax_analytics_demo.transactions
> 	at org.apache.cassandra.service.StorageService.bulkLoadInternal(
> 	at org.apache.cassandra.service.StorageService.bulkLoad(
> but the directory definitely exists. 
> so loading by using sstableloader works well.
> sstableloader -d localhost /home/palik/workspace/datastax-analytics-example/datastax_analytics_demo/datastax_analytics_demo.transactions
> here is example I've used:
> Is it a known issue? I've been unable to find any hint.
> So for any help many thanks in advance.

This message was sent by Atlassian JIRA

View raw message