[
https://issues.apache.org/jira/browse/HADOOP-15980?focusedWorklogId=732113&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-732113
]
ASF GitHub Bot logged work on HADOOP-15980:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Feb/22 03:26
Start Date: 24/Feb/22 03:26
Worklog Time Spent: 10m
Work Description: vnhive commented on a change in pull request #3966:
URL: https://github.com/apache/hadoop/pull/3966#discussion_r813516566
##########
File path:
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestNettyRPC.java
##########
@@ -0,0 +1,1742 @@
+/**
Review comment:
You are correct, this is TestRPC with netty turned on. I noticed that
parameterizing the unit tests and running both nettya and non-netty was causing
a lot of test failures. These failures just went away when we separated the
netty and non-netty tests.
I thought as a first step I will just duplicate the test in a separate file
and check whether things pass. This seems to work. A lot of the failures have
gone away.
In my next PR, I will eliminate the redundancy.
Sorry for the inconvenience. But please rest assure that the test code will
pretty much remain the same.
--
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: 732113)
Time Spent: 3h 10m (was: 3h)
> 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 10m
> 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]
