Closed Bug 1259547 Opened 8 years ago Closed 8 years ago

Opsify deployment of presto-hyperloglog on Presto cluster

Categories

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

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rvitillo, Assigned: robotblake)

References

Details

(Whiteboard: [SvcOps]) 

The plugin has to be deployed on all nodes of the cluster from emr-bootstrap-presto, see [1] on how to deploy it.

There should also be a standard way to upload a new version of a plugin (and possibly others, see Bug 1259452) or treat the cluster configuration as immutable and redeploy it when something changes.

https://github.com/vitillo/presto-hyperloglog#deployment-on-aws-emr
Points: --- → 1
Priority: -- → P1
Flags: needinfo?(whd)
Priority: P1 → P2
Whiteboard: [SvcOps]
Priority: P2 → P1
Assignee: nobody → whd
Assignee: whd → bimsland
Flags: needinfo?(whd)
Blocks: 1270257
No longer blocks: 1270257
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.