Closed
Bug 1460925
Opened 7 years ago
Closed 7 years ago
Mission Control v2 deployment
Categories
(Data Platform and Tools Graveyard :: Operations, enhancement)
Data Platform and Tools Graveyard
Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: whd)
References
Details
For deploying/using the mission control frontend with the latest dataset, we will need to purge the database and start over. I can take care of most of this if the environment is correct.
Wes, on Monday, could you change / set the following environment variables:
* Set `MISSION_CONTROL_TABLE` to `error_aggregates_v2`
* Set `FETCH_MEASURE_DATA` to 0
Let me know when you've done this and I will start the db purge/update/backfill. Once things are in an acceptable state, we will want to turn `FETCH_MEASURE_DATA` on again.
Assignee | ||
Comment 1•7 years ago
|
||
We did this. It mostly worked. We're going to follow up in investigating some potentially slow queries that were not slow on v1, but it might be an unrelated Athena issue or something we simply didn't notice before.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•