Page MenuHomePhabricator

restbase: high storage utilization
Open, MediumPublic

Assigned To
None
Authored By
Eevans
Jul 18 2023, 4:45 PM
Referenced Files
F57308664: image.png
Aug 27 2024, 9:07 PM
F57308639: image.png
Aug 27 2024, 9:07 PM
F57308628: image.png
Aug 27 2024, 9:07 PM
F57308618: image.png
Aug 27 2024, 9:07 PM
F57308609: image.png
Aug 27 2024, 9:07 PM
F37143947: image.png
Jul 19 2023, 8:56 PM
F37142959: image.png
Jul 18 2023, 4:45 PM

Description

Storage utilization in the RESTBase Cassandra cluster is quite high (some nodes faring worse than others):

image.png (878×1 px, 96 KB)

Event Timeline

Eevans triaged this task as Medium priority.Jul 19 2023, 8:52 PM
Eevans updated the task description. (Show Details)

I did some nodetool cleanups on some of the worst of the nodes, and lowered utilization by a few percent.

image.png (878×1 px, 66 KB)

The RESTBase mobile-sections tables (corresponding to Cassandra keyspaces {commons,enwiki,others,wikipedia}_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY) seem to be no longer in use (having been superseded by PCS?). See:

image.png (964×1 px, 74 KB)

image.png (964×1 px, 602 KB)

image.png (964×1 px, 74 KB)

image.png (964×1 px, 612 KB)

Combined that's almost 15TB of storage:

image.png (964×1 px, 177 KB)

I propose that we TRUNCATE these tables (leaving the schema in place for now). Any objections @Jgiannelos? @akosiaris ?

I think its fine to truncate the mobile-sections related tables.

Ok, here (for posterity sake) is what I will apply:

TRUNCATE "commons_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;
TRUNCATE "enwiki_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;
TRUNCATE "others_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;
TRUNCATE "wikipedia_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;

Mentioned in SAL (#wikimedia-operations) [2024-08-28T15:52:41Z] <urandom> TRUNCATE-ing RESTBase tables ({commons,enwiki,others,wikipedia}_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY) — T342148

Ok, here (for posterity sake) is what I will apply:

TRUNCATE "commons_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;
TRUNCATE "enwiki_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;
TRUNCATE "others_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;
TRUNCATE "wikipedia_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY".data;

That done, I'll give it a couple of hours before clearing the snapshots and actually reclaiming the space (out of an abundance of caution).

The RESTBase mobile-sections tables (corresponding to Cassandra keyspaces {commons,enwiki,others,wikipedia}_T_mobileoZCBVtILw5eSrwi0VIGaFVSr2jY) seem to be no longer in use (having been superseded by PCS?). See:

image.png (964×1 px, 74 KB)

image.png (964×1 px, 602 KB)

image.png (964×1 px, 74 KB)

image.png (964×1 px, 612 KB)

Combined that's almost 15TB of storage:

image.png (964×1 px, 177 KB)

I propose that we TRUNCATE these tables (leaving the schema in place for now). Any objections @Jgiannelos? @akosiaris ?

None on my side. Thanks for chasing that down!