Michael Shuler updated CASSANDRA-13950:
    Fix Version/s:     (was: 3.11.0)

> Metrics CsvReporterConfig fails to create directory if it exists and does not 
> work
> ----------------------------------------------------------------------------------
>                 Key: CASSANDRA-13950
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13950
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Metrics
>         Environment: Cassandra 3.11, Linux,  Ubuntu 15.04 (GNU/Linux 
> 3.19.0-84-generic x86_64).
>            Reporter: Lucas Benevides Dias
>            Priority: Minor
>              Labels: csvreporterconfig, error, metrics
>             Fix For: 3.11.x
>   Original Estimate: 3h
>  Remaining Estimate: 3h
> The metrics environment has the option of using a CsvReporterConfig, that 
> outputs the metrics in a directory that the user can put in the configuration 
> yaml file.
> If the directory doesn't exist, it is created and the metrics are written as 
> expected.
> However, if the directory already exists (suppose an unexpected cassandra 
> restart) the metrics aren't written in the directory. What I expected to 
> happen is to the metrics get written in the same directory, appending the new 
> values in the same CSV files they were been written before. This way there 
> would be continuity.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to