[
https://issues.apache.org/jira/browse/CASSANDRA-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302115#comment-15302115
]
Marcus Eriksson commented on CASSANDRA-11849:
---------------------------------------------
Having the compaction strategies do it sounds good to me but it would probably
be hard to fix this before 4.0.
Maybe we could use the java
[ServiceLoader|https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html]
interface for "external" compaction strategies and have the internal ones in a
list and initialize them early during startup? Was 5+ years since I touched
anything with the ServiceLoader, so there might be better solutions.
> Potential data directory problems due to CFS getDirectories logic
> -----------------------------------------------------------------
>
> Key: CASSANDRA-11849
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11849
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: Blake Eggleston
>
> CASSANDRA-8671 added the ability to change the data directory based on the
> compaction strategy.
> Since nothing uses this yet we haven't hit any issues but reading the code I
> see potential bugs for things like Transaction log cleanup and CFS
> initialization since these all use the default {{Directories}} location from
> the yaml.
> * {{Directories}} is passed into CFS constructor then possibly disregarded.
> * Startup checks like scrubDataDirectories are all using default Directories
> locations.
> * StandaloneSSTableUtil
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
