[jira] [Updated] (HBASE-5863) Improve the graceful_stop.sh CLI help (especially about reloads)
[ https://issues.apache.org/jira/browse/HBASE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-5863: - Fix Version/s: (was: 0.94.1) 0.94.0 Improve the graceful_stop.sh CLI help (especially about reloads) Key: HBASE-5863 URL: https://issues.apache.org/jira/browse/HBASE-5863 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.94.0 Reporter: Harsh J Assignee: Harsh J Priority: Minor Fix For: 0.92.2, 0.94.0 Attachments: HBASE-5863.patch Right now, graceful_stop.sh prints: {code} Usage: graceful_stop.sh [--config conf-dir] [--restart] [--reload] [--thrift] [--rest] hostname thrift If we should stop/start thrift before/after the hbase stop/start restIf we should stop/start rest before/after the hbase stop/start restart If we should restart after graceful stop reload Move offloaded regions back on to the stopped server debug Move offloaded regions back on to the stopped server hostnameHostname of server we are to stop {code} This does not help us specify that reload is actually a sub/additive-option to restart. Also, the debug line seems to still have an old copy/paste mistake. I've updated these two in the patch here. -- 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
[jira] [Updated] (HBASE-5863) Improve the graceful_stop.sh CLI help (especially about reloads)
[ https://issues.apache.org/jira/browse/HBASE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HBASE-5863: --- Attachment: HBASE-5863.patch Improve the graceful_stop.sh CLI help (especially about reloads) Key: HBASE-5863 URL: https://issues.apache.org/jira/browse/HBASE-5863 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.94.0 Reporter: Harsh J Assignee: Harsh J Priority: Minor Attachments: HBASE-5863.patch Right now, graceful_stop.sh prints: {code} Usage: graceful_stop.sh [--config conf-dir] [--restart] [--reload] [--thrift] [--rest] hostname thrift If we should stop/start thrift before/after the hbase stop/start restIf we should stop/start rest before/after the hbase stop/start restart If we should restart after graceful stop reload Move offloaded regions back on to the stopped server debug Move offloaded regions back on to the stopped server hostnameHostname of server we are to stop {code} This does not help us specify that reload is actually a sub/additive-option to restart. Also, the debug line seems to still have an old copy/paste mistake. I've updated these two in the patch here. -- 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
[jira] [Updated] (HBASE-5863) Improve the graceful_stop.sh CLI help (especially about reloads)
[ https://issues.apache.org/jira/browse/HBASE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HBASE-5863: --- Status: Patch Available (was: Open) Improve the graceful_stop.sh CLI help (especially about reloads) Key: HBASE-5863 URL: https://issues.apache.org/jira/browse/HBASE-5863 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.94.0 Reporter: Harsh J Assignee: Harsh J Priority: Minor Attachments: HBASE-5863.patch Right now, graceful_stop.sh prints: {code} Usage: graceful_stop.sh [--config conf-dir] [--restart] [--reload] [--thrift] [--rest] hostname thrift If we should stop/start thrift before/after the hbase stop/start restIf we should stop/start rest before/after the hbase stop/start restart If we should restart after graceful stop reload Move offloaded regions back on to the stopped server debug Move offloaded regions back on to the stopped server hostnameHostname of server we are to stop {code} This does not help us specify that reload is actually a sub/additive-option to restart. Also, the debug line seems to still have an old copy/paste mistake. I've updated these two in the patch here. -- 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
[jira] [Updated] (HBASE-5863) Improve the graceful_stop.sh CLI help (especially about reloads)
[ https://issues.apache.org/jira/browse/HBASE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-5863: - Resolution: Fixed Fix Version/s: 0.94.1 0.92.2 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to 0.92, 0.94 and trunk. Thanks for the patch Harsh. Improve the graceful_stop.sh CLI help (especially about reloads) Key: HBASE-5863 URL: https://issues.apache.org/jira/browse/HBASE-5863 Project: HBase Issue Type: Improvement Components: scripts Affects Versions: 0.94.0 Reporter: Harsh J Assignee: Harsh J Priority: Minor Fix For: 0.92.2, 0.94.1 Attachments: HBASE-5863.patch Right now, graceful_stop.sh prints: {code} Usage: graceful_stop.sh [--config conf-dir] [--restart] [--reload] [--thrift] [--rest] hostname thrift If we should stop/start thrift before/after the hbase stop/start restIf we should stop/start rest before/after the hbase stop/start restart If we should restart after graceful stop reload Move offloaded regions back on to the stopped server debug Move offloaded regions back on to the stopped server hostnameHostname of server we are to stop {code} This does not help us specify that reload is actually a sub/additive-option to restart. Also, the debug line seems to still have an old copy/paste mistake. I've updated these two in the patch here. -- 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