You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Benjamin Teke (Jira)" <ji...@apache.org> on 2022/02/11 14:21:00 UTC

[jira] [Created] (YARN-11075) Explicitly declare serialVersionUID in LogMutation class

Benjamin Teke created YARN-11075:
------------------------------------

             Summary: Explicitly declare serialVersionUID in LogMutation class
                 Key: YARN-11075
                 URL: https://issues.apache.org/jira/browse/YARN-11075
             Project: Hadoop YARN
          Issue Type: Bug
    Affects Versions: 3.3.1
            Reporter: Benjamin Teke
            Assignee: Benjamin Teke


The [LogMutation|https://github.com/apache/hadoop/blob/f91e21ac109e753e76d19c5c872c59a767b7b837/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/conf/YarnConfigurationStore.java#L55] class doesn't have its serialVersionUID defined as a private final static constant hence the compiler generates one for it. Upon every [logMutation|https://github.com/apache/hadoop/blob/d336227e5c63a70db06ac26697994c96ed89d230/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/conf/ZKConfigurationStore.java#L163] call the existing logMutation objects are collected from chosen config store and deserialised, but if a new/different RM jar loads these and the serialVersionUIDs don't match (because for example a different compiler generated a different ID) an InvalidClassException occurs.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org