[
https://issues.apache.org/jira/browse/BEAM-5495?focusedWorklogId=357239&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-357239
]
ASF GitHub Bot logged work on BEAM-5495:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Dec/19 17:08
Start Date: 10/Dec/19 17:08
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #10268: [BEAM-5495]
PipelineResources algorithm is not working in most environments
URL: https://github.com/apache/beam/pull/10268#issuecomment-564133817
I couldn't reproduce the Jenkins behavior in the dockerized-jenkins clone of
our environment.
Short description of the problem - jenkins does not try to run
validatesRunner task as I specified in the jobDsl definition. It tries to use
an old one - validatesJava11Runner even despite the fact that I retriggered
seed job.
I decided to improve the Java 11 Jenkins jobs in a separate pr in order not
to block the PR.
Created an issue for this: https://issues.apache.org/jira/browse/BEAM-8940
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 357239)
Time Spent: 10h 20m (was: 10h 10m)
> 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
> Time Spent: 10h 20m
> Remaining Estimate: 0h
>
> 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)
