Closed
Bug 1051836
Opened 11 years ago
Closed 11 years ago
Prune hive_results after import
Categories
(addons.mozilla.org Graveyard :: Administration, defect, P1)
addons.mozilla.org Graveyard
Administration
Tracking
(Not tracked)
RESOLVED
FIXED
2014-09
People
(Reporter: jason, Assigned: davidbgk)
Details
(Whiteboard: [qa-])
Please create a cleanup process to remove data after import. The path is t NETAPP_STORAGE/tmp/hive_results
[root@addonsadm.private.phx1 hive_results]# du -hs *
4.3G 2014-07-15
4.3G 2014-07-16
4.2G 2014-07-17
4.1G 2014-07-18
3.6G 2014-07-19
1.4G 2014-07-20
4.2G 2014-07-21
4.3G 2014-07-22
4.6G 2014-07-23
4.3G 2014-07-24
4.0G 2014-07-25
3.5G 2014-07-26
3.4G 2014-07-27
3.7G 2014-07-28
3.7G 2014-07-29
4.6G 2014-07-30
4.5G 2014-07-31
4.1G 2014-08-01
3.7G 2014-08-02
3.6G 2014-08-03
4.5G 2014-08-04
4.4G 2014-08-05
4.4G 2014-08-06
4.3G 2014-08-07
4.1G 2014-08-08
3.7G 2014-08-09
3.6G 2014-08-10
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → david
| Assignee | ||
Comment 1•11 years ago
|
||
There are a few strategic questions here:
* How do we envision the switch from previous stats to new ones? I see two options here, switching at d+1 with a highly visible difference OR logging results for a month and switching with results from d-30, the gap will only be visible for annual views in that case.
* What will be our reactivity on filling gaps when the script fails (because files are missing for instance)? Is that a week, a month? Deleting hive results without having filled gaps would result in a more painful process (re-running hive script + re-running cron tasks).
* How much space left do we have on that disk? :)
Comment 2•11 years ago
|
||
I'm not sure I understand the first question.
As far as a strategy: Why don't we just process anything that exists on disk and once it is done processing we delete it. If we want to re-process data we re-dump it from Hive. If data is missing, we re-dump it from Hive. Basically, if it exists on disk, we'll eventually pull it in to our database and delete it. The "normal" would be to have an empty directory.
| Assignee | ||
Comment 3•11 years ago
|
||
Sorry for not being clear. We're currently filling _tmp tables in production, maybe we can reuse that data to fill real _count tables for let's say the month of August once we make the switch to our new scripts (in September?). That way the differences are less visible/brutal for addons' owners. Thoughts?
Otherwise we just have to verify that the command works for a given missing day and delete all hive_results data.
I'll create a command for that anyway.
| Reporter | ||
Comment 4•11 years ago
|
||
We have about 70GB left on this volume. We should have more space once bug 1051854 is completed.
FWIW hive data push -> mktadm host was a temporary solution as per anurag and ops was not expecting this much hive data to be stored long term.
Comment 5•11 years ago
|
||
(In reply to David Larlet [:davidbgk] from comment #3)
> Sorry for not being clear. We're currently filling _tmp tables in
> production, maybe we can reuse that data to fill real _count tables for
> let's say the month of August once we make the switch to our new scripts (in
> September?). That way the differences are less visible/brutal for addons'
> owners. Thoughts?
Depending on why the numbers aren't lining up correctly, sure.
| Assignee | ||
Comment 6•11 years ago
|
||
Jason, I think we can safely remove 2014-07-* data given that it was mostly for testing purpose and we'll not use that data anymore. Do you confirm Wil?
Flags: needinfo?(clouserw)
| Assignee | ||
Comment 7•11 years ago
|
||
Comment 8•11 years ago
|
||
(In reply to David Larlet [:davidbgk] from comment #6)
> Jason, I think we can safely remove 2014-07-* data given that it was mostly
> for testing purpose and we'll not use that data anymore. Do you confirm Wil?
sure
Flags: needinfo?(clouserw)
| Reporter | ||
Comment 9•11 years ago
|
||
Removed 2014-07-* data.
Before:
147G hive_results/
After:
81G hive_results/
| Assignee | ||
Updated•11 years ago
|
Priority: -- → P1
Target Milestone: --- → 2014-09
| Assignee | ||
Comment 10•11 years ago
|
||
https://github.com/mozilla/olympia/commit/fd074305fa73293b8dae6b4d9b1add4bdbe15459
With that change, *new* imports will clean up files. We'll have to clean up older ones once the command in https://bugzilla.mozilla.org/show_bug.cgi?id=1014752#c75 has been run.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
Please add STR here or mark it with [qa-] if no QA is needed.
Flags: needinfo?(david)
| Assignee | ||
Comment 13•11 years ago
|
||
Given the differences in results we can remove hive data for 2014-08-* too as we'll not refill as previously described in https://bugzilla.mozilla.org/show_bug.cgi?id=1014752#c75. Jason can you do that?
| Reporter | ||
Comment 14•11 years ago
|
||
2014-08-* removed.
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•