You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Lukasz Gajowy (Jira)" <ji...@apache.org> on 2019/11/08 17:49:00 UTC
[jira] [Commented] (BEAM-5495) PipelineResources algorithm is not
working in most environments
[ https://issues.apache.org/jira/browse/BEAM-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970485#comment-16970485 ]
Lukasz Gajowy commented on BEAM-5495:
-------------------------------------
I'd like to push things forward here so I assigned myself. I'm looking into both solutions now and trying to determine what is best for the project. I will also revieve this thread on the devlist for all devs: [https://lists.apache.org/thread.html/61ae8750b4ed20413c6e93ba949ddd48dd0107a0a039ef518f9d6d21@%3Cdev.beam.apache.org%3E]
> PipelineResources algorithm is not working in most environments
> ---------------------------------------------------------------
>
> Key: BEAM-5495
> URL: https://issues.apache.org/jira/browse/BEAM-5495
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, runner-spark, sdk-java-core
> Reporter: Romain Manni-Bucau
> Assignee: Lukasz Gajowy
> Priority: Major
>
> Issue are:
> 1. it assumes the classloader is an URLClassLoader (not always true and java >= 9 breaks that as well for the app loader)
> 2. it uses loader.getURLs() which leads to including the JRE itself in the staged file
> Looks like this detect resource algorithm can't work and should be replaced by a SPI rather than a built-in and not extensible algorithm. Another valid alternative is to just drop that "guess" logic and force the user to set staged files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)