Change Details

Per the discussion in T164990, x1 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 x2, which does not exist yet. That means new hardware needs to be procured - per T164990#3264314, probably 4 DB servers. (Not adding #operations #hardware-requests yet as this is just a tracking task and not actionable right now; will probably happen in next annual budget planning.)

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. (Not adding #operations #hardware-requests yet as this is just a tracking task and not actionable right now; will probably happen in next annual budget planning.)

Per the discussion in T164990, x1the `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 x2,the to-be-established new cluster`x2`. which does not exist yet.That means new hardware needs to be procured - per T164990#3264314, That means new hardware needs to be procured - per T164990#3264314,probably 4 DB servers. probably 4 DB serversThis should be coordinated with the other would-be tenants of the new cluster. (Not adding #operations #hardware-requests yet as this is just a tracking task and not actionable right now; will probably happen in next annual budget planning.)