[
https://issues.apache.org/jira/browse/HADOOP-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhiyong zhang updated HADOOP-5363:
----------------------------------
Attachment: HADOOP-5363.patch
---++ General Design Idea.
* 1. Use forward servlet to forward requests to the right hadoop version
servlet.
* 2. Package each version's servlet into a separate war file.
* 3. Communication between forwarding war and hadoop-specific version war
only pass build-in type to avoid class loading issue.
* 4. Use a configuration file (hdfsproxy-site.xml) to identify the war file
path. Format example (suppose www.apache1.com and www.apache2.com point to the
same ip address through some dns configuration)
<property>
<name>www.apache1.com</name>
<value>/v18</value>
<description>one hostname corresponds to one web application archive
</description>
</property>
<property>
<name>www.apache2.com</name>
<value>/v21</value>
<description>one hostname corresponds to one web application archive
</description>
</property>
* 5. each war file package one proxy, which corresponds to one source
cluster. even same hadoop version can use different war file to point to
different source cluster. i.e. the war file are source-cluster oriented, but
not hadoop version oriented.
* 6. tomcat need to set crossContext="true" in context.xml config file to
allow cross war forwarding.
> Proxying for multiple HDFS clusters of different versions
> ---------------------------------------------------------
>
> Key: HADOOP-5363
> URL: https://issues.apache.org/jira/browse/HADOOP-5363
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/hdfsproxy
> Reporter: Kan Zhang
> Assignee: zhiyong zhang
> Attachments: HADOOP-5363.patch
>
>
> A single hdfsproxy server should be able to proxy for multiple HDFS clusters,
> whose Hadoop versions may be different from each other.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
