You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Michael Taylor (Jira)" <ji...@apache.org> on 2021/09/30 17:21:00 UTC
[jira] [Created] (HADOOP-17948) JAR in conflict with timestamp
check causes AM errors
Michael Taylor created HADOOP-17948:
---------------------------------------
Summary: JAR in conflict with timestamp check causes AM errors
Key: HADOOP-17948
URL: https://issues.apache.org/jira/browse/HADOOP-17948
Project: Hadoop Common
Issue Type: Bug
Components: common
Affects Versions: 2.9.2
Reporter: Michael Taylor
After an init action pulls down a new JAR and the check of a JAR's timestamp is performed [1]we can sometimes cause an incorrect error if the timestamp does not match. In order to address this you can perform workarounds like:
record old timestamp at the beginning before the connector is changed
local -r old_file_time=$(date -r ${dataproc_common_lib_dir}/gcs-connector.jar "+%m%d%H%M.00")
# at end of script.
touch -t "${old_file_time}" <any jar they changed>
touch -h -t "${old_file_time}" <symlinks they changed>
We should instead of checking the date be comparing version compatibility tests.
1. https://github.com/apache/hadoop/blob/release-2.7.3-RC2/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/FSDownload.java#L255-L258
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org