[SAMZA-2774] Fix incorrect symlinks used to generate classpath in run-class.sh

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Jon Bringhurst
• Reporter: Jon Bringhurst
• Created: 31/Jan/23 19:03
• Updated: 04/Sep/24 18:16
• Resolved: 04/Sep/24 18:16

Description

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.

[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]$

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.