[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529138
]
Owen O'Malley commented on HADOOP-1822:
---------------------------------------
Sorry for confusing the issue. *grin*
My original point was that all of the rpc protocol interfaces (eg.
DFSClientProtocol, JobSubmissionProtocol, etc.) may not want the same proxy.
However, on more thought I don't think that is likely.
I would rather have a richer hook into the rpcs and provide:
rpc.client.socket.factory.class
-> empty or undefined means direct or org.apache.hadoop.net.ProxySocketFactory
and the proxy socket factory is configured via:
rpc.proxy.server
-> the host:port of the socks server.
Does that make sense?
> Allow SOCKS proxy configuration to remotely access the DFS and submit Jobs
> --------------------------------------------------------------------------
>
> Key: HADOOP-1822
> URL: https://issues.apache.org/jira/browse/HADOOP-1822
> Project: Hadoop
> Issue Type: New Feature
> Components: dfs, ipc
> Reporter: Christophe Taton
> Assignee: Christophe Taton
> Priority: Minor
> Fix For: 0.15.0
>
> Attachments: 1822-2007-09-07a.patch, 1822-2007-09-11a.patch
>
>
> The purpose of this issue is to introduce a new configuration entry to setup
> SOCKS proxy for DFS and JobTracker clients.
> This enable users to remotely access the DFS and submit Jobs as if they were
> directly connected to the cluster Hadoop runs on.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
