[
https://issues.apache.org/jira/browse/YARN-11075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494149#comment-17494149
]
Szilard Nemeth commented on YARN-11075:
---------------------------------------
Hi [~bteke],
Could you please verify if we need backport to older branches (3.3, 3.2, 3.1)?
Thanks.
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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 the chosen config
> store and deserialized, but if a new/different RM jar loads these and the
> serialVersionUIDs don't match (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: [email protected]
For additional commands, e-mail: [email protected]
