cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arindam Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11978) StreamReader fails to write sstable if CF directory is symlink
Date Fri, 08 Jul 2016 10:39:10 GMT

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

Arindam Gupta commented on CASSANDRA-11978:
-------------------------------------------

Can you please provide some more information to proceed further, need to clarify the following
points :

1) In your case soft link name is "/path/to/data/dir/AnotherDisk/CFName" and actual path i.e.
target path is "/path/to/data/dir/Keyspace/CFName", am I right?

2) Have you made any changes in cassandra.yaml or other config files for this scenario?

3) If I execute "nodetool flush" command after inserting some data into a table will I get
this error immediately during this nodetool command execution?



> StreamReader fails to write sstable if CF directory is symlink
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-11978
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11978
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>            Reporter: Michael Frisch
>              Labels: lhf
>
> I'm using Cassandra v2.2.6.  If the CF is stored as a symlink in the keyspace directory
on disk then StreamReader.createWriter fails because Descriptor.fromFilename is passed the
actual path on disk instead of path with the symlink.
> Example:
> /path/to/data/dir/Keyspace/CFName -> /path/to/data/dir/AnotherDisk/CFName
> Descriptor.fromFilename is passed "/path/to/data/dir/AnotherDisk/CFName" instead of "/path/to/data/dir/Keyspace/CFName",
then it concludes that the keyspace name is "AnotherDisk" which is erroneous. I've temporarily
worked around this by using cfs.keyspace.getName() to get the keyspace name and cfs.name to
get the CF name as those are correct.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message