[
https://issues.apache.org/jira/browse/CASSANDRA-8713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965754#comment-14965754
]
Jeremy Hanna commented on CASSANDRA-8713:
-----------------------------------------
In addition to default or unlisted values in the yaml, this could also be for
calculated values. For example, memtable_cleanup_threshold could be printed
out in the log. This type of thing saves having to look in the source for
either the default value or the way that the value is calculated when trying to
troubleshoot an issue.
> Print out all current values of available configuration parameters at startup
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-8713
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8713
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Wei Deng
> Priority: Minor
>
> I know we have https://issues.apache.org/jira/browse/CASSANDRA-6456 to print
> out all parameters configured in cassandra.yaml at startup as in here
> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/config/YamlConfigurationLoader.java#L124-136,
> however, how about those parameters that we don't configure in
> cassandra.yaml? It will be helpful to troubleshooting if we can add a similar
> logConfig() method for all parameters in
> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/config/Config.java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
