Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 9 Mar 2016 01:54:40 +0000 (UTC)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12944636.1456429345000.40797.1457488480963@Atlassian.JIRA>
In-Reply-To: <JIRA.12944636.1456429345000@Atlassian.JIRA>
References: <JIRA.12944636.1456429345000@Atlassian.JIRA>
 <JIRA.12944636.1456429345788@arcas>
Subject: [jira] [Commented] (YARN-4736) Issues with HBaseTimelineWriterImpl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sangjin Lee commented on YARN-4736:
-----------------------------------

bq. BufferedMutatorImpl#flush() appeared in stack trace. However, if the hbase cluster was shutdown, the flush wouldn't succeed.

Right, I fully expect that the flush would not succeed if the cluster is shut down. What I'm concerned about is that not only did the flush fail, it does appear that it remained stuck in flush, preventing the client from shutting it down. That would be unexpected.

I know this is against 1.0.2 which is somewhat of an older version, but would it be helpful if I filed a HBASE JIRA to see if others have seen this or have suggestions?

> Issues with HBaseTimelineWriterImpl
> -----------------------------------
>
>                 Key: YARN-4736
>                 URL: https://issues.apache.org/jira/browse/YARN-4736
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Naganarasimha G R
>            Assignee: Vrushali C
>            Priority: Critical
>              Labels: yarn-2928-1st-milestone
>         Attachments: hbaseException.log, threaddump.log
>
>
> Faced some issues while running ATSv2 in single node Hadoop cluster and in the same node had launched Hbase with embedded zookeeper.
> # Due to some NPE issues i was able to see NM was trying to shutdown, but the NM daemon process was not completed due to the locks.
> # Got some exception related to Hbase after application finished execution successfully. 
> will attach logs and the trace for the same


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