Closed
Bug 1259547
Opened 9 years ago
Closed 8 years ago
Opsify deployment of presto-hyperloglog on Presto cluster
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
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
Reporter | ||
Updated•9 years ago
|
Points: --- → 1
Priority: -- → P1
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(whd)
Updated•9 years ago
|
Priority: P1 → P2
Updated•9 years ago
|
Whiteboard: [SvcOps]
Reporter | ||
Updated•8 years ago
|
Priority: P2 → P1
Updated•8 years ago
|
Assignee: nobody → whd
Updated•8 years ago
|
Assignee: whd → bimsland
Flags: needinfo?(whd)
Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•