[
https://issues.apache.org/jira/browse/HBASE-15924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588215#comment-15588215
]
Hadoop QA commented on HBASE-15924:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 15s
{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m 4s
{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m 5s
{color} | {color:red} The patch generated 62 new + 432 unchanged - 25 fixed =
494 total (was 457) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 24s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1 or 3.0.0-alpha1. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 1m
27s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
12s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 35m 34s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:7bda515 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12834122/HBASE-15924.master.0004.patch
|
| JIRA Issue | HBASE-15924 |
| Optional Tests | asflicense shellcheck shelldocs |
| uname | Linux ddab9cfb6734 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28
20:42:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 67f1ac1 |
| shellcheck | v0.4.4 |
| shellcheck |
https://builds.apache.org/job/PreCommit-HBASE-Build/4098/artifact/patchprocess/diff-patch-shellcheck.txt
|
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/4098/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Enhance hbase services autorestart capability to hbase-daemon.sh
> -----------------------------------------------------------------
>
> Key: HBASE-15924
> URL: https://issues.apache.org/jira/browse/HBASE-15924
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.98.19
> Reporter: Loknath Priyatham Teja Singamsetty
> Assignee: Loknath Priyatham Teja Singamsetty
> Fix For: 0.98.24
>
> Attachments: HBASE-15924.master.0001.patch,
> HBASE-15924.master.0002.patch, HBASE-15924.master.0003.patch,
> HBASE-15924.master.0004.patch
>
>
> As part of HBASE-5939, the autorestart for hbase services has been added to
> deal with scenarios where hbase services (master/regionserver/master-backup)
> gets killed or goes down leading to unplanned outages. The changes were made
> to hbase-daemon.sh to support autorestart option.
> However, the autorestart implementation doesn't work in standalone mode and
> other than that have few gaps with the implementation as per release notes of
> HBASE-5939. Here is an attempt to re-design and fix the functionality
> considering all possible usecases with hbase service operations.
> Release Notes of HBASE-5939:
> ------------------------------------------
> When launched with autorestart, HBase processes will automatically restart if
> they are not properly terminated, either by a "stop" command or by a cluster
> stop. To ensure that it does not overload the system when the server itself
> is corrupted and the process cannot be restarted, the server sleeps for 5
> minutes before restarting if it was already started 5 minutes ago previously.
> To use it, launch the process with "bin/start-hbase autorestart". This option
> is not fully compatible with the existing "restart" command: if you ask for a
> restart on a server launched with autorestart, the server will restart but
> the next server instance won't be automatically restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
