[ 
https://issues.apache.org/jira/browse/HADOOP-15980?focusedWorklogId=734343&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-734343
 ]

ASF GitHub Bot logged work on HADOOP-15980:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Mar/22 04:24
            Start Date: 01/Mar/22 04:24
    Worklog Time Spent: 10m 
      Work Description: vnhive commented on pull request #3966:
URL: https://github.com/apache/hadoop/pull/3966#issuecomment-1055000899


   @jojochuang Thank you very much for your earlier comments. I am working on 
the refactoring the test code. If you had more comments on the changes in 
Server.java and Client.java, can you please post them ? I will go ahead and 
submit these along with the next cut ?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 734343)
    Time Spent: 3h 40m  (was: 3.5h)

> Enable TLS in RPC client/server
> -------------------------------
>
>                 Key: HADOOP-15980
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15980
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc, security
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> Once the RPC client and server can be configured to use Netty, the TLS engine 
> can be added to the channel pipeline.  The server should allow QoS-like 
> functionality to determine if TLS is mandatory or optional for a client.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to