Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 29 Jul 2016 02:35:20 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12992817.1469600077000.164680.1469759720637@Atlassian.JIRA>
In-Reply-To: <JIRA.12992817.1469600077000@Atlassian.JIRA>
References: <JIRA.12992817.1469600077000@Atlassian.JIRA> <JIRA.12992817.1469600077807@arcas>
Subject: [jira] [Commented] (HBASE-16289) AsyncProcess stuck messages need
 to print region/server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 29 Jul 2016 02:35:22 -0000


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

stack commented on HBASE-16289:
-------------------------------

That log emission looks beautiful [~carp84]. Is that all it takes? That is much smarter than the way I was trying to go about it (overriding ServiceExecutor..). +1.

What are those hadoop failures about?


> AsyncProcess stuck messages need to print region/server
> -------------------------------------------------------
>
>                 Key: HBASE-16289
>                 URL: https://issues.apache.org/jira/browse/HBASE-16289
>             Project: HBase
>          Issue Type: Bug
>          Components: Operability
>            Reporter: stack
>            Assignee: Yu Li
>            Priority: Critical
>              Labels: beginner
>         Attachments: HBASE-16289.patch, HBASE-16289.patch
>
>
> Fix these out of AsyncProcess... 
> '2016-07-21 20:16:56.477 o.a.h.h.c.AsyncProcess [INFO] #13, waiting for 25  actions to finish'
> They are totally opaque, when you see one, it means a request is ten seconds old at least. It is awkward to do but we should be able to emit region/server.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)