HADOOP-19864. Cut WritableRPCEngine#8433
Conversation
RpcWritable still exists, and ClientCache uses it, but those are vestigal uses. Contains content generated by GitHub Copilot
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
shaded build failing was vm oom. I'm going to do a slightly modified PR which touches hdfs, mr and yarn out of diligence |
| // note anything marked public is solely for access by SaslRpcClient | ||
| /** | ||
| * Marshalling support, for hadoop shaded protobuf and legacy | ||
| * protobuf 2.5. |
There was a problem hiding this comment.
do you have a plan to cut protobuf 2.5 thoroughly?
protobuf 3-based ProtobufRpcEngine2 has been introduced in HADOOP-17046 (3.3.0, 6 years ago), also Hadoop 3.2 has reached EOL, I think we have already given downstream projects enough time to allow them to migrate from protobuf 2.5 to hadoop shaded protobuf 3.x seamlessly
There was a problem hiding this comment.
good point. the issue was always hbase 1. now we are cleaning up, getting rid of obsolete rpc stuff is good. someone should ping hbase dev list though.
There was a problem hiding this comment.
https://issues.apache.org/jira/browse/HBASE-27286
The 1.x release are now fully EOLed.
|
failures are legitimate org.apache.hadoop.hdfs.security.token.block.TestBlockToken.testBlockTokenRpcLeakLegacy org.apache.hadoop.hdfs.security.token.block.TestBlockToken.testBlockTokenRpcLeakProtobuf final failure less obvious But if heartbeats were failing, that could be the trigger. |
Description of PR
Purge WritableRPCEngine from the code.
There's hints of its existence in the code (RpcWritable and ClientCache), but its not an RPC mechanism any more.
How was this patch tested?
tests of immediate methods; remaining homework is left to yetus
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?AI Tooling
If an AI tool was used:
where is the name of the AI tool used.
https://www.apache.org/legal/generative-tooling.html