[
https://issues.apache.org/jira/browse/HBASE-22183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811937#comment-16811937
]
stack commented on HBASE-22183:
-------------------------------
Excellent.
Rather than listing table states, elsewhere in help output I see we do this:
{{{Arrays.stream(TableState.State.values()).map(i ->
i.toString()).collect(Collectors.joining(", ")));}}} Should we do same here?
s/resource/resort/
s/for this is/are when/
s/due region/due to region/
s/on an/in an/
s/a running/by a running/
Nice clarification to the philosophy behind hbck2 operations.
I suppose we should figure a way to ship code.... code that can be interpreted
server-side. Super dangerous and insecure but maybe we figure something?
Thanks for working on this [~wchevreuil]
> [hbck2] Update hbck2 README to explain new "setRegionState" method.
> -------------------------------------------------------------------
>
> Key: HBASE-22183
> URL: https://issues.apache.org/jira/browse/HBASE-22183
> Project: HBase
> Issue Type: New Feature
> Reporter: Wellington Chevreuil
> Priority: Minor
> Attachments: HBASE-22183-master-001.patch
>
>
> HBase-22143 introduced new *setRegionState* method that allows for manually
> setting a region to an specific state, in meta. This was added a client side
> logic for updating region state, to workout case where region is left in
> OPENING state (unassigns/assigns will fail to progress here) on releases
> prior to 2.1.2 (when scheduleServerCrashProcedure was added to Master's
> HbckService). To reflect, this jira adds not only setRegionState description,
> but also additional explanations on the Overview section of README.md file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
