[jira] [Updated] (HBASE-18392) Add default value of ----movetimeout to rolling-restart.sh

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated HBASE-18392:
---
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

> Add default value of movetimeout to rolling-restart.sh
> --
>
> Key: HBASE-18392
> URL: https://issues.apache.org/jira/browse/HBASE-18392
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.0.0
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
> Fix For: 3.0.0
>
> Attachments: HBASE-18392-master-001.patch
>
>
> We are calling graceful_stop.sh in rolling-restart.sh with following line 
> {code}
> "$bin"/graceful_stop.sh --config ${HBASE_CONF_DIR} --restart --reload -nob 
> --maxthreads  \
> ${RR_MAXTHREADS} ${RR_NOACK} --movetimeout ${RR_MOVE_TIMEOUT} 
> $hostname
> {code} 
> and if we not specified --movetimeout option while calling rolling-restart.sh 
>  --graceful script will not work. My propose is to add default value for this 
> parameter same way we are doing in graceful_stop.sh



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18392) Add default value of ----movetimeout to rolling-restart.sh

[Samir Ahmic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samir Ahmic updated HBASE-18392:

Status: Patch Available  (was: Open)

> Add default value of movetimeout to rolling-restart.sh
> --
>
> Key: HBASE-18392
> URL: https://issues.apache.org/jira/browse/HBASE-18392
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.0.0
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
> Fix For: 3.0.0
>
> Attachments: HBASE-18392-master-001.patch
>
>
> We are calling graceful_stop.sh in rolling-restart.sh with following line 
> {code}
> "$bin"/graceful_stop.sh --config ${HBASE_CONF_DIR} --restart --reload -nob 
> --maxthreads  \
> ${RR_MAXTHREADS} ${RR_NOACK} --movetimeout ${RR_MOVE_TIMEOUT} 
> $hostname
> {code} 
> and if we not specified --movetimeout option while calling rolling-restart.sh 
>  --graceful script will not work. My propose is to add default value for this 
> parameter same way we are doing in graceful_stop.sh



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (HBASE-18392) Add default value of ----movetimeout to rolling-restart.sh

[Samir Ahmic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samir Ahmic updated HBASE-18392:

Attachment: HBASE-18392-master-001.patch

Here is very simple patch.

> Add default value of movetimeout to rolling-restart.sh
> --
>
> Key: HBASE-18392
> URL: https://issues.apache.org/jira/browse/HBASE-18392
> Project: HBase
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.0.0
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
> Fix For: 3.0.0
>
> Attachments: HBASE-18392-master-001.patch
>
>
> We are calling graceful_stop.sh in rolling-restart.sh with following line 
> {code}
> "$bin"/graceful_stop.sh --config ${HBASE_CONF_DIR} --restart --reload -nob 
> --maxthreads  \
> ${RR_MAXTHREADS} ${RR_NOACK} --movetimeout ${RR_MOVE_TIMEOUT} 
> $hostname
> {code} 
> and if we not specified --movetimeout option while calling rolling-restart.sh 
>  --graceful script will not work. My propose is to add default value for this 
> parameter same way we are doing in graceful_stop.sh



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)