You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/27 23:46:26 UTC

[jira] [Resolved] (CASSANDRA-3423) Log configuration on startup for troubleshooting

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

Jonathan Ellis resolved CASSANDRA-3423.
---------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.0.9)

This doesn't add a whole lot of value over "please attach your cassandra.yaml".

(Schema is not available there, but is less frequently needed, and is available via cli or cqlsh.  Finally, including 100s or 1000s of CF schema in the log on startup is too noisy.)
                
> Log configuration on startup for troubleshooting
> ------------------------------------------------
>
>                 Key: CASSANDRA-3423
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3423
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>              Labels: lhf
>
> It would help troubleshooting if we logged pertinent details about server and CF configuration on startup.

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