[
https://issues.apache.org/jira/browse/HBASE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112056#comment-16112056
]
Hadoop QA commented on HBASE-18102:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
41s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
5s{color} | {color:red} The patch generated 2 new + 345 unchanged - 4 fixed =
347 total (was 349) {color} |
| {color:red}-1{color} | {color:red} ruby-lint {color} | {color:red} 0m
12s{color} | {color:red} The patch generated 2 new + 511 unchanged - 0 fixed =
513 total (was 511) {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}
30m 40s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
52s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 36m 11s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18102 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12880141/HBASE-18102.master.002.patch
|
| Optional Tests | asflicense unit rubocop ruby_lint |
| uname | Linux 9c19d94ca98a 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 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 / 71151eb |
| rubocop | v0.49.1 |
| rubocop |
https://builds.apache.org/job/PreCommit-HBASE-Build/7892/artifact/patchprocess/diff-patch-rubocop.txt
|
| ruby-lint | v2.3.1 |
| ruby-lint |
https://builds.apache.org/job/PreCommit-HBASE-Build/7892/artifact/patchprocess/diff-patch-ruby-lint.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7892/testReport/ |
| modules | C: hbase-shell U: hbase-shell |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7892/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> [SHELL] Purge close_region command that allows by-pass of Master
> ----------------------------------------------------------------
>
> Key: HBASE-18102
> URL: https://issues.apache.org/jira/browse/HBASE-18102
> Project: HBase
> Issue Type: Sub-task
> Components: Operability, shell
> Reporter: stack
> Assignee: Appy
> Fix For: 2.0.0, 3.0.0
>
> Attachments: HBASE-18102.master.001.patch,
> HBASE-18102.master.002.patch
>
>
> In AMv2, if a RS is not aligned with Master notions of how the world is, then
> the Master will kill the deviant RS (TODO: is forcing compliance via less
> radical means -- but that is how it is currently).
> The shell currently allows by-passing the Master to make cluster
> modifications such as our being able to send a close directly to a
> RegionServer for it to execute locally. This facility was used in the past to
> do fix-up when Master lost account of Region locations. In the new regime,
> such mis-accounting should no longer happen and, should a user mistakenly do
> an explicit close against a RS, the consequences will be more than the user
> bargained for; the Master will shut down the RS as soon as it reports close
> of a Region the master thinks should be open (No independence allowed!).
> This issue is to review shell Region and Table manipulation commands to purge
> those that by-pass Master or at least to add big warning.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
