[
https://issues.apache.org/jira/browse/YARN-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172779#comment-15172779
]
Sangjin Lee commented on YARN-4736:
-----------------------------------
{quote}
Was checking with our hbase team from the logs and the trace they were
informing that the issue might be due to bad connectivity with the zookeeper,
but it strange to see that in the local node setup. So i suspect that there is
some issue with my hbase setup, so planning to test with hbase-1.0.3 tar.
{quote}
Regardless of what happens on the cluster, the client (NM in this case) should
not lock up. So in that sense, I think the "deadlock" we're seeing should be
looked at from the client-side. [[email protected]], do you recall seeing any
issues like this?
{quote}
But also would like to know whether you guys are facing the same issue or its
only me who is facing it ?
{quote}
I haven't had a chance to try to reproduce it yet. I'll try it as soon as
feasible. Does this happen every time you run the timeline service performance
test with the latest branch?
> 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)
