You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/07/03 20:01:47 UTC

[jira] Updated: (HBASE-1609) [part of hbase-1583] We wait on leases to expire before regionserver goes down. Rather, just let client fail

     [ https://issues.apache.org/jira/browse/HBASE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-1609:
-------------------------

    Attachment: 1609.patch

Here is a patch for the serverside.  It removes all the fancy scanner counting we used do.

In testing, serverside logs seem fine when outstanding scanner..... scanners start to get notserveringregionexception as the regions go down.

Client-side though goes crazy.... retries of zk and retries of scanner stuff.  Need to clean up client handling of this case before can commit, i'd suggest.

> [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.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.