[
https://issues.apache.org/jira/browse/CASSANDRA-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039221#comment-14039221
]
Brandon Williams commented on CASSANDRA-7370:
---------------------------------------------
3.0. I'm not too crazy about this, however. I can almost guarantee we're
going to add some mbean and forget to update this table at some point, and it
seems to me an administrator is going to need JMX anyway to perform any
operation that nodetool does. Unless they also want "INSERT into gossip set ip
= null where ip = 192.168.0.1" to remove a node. Perhaps a more reasonable
approach would be to have a nodetool getconfig <item> operation instead of
abusing the storage system with phantom tables.
> 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
> Priority: Minor
> Labels: ponies
>
> 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)
