[ 
https://issues.apache.org/jira/browse/BEAM-6237?focusedWorklogId=189103&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-189103
 ]

ASF GitHub Bot logged work on BEAM-6237:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Jan/19 18:11
            Start Date: 23/Jan/19 18:11
    Worklog Time Spent: 10m 
      Work Description: swegner commented on issue #7571: [BEAM-6237] Fix ULR 
not deleting artifacts after running jobs.
URL: https://github.com/apache/beam/pull/7571#issuecomment-456907836
 
 
   The java precommit failure is a known issue. I believe this is ok to merge.
 
----------------------------------------------------------------
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: 189103)
    Time Spent: 1h  (was: 50m)

> ULR ValidatesRunner tests not deleting artifacts.
> -------------------------------------------------
>
>                 Key: BEAM-6237
>                 URL: https://issues.apache.org/jira/browse/BEAM-6237
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>            Reporter: Daniel Oliveira
>            Assignee: Daniel Oliveira
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> When running ValidatesRunner tests with the ULR, artifacts are never deleted. 
> Since a new job is run per test, this uses up massive amounts of disk storage 
> quickly (over 20 Gigabytes per execution). This often causes the machine 
> running these tests to run out of disk space which means tests start failing.
> The ULR should be modified to delete these artifacts after they have been 
> staged to avoid this issue. Flink already does this, so the infrastructure 
> exists.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to