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

Brandon Williams commented on CASSANDRA-2940:
---------------------------------------------

{quote}
If I understand correctly, the preferred approach would be something like this:

-New methods in StorageProxyMBean expose this property.
-StorageProxy implements this as a call to the new static method 
DatabaseDescriptor.setRpcTimeout(Long).
-DatabaseDescriptor.setRpcTimeout(Long) changes the value of 
Config.rpc_timeout_in_ms (notice that my understanding is that we should keep 
this as it is, so that the default value can still be loaded from the yaml file 
if needed).
{quote}

Yes, this is correct, we should never be rewriting the yaml.  Thanks!
                
> Make rpc_timeout_in_ms into a jmx mbean property
> ------------------------------------------------
>
>                 Key: CASSANDRA-2940
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2940
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremy Hanna
>              Labels: lhf
>         Attachments: trunk-CASSANDRA-2940.txt
>
>
> When using the hadoop integration especially, experimenting with 
> rpc_timeout_in_ms is a pain if you have to restart every server in the 
> cluster for it to take effect.  This would be an improvement to make it into 
> a jmx mbean property to set it at runtime.  The yaml file could be updated 
> separately so it would be persistent still.

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

        

Reply via email to