[
https://issues.apache.org/jira/browse/HBASE-11760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129413#comment-14129413
]
stack commented on HBASE-11760:
-------------------------------
Here are more comments on the diagram. [~misty] how you suggest we integrate
Jimmy's fine work into the refguide... dev section I'd say.
Man, should we change OPEN to be named ONLINE? I suppose OPEN is ok... goes
well with OPENING, CLOSE, CLOSING...
Should you say where these states are noted? Are they in zk or are they only
for zk-less hbase assignment? Are these states written into meta table? Or
also into zk when zk does assign?
We should list FAILED_OPEN and FAILED_CLOSED on the UI.
Do we need CLOSED? Why not just mark region OFFLINE?
Would be fun to write a formal spec with this for input:
http://research.microsoft.com/en-us/um/people/lamport/tla/amazon.html
On the patch, the comments about PENDING_CLOSE going away help... explains why
some of the changes.
On the rest of the patch, it is not that large being mostly refactors of log
messages and new handling of removed exception as well as instituting max
retries in place of while loop. Let me try and have another go at review. I
got googledy-eyed down in AM.....
> Tighten up region state transition
> ----------------------------------
>
> Key: HBASE-11760
> URL: https://issues.apache.org/jira/browse/HBASE-11760
> Project: HBase
> Issue Type: Improvement
> Components: Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 2.0.0
>
> Attachments: hbase-11760.patch, hbase-11760_2.1.patch,
> hbase-11760_2.2.patch, hbase-11760_2.patch, rsm-2.pdf, rsm.pdf, rsm.png
>
>
> When a regionserver reports to master a region transition, we should check
> the current region state to be exactly what we expect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
