[
https://issues.apache.org/jira/browse/BEAM-5187?focusedWorklogId=139534&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-139534
]
ASF GitHub Bot logged work on BEAM-5187:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Aug/18 05:07
Start Date: 30/Aug/18 05:07
Worklog Time Spent: 10m
Work Description: tweise commented on issue #6287: [BEAM-5187] Add a
ProcessJobBundleFactory for process-based execution
URL: https://github.com/apache/beam/pull/6287#issuecomment-417191289
Something is wrong with the bookkeeping of processes in `ProcessManager`.
If I repeat a pipeline run before the environment was cleaned up (which
would happen after 30s?), the process manager will find that a process with the
id already exists, and fail.
```
Caused by: java.lang.IllegalStateException: There was already a process
running with id 1
at
org.apache.beam.runners.fnexecution.environment.ProcessManager.runCommand(ProcessManager.java:78)
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 139534)
Time Spent: 5h (was: 4h 50m)
> Create a ProcessJobBundleFactory for non-dockerized SDK harness
> ---------------------------------------------------------------
>
> Key: BEAM-5187
> URL: https://issues.apache.org/jira/browse/BEAM-5187
> Project: Beam
> Issue Type: New Feature
> Components: runner-core
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Time Spent: 5h
> Remaining Estimate: 0h
>
> As discussed on the mailing list [1], we want to giver users an option to
> execute portable pipelines without Docker. Analog to the
> {{DockerJobBundleFactory}}, a {{ProcessJobBundleFactory}} could be added to
> directly fork SDK harness processes.
> Artifacts will be provided by an artifact directory or could be setup similar
> to the existing bootstrapping code ("boot.go") which we use for containers.
> The process-based execution can optionally be configured via the pipeline
> options.
> [1]
> [https://lists.apache.org/thread.html/d8b81e9f74f77d74c8b883cda80fa48efdcaf6ac2ad313c4fe68795a@%3Cdev.beam.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
