ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14070) App Timeline Server become stopped by itself (Upgrade from 2.1.2 to 2.1.3.0 )
Date Wed, 25 Nov 2015 21:07:11 GMT

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

Hudson commented on AMBARI-14070:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3911 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3911/])
AMBARI-14070 App Timeline Server become stopped by itself (Upgrade from (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8b2853547d53d277bb0a320f74cd99a7dc90ebd])
* ambari-server/src/test/python/stacks/2.1/YARN/test_apptimelineserver.py
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service.py


> App Timeline Server become stopped by itself (Upgrade from 2.1.2 to 2.1.3.0 )
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-14070
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14070
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-upgrade, stacks
>    Affects Versions: 2.1.3
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14070-trunk.patch
>
>
> STR:  (Optional step) mean that step may be not important for reproduce 
> 1)Deploy old version 2.1.2
> 2) Add host, ZK server at added host (Optional step)
> 3)Enable NN, RM HA
> 4)Make Ambari only upgrade to 2.1.3.0
> 5)Check Yarn status after 5 minutes
> Actual results:
> App Timeline Server become stopped by itself
> {code}
> /grid/0/log/hadoop/yarn/yarn-yarn-timelineserver-amb-upg212-rhel7oracle1447032689-3.log
:
> 2015-11-09 16:58:21,519 FATAL applicationhistoryservice.ApplicationHistoryServer (ApplicationHistoryServer.java:launchAppHistoryServer(164))
- Error starting ApplicationHistoryServer
> org.apache.hadoop.service.ServiceStateException: org.fusesource.leveldbjni.internal.NativeDB$DBException:
IO error: lock /grid/0/hadoop/yarn/timeline/leveldb-timeline-store.ldb/LOCK: Resource temporarily
unavailable
>         at org.apache.hadoop.service.ServiceStateException.convert(ServiceStateException.java:59)
>         at org.apache.hadoop.service.AbstractService.init(AbstractService.java:172)
>         at org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
>         at org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:103)
>         at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
>         at org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:161)
>         at org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:171)
> Caused by: org.fusesource.leveldbjni.internal.NativeDB$DBException: IO error: lock /grid/0/hadoop/yarn/timeline/leveldb-timeline-store.ldb/LOCK:
Resource temporarily unavailable
>         at org.fusesource.leveldbjni.internal.NativeDB.checkStatus(NativeDB.java:200)
>         at org.fusesource.leveldbjni.internal.NativeDB.open(NativeDB.java:218)
>         at org.fusesource.leveldbjni.JniDBFactory.open(JniDBFactory.java:168)
>         at org.apache.hadoop.yarn.server.timeline.LeveldbTimelineStore.serviceInit(LeveldbTimelineStore.java:229)
>         at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
>         ... 5 more
> 2015-11-09 16:58:21,521 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - Exiting
with status -1
> {code}



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

Mime
View raw message