[
https://issues.apache.org/jira/browse/SAMZA-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Bringhurst resolved SAMZA-2774.
-----------------------------------
Resolution: Fixed
See https://github.com/apache/samza/pull/1653
> Fix incorrect symlinks used to generate classpath in run-class.sh
> -----------------------------------------------------------------
>
> Key: SAMZA-2774
> URL: https://issues.apache.org/jira/browse/SAMZA-2774
> Project: Samza
> Issue Type: Improvement
> Reporter: Jon Bringhurst
> Assignee: Jon Bringhurst
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Manifest generation (application-level) is pointing to container-level
> symlinks instead of application-level files.
> This will cause issues when multiple containers for an application land on a
> single host and the container the manifest is pointing to gets cleaned up.
> {noformat}
> [yyy@zzz filecache]$ cat
> /export/content/data/samsa-yarn/usercache/vapp5251/appcache/application_1668550466222_0989/filecache/10/xxx-0.0.672.tgz/classpath_workspace/manifest.txt|tail
> -n 2
>
> /export/content/data/samsa-yarn/usercache/yyy/appcache/application_1668550466222_0989/container_e114_1668550466222_0989_01_000003/__package/lib/zstd-jni-1.5.2-3.jar
> [yyy@zzz filecache]$
> {noformat}
> Something like "realpath" (but not realpath, since it doesn't work with osx)
> should be used in "run-class.sh" to resolve the container-level symlinks to
> application-level files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
