[
https://issues.apache.org/jira/browse/EAGLE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989047#comment-14989047
]
patrick.h commented on EAGLE-1:
-------------------------------
yes,i had found the error. so i closed this issue with Done on "eagle version
not match the ambari version.",ok? and the eagle with own cluster deploy is ok
and just needs to be done carefully.
> eagle0.1.0 with ambari 2.1.0
> ----------------------------
>
> Key: EAGLE-1
> URL: https://issues.apache.org/jira/browse/EAGLE-1
> Project: Eagle
> Issue Type: Test
> Environment: ambari-server:2.1.0
> hdp:2.3
> eagle:0.1.0
> 4 nodes
> Reporter: patrick.h
> Labels: ambari-server
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> follow the "Install Eagle Ambari Plugin",finished success,but the ambari-web
> cannot loggin ,because the error "the version not match",so i uninstall the
> eagle , but still cannot restart the ambari-server,so i changed the
> /var/lib/ambari-server/resources/version file ,change "2.0.0" to "2.1.0",then
> can restart,but the web also not correct!
> the ambari-server.log:
> 03 Nov 2015 09:52:40,843 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:154
> - Heartbeat lost from host bigdata-206
> 03 Nov 2015 09:52:40,843 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169
> - Setting component state to UNKNOWN for component METRICS_MONITOR on
> bigdata-206
> 03 Nov 2015 09:52:40,844 WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169
> - Setting component state to UNKNOWN for component HBASE_REGIONSERVER on
> bigdata-206
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
