ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-149) If the HDFS file system is empty then repository configurator gives confusing message
Date Tue, 15 Mar 2016 16:09:33 GMT

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

Madhan Neethiraj commented on RANGER-149:
-----------------------------------------

[~rmani] Please review and update the message returned during HDFS 'Test Connection'.

> If the HDFS file system is empty then repository configurator gives confusing message
> -------------------------------------------------------------------------------------
>
>                 Key: RANGER-149
>                 URL: https://issues.apache.org/jira/browse/RANGER-149
>             Project: Ranger
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Alok Lal
>            Assignee: Ramesh Mani
>            Priority: Trivial
>
> test of correct hdfs repo relies on non-null file listing.  If one tries to configure
an empty repository then one gets the following message:
> {code}
> Connection Failed.
> Unable to retrieve any files using given parameters, You can still save the repository
and start creating policies, but you would not be able to use autocomplete for resource names.
Check xa_portal.log for more info.
> Unable to retrieve any files using given parameters, You can still save the repository
and start creating policies, but you would not be able to use autocomplete for resource names.
Check xa_portal.log for more info.
> {code}
> The message is factually correct.  It would be helpful if it said something to the effect:
unable to retrieve any files.  Either the file system is currently empty or connection wasn't
successful.
> While it asks one to look at xa_portal.log in this case the log does not have any helpful
information because connection in fact was successful.
> h4. Steps to reproduce
> - format the namenode: {{bin/hdfs namenode -format}}
> - confirm that fs is empty {{bin/hdfs dfs -ls -R /}}
> - go to admin portal and test the connection.  You will get the above error.  Check in
the xa_portal.log to confirm that there wasn't any connection error or exceptions.
> - Now go an create a single file {{bin/hdfs dfs -touchz /test}}
> - go back to admin portal and test the connection.  Test would succeed this time.



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

Mime
View raw message