[jira] [Commented] (BEAM-12903) Implement a solution to cleanup GCP resources in beam testing projects

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443978#comment-17443978 ] 

Beam JIRA Bot commented on BEAM-12903:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Implement a solution to cleanup GCP resources in beam testing projects
> ----------------------------------------------------------------------
>
>                 Key: BEAM-12903
>                 URL: https://issues.apache.org/jira/browse/BEAM-12903
>             Project: Beam
>          Issue Type: Test
>          Components: testing
>            Reporter: Alex Amato
>            Priority: P2
>              Labels: stale-P2
>
> FR to create a solution to clean up lingering GCE, VMs, Dataproc clusters, etc.
> Some sort of perodic job which runs and deletes leaked GCE VMs would prevent the resource concerns caused by failed tests as in: 
> https://issues.apache.org/jira/browse/BEAM-12898?filter=-2 
> Possible solutions:
>  * Name all the resources with a convention that represents a TTL. Then the resources can be deleted by a cron/periodic job if the TTL has expired
>  * Dataproc cluster may have a TTL configuration option itself which the flink on dataproc test can use.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)