[ https://issues.apache.org/jira/browse/CASSANDRA-13728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Jirsa updated CASSANDRA-13728: ----------------------------------- Fix Version/s: (was: 3.11.1) (was: 3.0.15) 4.x 3.11.x 3.0.x > Provide max hint window as part of nodetool > ------------------------------------------- > > Key: CASSANDRA-13728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13728 > Project: Cassandra > Issue Type: Improvement > Components: Tools > Reporter: Milan Milosevic > Assignee: Varun Gupta > Priority: Minor > Labels: lhf > Fix For: 3.0.x, 3.11.x, 4.x > > Attachments: display-max-hint-handoff-period.patch > > > Currently it is not possible to get max_hint_window over nodetool. The > information is available through StorageProxyMBean, though. Since max hint > window information is needed in order to asses what kind of failure recovery > should be performed for a node that goes down (bootstrap or just restart), it > would be handy if max hint window is easily accessible using nodetool. > Currently nodetool statushandoff output is: > {code} > [centos@cassandra-node]$ nodetool statushandoff > Hinted handoff is running > {code} > The output could be improved to look like this: > {code} > [centos@cassandra-node]$ nodetool statushandoff > Hinted handoff is running with max hint window (ms): 10800000 > {code} > Implementation is quite trivial (fetch the info from the StorageProxyMBean > from the StatusHandoff class). I can provide the patch for this, if it is > agreed that this it right approach. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org