[
https://issues.apache.org/jira/browse/HADOOP-15980?focusedWorklogId=728016&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728016
]
ASF GitHub Bot logged work on HADOOP-15980:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/22 02:53
Start Date: 16/Feb/22 02:53
Worklog Time Spent: 10m
Work Description: vnhive commented on a change in pull request #3966:
URL: https://github.com/apache/hadoop/pull/3966#discussion_r807491809
##########
File path:
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/CommonConfigurationKeys.java
##########
@@ -59,6 +59,16 @@
"ipc.client.rpc-timeout.ms";
/** Default value for IPC_CLIENT_RPC_TIMEOUT_KEY. */
public static final int IPC_CLIENT_RPC_TIMEOUT_DEFAULT = 120000;
+ /** Enable the experimental use of netty instead of nio. */
+ public static final String IPC_SERVER_NETTY_ENABLE_KEY =
Review comment:
I guess by backward compatible what is meant is,
The Server checks if the incoming request is SSL enabled, if yes, it
continues with SSL otherwise it resorts to non-SSL based communication.
If you meant the above, yes the goal is to eventually support the above
behaviour. I guess this what Daryn meant in his original comment on supporting
a QoS like functionality.
But in the first version I plan to get SSL working and reject a
communication from a client that is not SSL enabled.
I will definitely change the patch to be backward compatible in a later
revision.
--
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: 728016)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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]
