[
https://issues.apache.org/jira/browse/YARN-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198862#comment-15198862
]
Anoop Sam John commented on YARN-4736:
--------------------------------------
When one RS is down, those regions in that would get moved to other RS(s). And
if that was a META serving RS, then META will get moved to new RS. So any way
next retries may get things moving. The issue here was that the entire HBase
cluster went down and no one brought it back.
There are certain must fix things in HBase. Will talk abt that in HBase jira.
> 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: NM_Hang_hbase1.0.3.tar.gz, 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)
