[
https://issues.apache.org/jira/browse/HBASE-29814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Kumar Kumawat updated HBASE-29814:
----------------------------------------
Description:
This Jira is to handle below part (bold) from the parent JIRA.
2. The next step is to put the region of the source RegionServer in the MOVING
state. This will trigger MemStore flushing. In the MOVING state, the region
will not accept new (read or write) operations but *continue serving
in-progress read (gets and scans) operations. Please note as part of snapshot
isolation, these operations are allowed.* This is essentially the initial part
of the region CLOSING state where the MemStore is flushed.
As HBase operation run with snapshot isolation, Region Server can continue
serve ongoing GET/SCAN operation. By default, for now we interrupt all the
ongoing opertion within 60 seconds.
Here also, only operation with IsolationLevel.READ_COMMITTED can be allowed.
Operation with isolationLevel.READ_UNCOMMITTED should be continued only on RS
where writes are happening.
was:
As HBase operation run with snapshot isolation, Region Server can continue
serve ongoing GET/SCAN operation. By default, for now we interrupt all the
ongoing opertion within 60 seconds.
Here also, only operation with IsolationLevel.READ_COMMITTED can be allowed.
Operation with isolationLevel.READ_UNCOMMITTED should be continued only on RS
where writes are happening.
> Allow ongoing Get/Scan operations during/after region closure
> -------------------------------------------------------------
>
> Key: HBASE-29814
> URL: https://issues.apache.org/jira/browse/HBASE-29814
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver
> Affects Versions: 3.0.0, 2.6.4, 2.5.13
> Reporter: Umesh Kumar Kumawat
> Assignee: Umesh Kumar Kumawat
> Priority: Minor
>
> This Jira is to handle below part (bold) from the parent JIRA.
> 2. The next step is to put the region of the source RegionServer in the
> MOVING state. This will trigger MemStore flushing. In the MOVING state, the
> region will not accept new (read or write) operations but *continue serving
> in-progress read (gets and scans) operations. Please note as part of snapshot
> isolation, these operations are allowed.* This is essentially the initial
> part of the region CLOSING state where the MemStore is flushed.
>
>
> As HBase operation run with snapshot isolation, Region Server can continue
> serve ongoing GET/SCAN operation. By default, for now we interrupt all the
> ongoing opertion within 60 seconds.
> Here also, only operation with IsolationLevel.READ_COMMITTED can be allowed.
> Operation with isolationLevel.READ_UNCOMMITTED should be continued only on RS
> where writes are happening.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
