You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Takanobu Asanuma (JIRA)" <ji...@apache.org> on 2018/01/30 06:51:00 UTC

[jira] [Commented] (HDFS-12564) Add the documents of swebhdfs configurations on the client side

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

Takanobu Asanuma commented on HDFS-12564:
-----------------------------------------

Hi, [~xyao]. I'm sorry for very late response. Thanks for your review and comments. I uploaded a new patch based on your advice.

> Line 423: suggest adding a separate section and put the content(links) under it.
 Done in the latest patch.

> This page is for HTTPFS. To avoid confusion, I would suggest we add a detailed ssl-client.xml example instead of linking it to 
 > Swebhdfs document.

Since HttpFS provides WebHDFS interface, the clients of HttpFS follow WebHDFS REST API. It is not different between "HttpFS over SSL" and "WebHDFS over SSL" from the perspective of the clients. It might be a little redundant to add the same {{ssl-client.xml}} example. The latest patch still uses the link but also adds more sentence to avoid confusion. How does look that?

> Line 161: /etc/hadoop/hdfs-site.xml has a configuration key to enable secure http, 
 > i.e., dfs.http.policy=HTTPS_ONLY
 > Also note that dfs.http.policy is not for swebhdfs only. This will also affect all the HTTP endpoints of HDFS such as the NN, DN WebUI, JMX, QJM.
 > We also need to document settings for the server side settings, e.g., ssl-server.xml.

{{dfs.http.policy=HTTPS_ONLY}} and {{ssl-server.xml}} are on the server side settings and clients don't use it. Since {{Webhdfs.md}}(WebHDFS REST API) is focusing on the client side, I think we should not write it in {{Webhdfs.md}}.

I agree to adding the documents for the server side settings. That seems to be missing from the current community documents. How about doing it in HDFS-12736?

> Line 198: suggest give a full path: ssl-client.xml -> /etc/hadoop/ssl-client.xml

I tried some experiments and it seems that {{hadoop.ssl.client.conf}} reqires only relative path, not absolute path. So {{hadoop.ssl.client.conf=/etc/hadoop/ssl-client.xml}} doesn't work well. The latest patch includes the explanation.

> Add the documents of swebhdfs configurations on the client side
> ---------------------------------------------------------------
>
>                 Key: HDFS-12564
>                 URL: https://issues.apache.org/jira/browse/HDFS-12564
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation, webhdfs
>            Reporter: Takanobu Asanuma
>            Assignee: Takanobu Asanuma
>            Priority: Major
>         Attachments: HDFS-12564.1.patch, HDFS-12564.2.patch, HDFS-12564.3.patch
>
>
> Documentation does not cover the swebhdfs configurations on the client side. We can reuse the hftp/hsftp documents which was removed from Hadoop-3.0 in HDFS-5570, HDFS-9640.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org