[jira] [Commented] (CASSANDRA-7370) Create a new system table "node_config" to load cassandra.yaml config data.

["Robert Stupp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063353#comment-14063353 ] 

Robert Stupp commented on CASSANDRA-7370:
-----------------------------------------

ping - shall we add this to 3.0?

* use a system KS table (as a schema table to distribute node config of all nodes to all other nodes) ?
* use a separate KS with "moderate" RF for the table ?
* switch in cassandra.yaml to turn writing to this table on and off ? Default off ?


> Create a new system table "node_config" to load cassandra.yaml config data.
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7370
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7370
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Config
>            Reporter: Hayato Shimizu
>            Assignee: Robert Stupp
>            Priority: Minor
>              Labels: ponies
>         Attachments: 7370-v1-prototype.diff, 7370-v2-with-jmx.diff
>
>
> Currently the node configuration information specified in cassandra.yaml can only be viewed via JMX or by looking at the file on individual machines.
> As an administrator, it would be extremely useful to be able to execute queries like the following example;
> select concurrent_reads from system.node_config;
> which will list all the concurrent_reads value from all of the nodes in a cluster.
> This will require a new table in the system keyspace and the data to be loaded (if required) during the bootstrap, and updated when MBeans attribute value updates are performed. The data from other nodes in the cluster is also required in the table.



--
This message was sent by Atlassian JIRA
(v6.2#6252)