beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4778) Less wasteful ArtifactStagingService
Date Thu, 02 Aug 2018 04:27:00 GMT


ASF GitHub Bot logged work on BEAM-4778:

                Author: ASF GitHub Bot
            Created on: 02/Aug/18 04:26
            Start Date: 02/Aug/18 04:26
    Worklog Time Spent: 10m 
      Work Description: ryan-williams commented on a change in pull request #5958: [BEAM-4778]
add option to flink job server to clean staged artifacts per-job

 File path: runners/java-fn-execution/src/main/java/org/apache/beam/runners/fnexecution/artifact/
 @@ -329,6 +335,29 @@ private void setBasePath(String basePath) {
       this.basePath = basePath;
+    public String encode() throws Exception {
+      try {
+        return MAPPER.writeValueAsString(this);
+      } catch (JsonProcessingException e) {
+        LOG.error("Error {} occurred while serializing {}.", e.getMessage(), this);
 Review comment:
   good catch, done

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:

Issue Time Tracking

    Worklog Id:     (was: 130099)
    Time Spent: 5h 50m  (was: 5h 40m)

> Less wasteful ArtifactStagingService
> ------------------------------------
>                 Key: BEAM-4778
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Eugene Kirpichov
>            Assignee: Ryan Williams
>            Priority: Major
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
> [] is
the main implementation of ArtifactStagingService.
> It stages artifacts into a directory; and in practice the passed staging session token
is such that the directory is different for every job. This leads to 2 issues:
>  * It doesn't get cleaned up when the job finishes or even when the JobService shuts
down, so we have disk space leaks if running a lot of jobs (e.g. a suite of ValidatesRunner
>  * We repeatedly re-stage the same artifacts. Instead, ideally, we should identify that
some artifacts don't need to be staged - based on knowing their md5. The artifact staging
protocol has rudimentary support for this but may need to be modified.
> CC: [~angoenka]

This message was sent by Atlassian JIRA

View raw message