Page MenuHomePhabricator

categories migration: determine size of new WDQS categories dump
Closed, ResolvedPublic

Description

Per T374016 and T374967 , we have to migrate wdqs-categories to its own infrastructure. To that end, we'll need to figure out our disk space needs.

The current WDQS categories journal file is ~36 GB:

bking@cumin2002:~$ sudo cumin A:wdqs-public 'du -hcxs /srv/wdqs/categories.jnl'
...
----- OUTPUT of 'du -hcxs /srv/wdqs/categories.jnl' -----
36G     /srv/wdqs/categories.jnl
36G     total

However, a newly-imported dump is likely to be smaller, as Blazegraph (similar to other DBs) doesn't fully reclaim space. Creating this ticket to:

  • Do a full data reload from categories using this cookbook
  • Record results

RESULTS Total size 27200978944 (human readable: 26G)

Event Timeline

I had a problem starting the categories reload cookbook, as we've already made some changes as part of the process of separating categories from the rest of the WDQS stack (T374009 links some of the changes).

Before I could get the cookbook to run, I had to load the new scripts from this CR . The right way to do this is via a scap deploy, but I one-off copied the scripts to /srv/deployment/wdqs/wdqs on wdqs2020 and started the cookbook from wdqs2020. This appears to have worked, and the cookbook is still running as I write this...

RKemper subscribed.

Results are in on wdqs2020:

Total size 27200978944 (human readable: 26G)

Gehel triaged this task as Medium priority.Sep 24 2024, 2:29 PM
bking claimed this task.

For a bit more context:

Size of dumps download: ~1.5 GB
Size of newly-created journal file: 26 GB
Time to create journal file from dumps: ~90 minutes

All of these figures will be important as we decide the next steps.

I've added this info to the WDQS categories migration Google Doc and now I'm closing out this ticket.