[
https://issues.apache.org/jira/browse/HBASE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1609:
-------------------------
Attachment: 1609-v2.patch
This patch cancels leases when next is called and we're going down.
It also just closes all leases in HRS before we run close of all regions.
I don't see why we have to pussy-foot around with Scanners. They are reading.
If they get exception in middle of reading, then no big deal. It looks like
Scanners will get UnknownScannerException if cluster is shutting down on them.
I added javadoc saying this could be one of the reasons for an USE.
> [part of hbase-1583] We wait on leases to expire before regionserver goes
> down. Rather, just let client fail
> -------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-1609
> URL: https://issues.apache.org/jira/browse/HBASE-1609
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Fix For: 0.20.0
>
> Attachments: 1609-v2.patch, 1609.patch
>
>
> Addressing this issue will help hbase-1583. We should do for 0.20.0 and
> perhaps for 0.19.x even.
> Currently, if outstanding leases, in HRegion close, we'll hang until lease
> expires. Could be a minute. Could be worse, the client might come in and
> renew the lease a few times at least till it finishes out the region. This
> gets in way of regionserver shutting down fast.
> J-D suggests that regionserver should just go down and outstanding clients
> should fail rather than try and be nice to outstanding clients (in his case,
> his MR job had failed so no clients... but we insist on lease expiring).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
