[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1822:
----------------------------------
Status: Open (was: Patch Available)
I think this is close, but I don't like the way it is controlled. In particular
the fact that JobClient is clearing the setting is really problematic.
I'd propose that each interface get a different config attribute to set the
socket factory, such as:
"hadoop.rpc.socket.class." + interface.getClassName()
and
"hadoop.rpc.socket.class.default" is the default socket factory.
> 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.
