cxzl25 opened a new pull request, #3309:
URL: https://github.com/apache/celeborn/pull/3309

   ### What changes were proposed in this pull request?
   
   
   
   ### Why are the changes needed?
   Spark4 uses scala 2.13, but it cannot be connected to the celeborn master 
compiled with scala 2.12.
   
   For example, the first node of `celeborn.master.endpoints` configured by 
client is not a leader, and RpcFailure will be returned at this time.
   
   ```java
   java.io.InvalidClassException: 
org.apache.celeborn.common.rpc.netty.RpcFailure; local class incompatible: 
stream classdesc serialVersionUID = 2793139166962436434, local class 
serialVersionUID = -1724324816907181707
        at 
java.base/java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:598) 
~[?:?]
   ```
   
   ```bash
   scala  -cp /tmp/celeborn-client-spark-3-shaded_2.12-0.5.4.jar
   ```
   
   ```scala
   
   :paste -raw
   
     package org.apache.celeborn {
       class Y {
           def printId = {
               val clazz = 
classOf[org.apache.celeborn.common.rpc.netty.RpcFailure]
               val uid = 
java.io.ObjectStreamClass.lookup(clazz).getSerialVersionUID
               println(s"Scala version: 
${scala.util.Properties.versionNumberString}")
               println(s"serialVersionUID: $uid")
         }
       }
     }
   
   new org.apache.celeborn.Y().printId
   ```
   
   2.11
   ```
   Scala version: 2.11.12
   serialVersionUID: 2793139166962436434
   ```
   2.12
   ```
   Scala version: 2.12.19
   serialVersionUID: 2793139166962436434
   ```
   2.13
   ```
   Scala version: 2.13.16
   serialVersionUID: -1724324816907181707
   ```
   
   
   
   
   ### Does this PR introduce _any_ user-facing change?
   If we use 2.13 compiled master, it may be incompatible.
   
   ### How was this patch tested?
   local test
   


-- 
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]

Reply via email to