[
https://issues.apache.org/jira/browse/MAPREDUCE-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated MAPREDUCE-6387:
-----------------------------------
Attachment: MAPREDUCE-6387.1.patch
Attaching trivial patch to fix this.
Not adding test-cases since it is just reordering of a few fields
> Fix Task object to allow Jobs not submitted via distributed cache to survive
> rolling upgrade
> --------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6387
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6387
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Priority: Minor
> Attachments: MAPREDUCE-6387.1.patch
>
>
> There was a recent addition of an {{encryptedSpillKey}} to the Task object.
> And when serialized, this field was written out somewhere in the middle. This
> caused deployments that do not use DistributedCache to push job jars before
> running the job to fail rolling upgrade.
> Although deploying via Distributed Cache is the recommended method, there
> might still be deployments that use the node local classpath to pick up the
> MR framework classes (eg. for efficiency purposes, since this does not
> require the jar being copied to hdfs and then to all the nodes)
> Ensuring that it is the last field written and read when the Task object is
> serialized would alleviate this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
