Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 12 Jun 2014 15:58:03 +0000 (UTC)
From: "Jimmy Xiang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12705625.1396263410876.118103.1402588683652@arcas>
In-Reply-To: <JIRA.12705625.1396263410876@arcas>
References: <JIRA.12705625.1396263410876@arcas>
Subject: [jira] [Commented] (HBASE-10871) Indefinite OPEN/CLOSE wait on busy
 RegionServers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-10871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029298#comment-14029298 ] 

Jimmy Xiang commented on HBASE-10871:
-------------------------------------

Looks good to me. We need to re/set socketTimeoutException to false around line 1780. Can you also post patches for 0.98 and trunk?

> Indefinite OPEN/CLOSE wait on busy RegionServers
> ------------------------------------------------
>
>                 Key: HBASE-10871
>                 URL: https://issues.apache.org/jira/browse/HBASE-10871
>             Project: HBase
>          Issue Type: Improvement
>          Components: Balancer, master, Region Assignment
>    Affects Versions: 0.94.6
>            Reporter: Harsh J
>            Assignee: Esteban Gutierrez
>         Attachments: HBASE-10871.v0.patch
>
>
> We observed a case where, when a specific RS got bombarded by a large amount of regular requests, spiking and filling up its RPC queue, the balancer's invoked unassigns and assigns for regions that dealt with this server entered into an indefinite retry loop.
> The regions specifically began waiting in PENDING_CLOSE/PENDING_OPEN states indefinitely cause of the HBase Client RPC from the ServerManager at the master was running into SocketTimeouts. This caused a region unavailability in the server for the affected regions. The timeout monitor retry default of 30m in 0.94's AM compounded the waiting gap further a bit more (this is now 10m in 0.95+'s new AM, and has further retries before we get there, which is good).
> Wonder if there's a way to improve this situation generally. PENDING_OPENs may be easy to handle - we can switch them out and move them elsewhere. PENDING_CLOSEs may be a bit more tricky, but there must perhaps at least be a way to "give up" permanently on a movement plan, and letting things be for a while hoping for the RS to recover itself on its own (such that clients also have a chance of getting things to work in the meantime)?


--
This message was sent by Atlassian JIRA
(v6.2#6252)