[
https://issues.apache.org/jira/browse/AMBARI-24535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628273#comment-16628273
]
Hudson commented on AMBARI-24535:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10134 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10134/])
AMBARI-24535 : File View not accessible in Ambari 2.7 after enabling 3 (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f26bad435c6b9914e400472ec923e2fddf39ea22])
* (edit)
contrib/views/utils/src/test/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilderTest.java
* (edit)
contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java
* (edit) contrib/views/files/src/main/resources/view.xml
* (edit) contrib/views/wfmanager/src/main/resources/view.xml
> File View not accessible in Ambari 2.7 after enabling 3 namenodes in HDP 3.0
> ----------------------------------------------------------------------------
>
> Key: AMBARI-24535
> URL: https://issues.apache.org/jira/browse/AMBARI-24535
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.7.0
> Reporter: Akhil S Naik
> Assignee: Nitiraj Singh Rathore
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *Ambari-2.7.0* supports HDFS Federation architecture
> But if we configure 3 namenode the Files view never works.
> It will fail with below exception
> {code:java}
> Service 'hdfs' check failed: HDFS080 webhdfs.ha.namenodes.list namenodes
> count is not exactly 2
> Service 'hdfs' check failed:
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS080
> webhdfs.ha.namenodes.list namenodes count is not exactly 2
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.copyHAProperties(ConfigurationBuilder.java:247)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.parseProperties(ConfigurationBuilder.java:110)
>
> at
> org.apache.ambari.view.utils.hdfs.ConfigurationBuilder.buildConfig(ConfigurationBuilder.java:327)
>
> at org.apache.ambari.view.utils.hdfs.HdfsApi.<init>(HdfsApi.java:75)
> at org.apache.ambari.view.utils.hdfs.HdfsUtil.getHdfsApi(HdfsUtil.java:157)
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:145)
>
> at
> org.apache.ambari.view.commons.hdfs.HdfsService.hdfsSmokeTest(HdfsService.java:145)
>
> at
> org.apache.ambari.view.filebrowser.HelpService.hdfsStatus(HelpService.java:95)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>
> {code}
> By inspecting the code , it looks like this is not supposed to work in
> filesview and it wil only allow two namenodes
> code :
> https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L247
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
