[
https://issues.apache.org/jira/browse/HBASE-21644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730067#comment-16730067
]
Nihal Jain commented on HBASE-21644:
------------------------------------
{quote}This is not the correct way to fix the problem I'd say.
{quote}
Yes, I fully agree as it kills the whole point of re-open check based on open
sequence number.
Also, I checked with branch-1.3 installation, and found the following wrt
region replicas:
* We do not increase the open seq number in case of re-open of replica regions
(upon disable and then enable)
* But, if we put some data and flush it, then the open sequence number will be
updated for replica regions (upon disable and then enable)
The only concern I have is whether the non-updation of sequence number for
replica region upon re-open deliberate?
> Modify table procedure runs infinitely for a table having region replication
> > 1
> --------------------------------------------------------------------------------
>
> Key: HBASE-21644
> URL: https://issues.apache.org/jira/browse/HBASE-21644
> Project: HBase
> Issue Type: Bug
> Components: Admin
> Affects Versions: 3.0.0, 2.1.1, 2.1.2
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Critical
> Attachments: HBASE-21644.master.001.patch, HBASE-21644.master.UT.patch
>
>
> *Steps to reproduce*
> # Create a table with region replication set to a value greater than 1
> # Modify any of the table properties, say max file size
> *Expected Result*
> The modify table should succeed and run to completion.
> *Actual Result*
> The modify table keep running infinitely
> *Analysis/Issue*
> The problem occurs due to inifinitely looping between states
> {{REOPEN_TABLE_REGIONS_REOPEN_REGIONS}} and
> {{REOPEN_TABLE_REGIONS_CONFIRM_REOPENED}} of {{ReopenTableRegionsProcedure}},
> called as part of {{ModifyTableProcedure}}.
> *Consequences*
> For a table having region replicas:
> - Any modify table operation fails to complete
> - Also, enable table replication fails to complete as it is unable to change
> the replication scope of the table in source cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
