Drop unused celery_taskmeta and celery_tasksetmeta tables

RESOLVED FIXED

Status

Tree Management
Treeherder: Infrastructure
P3
normal
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: emorley, Assigned: emorley)

Tracking

Details

(Assignee)

Description

2 years ago
These two tables only exist on:
* SCL3 prod
* Heroku stage (which was copied from SCl3 prod)
* Heroku prototype (where celery results were temporarily enabled as part of auto-classify experimentation)

I believe the tables are unused and can be removed, and only exist on SCL3 prod since 2 years ago celery results were enabled, prior to:
https://github.com/mozilla/treeherder/commit/ad1310fb26afa25a13f4c17d25a62385569d085e#diff-52b9059212bc068dcffb374ea6360316R273

James, is this correct? :-)
Flags: needinfo?(james)
(Assignee)

Updated

2 years ago
Blocks: 1252854
This seems like a good idea to me. They aren't used for anything I know of.
Flags: needinfo?(james)
(Assignee)

Comment 2

2 years ago
Prototype:

18:54:00	DROP TABLE treeherder.celery_taskmeta	0 row(s) affected	0.141 sec
18:54:00	DROP TABLE treeherder.celery_tasksetmeta	0 row(s) affected	0.125 sec

Stage:

18:52:05	DROP TABLE treeherder.celery_taskmeta	0 row(s) affected	0.110 sec
18:52:05	DROP TABLE treeherder.celery_tasksetmeta	0 row(s) affected	0.125 sec

Prod:

18:56:50	DROP TABLE treeherder.celery_taskmeta	0 row(s) affected	0.203 sec
18:56:50	DROP TABLE treeherder.celery_tasksetmeta	0 row(s) affected	0.140 sec
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.