[
https://issues.apache.org/jira/browse/HBASE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112021#comment-16112021
]
Appy commented on HBASE-18102:
------------------------------
TestShell is in [flaky excludes
list|https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/*view*/],
so it won't run as part of precommit.
I ran the test locally with this patch on top of master and it passed, so
pushing to fix broken tests
> [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)
