hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3893) QJM: Make QJM work with security enabled
Date Wed, 05 Sep 2012 22:52:07 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron T. Myers updated HDFS-3893:
---------------------------------

    Attachment: HDFS-3893.patch

Here's a patch which addresses the issue. The gist is simply that we had the wrong principals
configured in a few places, and in a few other places we were making RPCs or authenticated
HTTP requests without providing any credentials.

No tests are included since security must be enabled to test this. I tested this manually
by ensuring that all of the following works when security is enabled with the patch, but not
without:

# Formatting an NN which is using the QJM.
# An NN is able to fetch edits files from the JNs.
# When the JNs get out of sync, the JNs are able to fetch edits from each other during recovery.
# The standby NN is able to fetch edits from the JNs.

Additionally, I also ran all of the existing QJM tests with this patch applied, and confirmed
that they all passed.
                
> QJM: Make QJM work with security enabled
> ----------------------------------------
>
>                 Key: HDFS-3893
>                 URL: https://issues.apache.org/jira/browse/HDFS-3893
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node, security
>    Affects Versions: QuorumJournalManager (HDFS-3077)
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-3893.patch
>
>
> Currently the QJM does not work when security is enabled. The quorum cannot be formatted,
the NN and SBN cannot communicate with the JNs, and JNs cannot synchronize edit logs with
each other.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message