cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Frisch (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-11978) StreamReader fails to write sstable if CF directory is symlink
Date Fri, 08 Jul 2016 16:04:11 GMT

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

Michael Frisch edited comment on CASSANDRA-11978 at 7/8/16 4:03 PM:
--------------------------------------------------------------------

We haven't tried to bootstrap a new node, this occurred 100% of the time when trying to do
a repair in our production environment.

Worth noting: This cluster has been around since C* version 0.8.6. All sstables are the current
version.


was (Author: blafrisch):
We haven't tried to bootstrap a new node, this occurred 100% of the time when trying to do
a repair in our production environment.

Worth noting: This cluster has been around since C* version 0.8.6.

> 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