[jira] [Created] (FLINK-20505) Yarn provided lib does not work with http paths.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-20505) Yarn provided lib does not work with http paths.

Shang Yuanchun (Jira)
Xintong Song created FLINK-20505:
------------------------------------

             Summary: Yarn provided lib does not work with http paths.
                 Key: FLINK-20505
                 URL: https://issues.apache.org/jira/browse/FLINK-20505
             Project: Flink
          Issue Type: Bug
          Components: Deployment / YARN
    Affects Versions: 1.11.2, 1.12.0
            Reporter: Xintong Song
            Assignee: Xintong Song


If an http path is used for provided lib, the following exception will be thrown on the resource manager side:
{code:java}
2020-12-04 17:01:28.955 ERROR org.apache.flink.yarn.YarnResourceManager - Could not start TaskManager in container containerXXXXXX.
org.apache.flink.util.FlinkException: Error to parse YarnLocalResourceDescriptor from YarnLocalResourceDescriptor{key=XXXXX.jar, path=https://XXXXXXX.jar, size=-1, modificationTime=0, visibility=APPLICATION}
    at org.apache.flink.yarn.YarnLocalResourceDescriptor.fromString(YarnLocalResourceDescriptor.java:99)
    at org.apache.flink.yarn.Utils.decodeYarnLocalResourceDescriptorListFromString(Utils.java:721)
    at org.apache.flink.yarn.Utils.createTaskExecutorContext(Utils.java:626)
    at org.apache.flink.yarn.YarnResourceManager.getOrCreateContainerLaunchContext(YarnResourceManager.java:746)
    at org.apache.flink.yarn.YarnResourceManager.createTaskExecutorLaunchContext(YarnResourceManager.java:726)
    at org.apache.flink.yarn.YarnResourceManager.startTaskExecutorInContainer(YarnResourceManager.java:500)
    at org.apache.flink.yarn.YarnResourceManager.onContainersOfResourceAllocated(YarnResourceManager.java:455)
    at org.apache.flink.yarn.YarnResourceManager.lambda$onContainersAllocated$1(YarnResourceManager.java:415)
{code}
The problem is that, `HttpFileSystem#getFilsStatus` returns file status with length `-1`, while `YarnLocalResourceDescriptor` does not recognize the negative file length.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)