[
https://issues.apache.org/jira/browse/KNOX-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504019#comment-16504019
]
Mert Hocanin commented on KNOX-1334:
------------------------------------
I have been working on enhancing Knox's service rules to better support EMR's
topology. Some of the issues that I have faced is that the current rewrite
rules were not properly redirecting requests to slave nodes in an EMR cluster.
I will provide a github link or patch which seems to solve a lot of the issues,
although I still need to test against the quick start environment to make sure
that I didn't break anything.
The changes were taken from KNOX-1270 and KNOX-1023 as they have not been
committed yet, and then enhanced.
> Knox on AWS EMR
> ---------------
>
> Key: KNOX-1334
> URL: https://issues.apache.org/jira/browse/KNOX-1334
> Project: Apache Knox
> Issue Type: Bug
> Reporter: PRAVEEN K RAVIKUMAR
> Priority: Major
>
> Hi
> I have requirement to send all the request coming to proxy to be forwarded to
> EMR master node.
> Example:
> https://<any dns-name>:<PORT>/ --> Proxy --> EMR master.
> The DNS name could be anything, because there are many slave nodes. I would
> like the proxy to "redirect" dynamically "https://<any dns-name>:<PORT>/" to
> EMR master host. Could you please let me know if a reverse proxy/ Apache Knox
> can do that. I am trying to mimic option2 "SSH Tunnel to the Master Node
> Using Dynamic Port Forwarding"
> https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-ssh-tunnel.html
> Sample URLS:
> YARN ResourceManager https://master-public-dns-name:8088/ YARN NodeManager
> https://slave-public-dns-name:8042/ Spark HistoryServer
> https://master-public-dns-name:18080/
> [https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-ssh-tunnel.html]
>
> If so could you please share me the steps to configure Knox on EMR cluster-
> would be very helpful?
> Praveen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
