[jira] [Updated] (CASSANDRA-3504) Storage paths exposed in JMX should be absolute/canonical

["Tyler Hobbs (Updated) (JIRA)" <ji...@apache.org>]

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

Tyler Hobbs updated CASSANDRA-3504:
-----------------------------------

    Attachment: 3504-v1.txt

v1 patch tries to convert the config filenames to their canonical form in StorageService.getCommitLogLocation(), etc.
                
> Storage paths exposed in JMX should be absolute/canonical
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-3504
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3504
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.2
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>            Priority: Trivial
>         Attachments: 3504-v1.txt
>
>
> The data, commitlog, and saved caches directories are exposed through JMX.  However, what's exposed is just exactly what's in the config file.  This can be ambiguous in some cases.  For example, on Windows, if your conf entry is "/var/log/cassandra/data", JMX will expose the String "/var/log/cassandra/data", but the actual directory used might be "C:\var\log\cassandra\data" or "D:\var\log\cassandra\data" -- there's no way to determine what drive letter is actually being used.
> Reporting the result of File.getCanonicalPath(filename) instead would eliminate the ambiguity.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira