Per the discussion in T164990, the x1 database cluster is close enough to full that a new service does not comfortably fit there. Reading Lists can temporarily live there with some restrictions but should eventually go to the to-be-established new cluster x2. That means new hardware needs to be procured - per T164990#3264314, probably 4 DB servers. This should be coordinated with the other would-be tenants of the new cluster.
|Open||None||T199451 Revisit limits on reading lists and increase them if possible|
|Open||None||T177462 DB hardware for Reading Lists|
- Mentioned In
- T199451: Revisit limits on reading lists and increase them if possible
rERLS0758ac79b2a0: Track reading list size
rERLSff5c38403e6e: Track reading list size
rERLS27a9b033b189: Track reading list size
rERLS7021e534eec3: Track reading list size
rERLS5bd648a1d184: Track reading list size
rERLS8ec7242f5c09: Track reading list size
T168984: Create and enforce a limit for number of Reading Lists and Reading Lists entries for each user
- Mentioned Here
- T164990: RfC: Reading List service
new cluster x2
When budgeting this year's resources, SRE decision (not only mine, Mark signed it off) was to budget to increase x1 servers rather than setting up a separate, dedicated cluster. That is coming for codfw on Q1 and for eqiad in Q3.
There was already a small increase of resources in late Q4.
I don't really have anything beyond what was projected in T164990. (The current load is around 1 read/sec an 0.1 write/sec, but the feature is not used on the web which would be the overwhelming majority of the load. OTOH there are some temporary limitations in place: no more than 10 lists or 100 list entries read in a single request - those would presumably be lifted if the DB permits.)