question How Apache Knox gets integrated with data encryption on RPC protocols in hadoop cluster? in Archives of Support Questions (Read Only)

How Apache Knox gets integrated with data encryption on RPC protocols in hadoop cluster?

nhgodwal — Fri, 06 Oct 2017 23:59:35 GMT

Re: How Apache Knox gets integrated with data encryption on RPC protocols in hadoop cluster?

lmccay — Sat, 07 Oct 2017 01:59:55 GMT

Apache Knox is an HTTP Gateway - it doesn't proxy RPC calls to platform components. I will proxy REST API calls for many of the same components and provide you access to resources that you otherwise couldn't due to authentication requirements, etc.

I assume by data encryption in this context you mean on the wire. Wire level encryption for Knox interactions is based on TLS/SSL.

Re: How Apache Knox gets integrated with data encryption on RPC protocols in hadoop cluster?

nhgodwal — Mon, 09 Oct 2017 22:28:14 GMT

Thanks @Imccay! I have a follow question, why rpc address is mentioned for Jobtracker in the Apache Knox user's guide? Can you please help me understand how this service gets routed?

<service>
        <role>JOBTRACKER</role>
        <url>rpc://localhost:8050</url>
    </service>

Re: How Apache Knox gets integrated with data encryption on RPC protocols in hadoop cluster?

lmccay — Mon, 09 Oct 2017 22:32:02 GMT

The JOBTRACKER and NAMENODE services are a bit odd at first glance. Don't confuse their use with proxying of RPC services. These are used in order to realize the rewrite requirements for Oozie. Oozie responses include some host and port information that we need to be able to identify internally through the ServiceRegistryService gateway service.