[ 
https://issues.apache.org/jira/browse/HADOOP-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471697#comment-15471697
 ] 

Kai Zheng commented on HADOOP-13218:
------------------------------------

Sorry for the inconvenience. I'll fire a new JIRA and sort out a fix soon.

The cause should that the default engine should remain as the old one, before 
MAPREDUCE-6706 is solved. The fix should be simple in YARN/MapReduce side so 
necessary test cases are involved and triggered.
{code}
@@ -207,7 +208,7 @@ static synchronized RpcEngine getProtocolEngine(Class<?> 
protocol,
     RpcEngine engine = PROTOCOL_ENGINES.get(protocol);
     if (engine == null) {
       Class<?> impl = conf.getClass(ENGINE_PROP+"."+protocol.getName(),
-                                    WritableRpcEngine.class);
+                                    ProtobufRpcEngine.class);
       engine = (RpcEngine)ReflectionUtils.newInstance(impl, conf);
       PROTOCOL_ENGINES.put(protocol, engine);
     }
{code}

> Migrate other Hadoop side tests to prepare for removing WritableRPCEngine
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-13218
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13218
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Kai Zheng
>            Assignee: Wei Zhou
>             Fix For: 3.0.0-alpha2
>
>         Attachments: HADOOP-13218-v01.patch, HADOOP-13218-v02.patch
>
>
> Patch for HADOOP-12579 contains lots of work to migrate the left Hadoop side 
> tests basing on the new RPC engine and nice cleanups. HADOOP-12579 will be 
> reverted to allow some time for YARN/Mapreduce side related changes, open 
> this to recommit most of the test related work in HADOOP-12579 for easier 
> tracking and maintain, as other sub-tasks did.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to