[jira] [Updated] (CASSANDRA-11849) Potential data directory problems due to CFS getDirectories logic

2016-06-01 Thread T Jake Luciani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

T Jake Luciani updated CASSANDRA-11849:
---
   Resolution: Fixed
Fix Version/s: 3.0.7
   3.7
   Status: Resolved  (was: Patch Available)

committed {{7eb464734b0732ab3c6cd2a5c3409085c81f95a7}}

> 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
> Fix For: 3.7, 3.0.7
>
>
> 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)

[jira] [Updated] (CASSANDRA-11849) Potential data directory problems due to CFS getDirectories logic

2016-05-31 Thread T Jake Luciani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

T Jake Luciani updated CASSANDRA-11849:
---
Status: Patch Available  (was: Open)

> 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)

[jira] [Updated] (CASSANDRA-11849) Potential data directory problems due to CFS getDirectories logic

2016-05-25 Thread Blake Eggleston (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Blake Eggleston updated CASSANDRA-11849:

Reviewer: T Jake Luciani

> 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)

[jira] [Updated] (CASSANDRA-11849) Potential data directory problems due to CFS getDirectories logic

2016-05-19 Thread T Jake Luciani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

T Jake Luciani updated CASSANDRA-11849:
---
Description: 
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 

  was:
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 CFA 
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 


> 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)