You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2016/01/01 01:43:39 UTC
[jira] [Updated] (CASSANDRA-10953) Make all timeouts configurable
via nodetool and jmx
[ https://issues.apache.org/jira/browse/CASSANDRA-10953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-10953:
-------------------------------------
Attachment: 10953-2.1-v2.txt
Thanks [~thobbs]. Attaching an updated v2 patch that has the updates. I added misc with a comment that it's the general rpc_timeout_in_ms to clarify. Not sure if that's the clearest way to do that.
> Make all timeouts configurable via nodetool and jmx
> ---------------------------------------------------
>
> Key: CASSANDRA-10953
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10953
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sebastian Estevez
> Assignee: Jeremy Hanna
> Labels: docs-impacting
> Fix For: 2.1.13
>
> Attachments: 10953-2.1-v2.txt, 10953-2.1.txt
>
>
> Specifically I was interested in being able to monitor and set stream_socket_timeout_in_ms from either (or both) nodetool and JMX.
> Chatting with [~thobbs] and [~jeromatron] we suspect it would also be useful to be able to view and edit other C* timeouts via nodetool and JMX.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)