[
https://issues.apache.org/jira/browse/HBASE-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614801#comment-13614801
]
Enis Soztutar commented on HBASE-8196:
--------------------------------------
bq. Ok, a good chunk of this is ws comments changes. Ideally we'd have less of
this in a review.
Agreed, but unless we fix the current formatting, and be more strict about the
patches in, we will have to deal with it.
Thanks for taking a look.
bq. Was this intentional?
No, see my earlier comments.
bq. Any compatibility concerns? Can you spell out the cases?
Cases would be:
(1) Old / new master
(2) Old new META RS
(3) Old new other RS
(4) Master updated after META
(1) is fine, since Master's and SSH's fixup checks have ben kept around. SSH
processes dead regions by going through META.
(2) META server deploying new code wont be a problem. The old way will just
work. META server having old version of the code, but RS's having newer
versions might be. The META update in SplitTransaction will fail because of not
deployed coprocessor, and it will cause RS to abort. We can do a quick check in
SplitRequest to not split if META is not updated.
(3) This won't be a problem.
(4) Master updates the META table's definition. If master is updated after the
META server, then the META server won't see the new META table def unless the
region is reopened.
Let me think about how we can handle 2 and 4 in a meaningful way. If not, we
can abort.
> Port HBASE-7721 Atomic multi-row mutations in META to 0.94
> ----------------------------------------------------------
>
> Key: HBASE-8196
> URL: https://issues.apache.org/jira/browse/HBASE-8196
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.94.7
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.94.7
>
> Attachments: hbase-7721_v4-0.94.patch
>
>
> There has been some interest in porting region merge (HBASE-7403), and making
> splits more stable in 0.94. For online merge, we depend on HBASE-7721, thus
> we might need the backport.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
