[
https://issues.apache.org/jira/browse/CASSANDRA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruben Terrazas updated CASSANDRA-2940:
--------------------------------------
Attachment: trunk-CASSANDRA-2940.txt
Patch I propose for this issue:
I implemented the new ConfigMBean.java interface in the Config.java class, and
only exposed the desired property's getter and setter.
I also registered the bean in the Config constructor because it seemed to me
the best place to do so, I could have done this in DatabaseDescriptor, but it
seemed cleaner to do so here.
I added Jeremy Hanna as reviewer, don't know if this is the right thing to do,
but if he could give the patch a look, I'd be appreciative.
As stated in the guidelines, I re-threw exceptions as Runtime exception, since
no callers could handle them (ended up in a static block).
> 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
