1289169 - Reaper should spare Spark & Presto instances

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

Comment 1

[Roberto Agostino Vitillo (:rvitillo)]

Reaper is going to stop and terminate forgotten and unowned instances in the cloudservices-aws-dev (Dev) IAM beginning August 1st.

Comment 2

[Blake Imsland [:robotblake]]

This is now fixed for the existing presto clusters (though should have something added to emr-bootstrap-presto). I'm not sure the impact against the spark clusters as they shouldn't normally be long-lived enough to even be affected by this. We should make sure that the Owner tag gets set when spinning up new clusters both in documentation for manual creation as well as in ATMO.

Any thoughts on any of that?

Comment 3

[Roberto Agostino Vitillo (:rvitillo)]

(In reply to Blake Imsland [:robotblake] from comment #2)
> This is now fixed for the existing presto clusters (though should have
> something added to emr-bootstrap-presto). I'm not sure the impact against
> the spark clusters as they shouldn't normally be long-lived enough to even
> be affected by this. We should make sure that the Owner tag gets set when
> spinning up new clusters both in documentation for manual creation as well
> as in ATMO.
> 
> Any thoughts on any of that?

Please send a PR for emr-bootstrap-spark and emr-bootstrap-presto with the required changes. You can find the repository for ATMO at [1]; it seems that Spark clusters have already an Owner tag though.

[1] https://github.com/mozilla/telemetry-server/tree/master/http/analysis-service

Comment 4

[Blake Imsland [:robotblake]]

Attachment: add-reaper-tag

Comment 5

[Roberto Agostino Vitillo (:rvitillo)]

Comment on attachment 8783617 [details] [review]
add-reaper-tag

This has a landed a while ago.