[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-------------------------------------
Attachment: 1822_2007-09-29_6.patch
The configuration now follows the suggested scheme:
- {{hadoop.rcp.socket.factory.class.default}} defines the default socket
factory to be used
- this can be overridden for ClientProtocol (DFS RPCs) and for
JobSubmissionProtocol (M/R jobs RPCs)
The patch provides:
- {{org.apache.hadoop.net.StandardSocketFactory}} to create standard (direct)
sockets (we cannot use directly the abstract class {{javax.net.SocketFactory}}).
- {{org.apache.hadoop.net.SocksSocketFactory}} to create sockets which use
SOCKS proxies. The SOCKS server used by the factory is configured by the
{{hadoop.socks.server}} property (format: "host:port").
The map: SocketFactory => Client is required as soon as one needs to mix direct
connections and socksified connections (or different socksified connections)
simultaneously (that's especially true for the eclipse plug-in).
I have been unable to run JUnit tests (HBase tests failed on my machine, even
in the original trunk version).
> 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-22_5.patch, 1822_2007-09-29_6.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.
