You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/10/08 16:27:26 UTC

[jira] [Commented] (AMBARI-13345) Views: HDFS API utility needs to work with WASB

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

Hadoop QA commented on AMBARI-13345:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12765580/AMBARI-13345_branch-2.1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in contrib/views/hive contrib/views/utils:

                  org.apache.ambari.view.hive.resources.jobs.JobLDAPServiceTest
                  org.apache.ambari.view.hive.client.ConnectionTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3929//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3929//console

This message is automatically generated.

> Views: HDFS API utility needs to work with WASB
> -----------------------------------------------
>
>                 Key: AMBARI-13345
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13345
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.1.0, 2.1.1, 2.1.2
>            Reporter: Rohit Choudhary
>             Fix For: 2.1.0, 2.1.1, 2.1.2
>
>         Attachments: AMBARI-13345_branch-2.1.patch
>
>
> We have a cluster that has HDFS configured for WASB. The Files View fails to load with the error below. This is the HDFS config...
> fs.defaultFS = wasb://cloudbreak@operations8738sa.blob.core.windows.net
> In an attempt to get this working, I placed hadoop-azure-2.7.1.jar in here and restarted Ambari Server.
> /var/lib/ambari-server/resources/views/work/FILES{1.0.0}/WEB-INF/lib
> But the view still continued to fail to load. This is from ambari-server.log when I try to access the view:
> 25 Sep 2015 15:48:39,450  INFO [qtp-client-20] ConfigurationBuilder:101 - HdfsApi configured to connect to defaultFS='wasb://cloudbreak@operations8738sa.blob.core.windows.net:50070'
> 25 Sep 2015 15:48:39,584  WARN [qtp-client-20] NativeCodeLoader:62 - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
> 25 Sep 2015 15:48:39,615 ERROR [qtp-client-20] HdfsUtil:130 - HDFS040 Couldn't open connection to HDFS
> This is the exception shown in the UI when trying to access the view.
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS040 Couldn't open connection to HDFS
> 	at org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:131)
> 	at org.apache.ambari.view.filebrowser.HdfsService.getApi(HdfsService.java:79)
> 	at org.apache.ambari.view.filebrowser.FileOperationService.listdir(FileOperationService.java:64)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)



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