Closed
Bug 1152996
Opened 11 years ago
Closed 11 years ago
DEPLOY updated Zenko stack
Categories
(Content Services Graveyard :: Tiles: Ops, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mostlygeek, Assigned: relud)
References
Details
Changes:
- CFN updated from jenkins created to static template+params
- datadog agent deployed on hosts
Deploy:
- This updates the current Zenko CFN stack, not create a new one
- This is not on the critical path for reporting
- Deploy and roll forward to fix any issues
| Reporter | ||
Updated•11 years ago
|
Assignee: nobody → dthornton
| Assignee | ||
Comment 1•11 years ago
|
||
zenko is prepared for prod deployment
| Assignee | ||
Comment 2•11 years ago
|
||
intiating prod deployment
| Assignee | ||
Comment 3•11 years ago
|
||
prod deployment succeeded, but zenko has been taken down to prevent executing a particularly harsh query it attempts to execute on start.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•11 years ago
|
||
Since bug 1154007 went well did we restart Zenko and verified that this is ok?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 5•11 years ago
|
||
zenko has a really bad query: https://github.com/mozilla/zenko/blob/master/zenko/redshift.py#L62-L74
so at the moment I'm leaving zenko off until I can get a dev to say it's okay to either start it or help come up with a better replacement query.
Comment 6•11 years ago
|
||
This query makes a join on impression_stats_daily, which is a table with billions of rows
A join on a table of that size is something one should never do, as it will make the database do a lot of work and will probably timeout
| Reporter | ||
Comment 7•11 years ago
|
||
:oyiptong could you open up a bug to fix the zenko query and make it a dependency for this bug. I don't feel comfortable turning zenko back on if it's just going to degrade redshift again.
Flags: needinfo?(oyiptong)
Updated•11 years ago
|
Flags: needinfo?(oyiptong)
| Assignee | ||
Comment 8•11 years ago
|
||
we're not going to be deploying zenko, because it won't work as of the latest splice deployment, and zenko functionality is being merged into splice.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → WONTFIX
Comment 9•11 years ago
|
||
In fact, zenko did not break. mostlygeek suggested some changes at the last minute for safety and that allows zenko to still function right now
| Assignee | ||
Comment 10•11 years ago
|
||
ah, cool
You need to log in
before you can comment on or make changes to this bug.
Description
•