Change Details

The long process to load the new servers with data from all shards ({T153743}) has finished. We need to get more usage of the new servers to shake out issues like: * missing grants * performance of new servers * evaluate need for query killers The new hosts are reachable at: * labsdb-web.eqiad.wmnet * labsdb-analytics.eqiad.wmnet Both service names provide access to all shards. The intended difference is for the labsdb-web to be more responsive for interactive queries and labsdb-analytics to be optimized for long running queries.

The long process to load the new servers with data from all shards ({T153743}) has finished. We need to get more usage of the new servers to shake out issues like: * missing grants * performance of new servers * evaluate need for query killers The new hosts are reachable at: * `labsdb-web.eqiad.wmnet` * `labsdb-analytics.eqiad.wmnet` Both service names provide access to all shards. The intended difference is for the labsdb-web to be more responsive for interactive queries and labsdb-analytics to be optimized for long running queries. NOTE: These new servers currently will **not** allow tools to create their own databases/tables co-located with the replicated content. If a tool is using this functionality on the current `*.labsdb` hosts we are recommending that it be updated to instead keep all tool specific data on toolsdb and perform any joining of replica data and tool specific data in application space rather than with cross-database joins. See T156869 for further discussion.

The long process to load the new servers with data from all shards ({T153743}) has finished. We need to get more usage of the new servers to shake out issues like: * missing grants * performance of new servers * evaluate need for query killers The new hosts are reachable at: * `labsdb-web.eqiad.wmnet` * `labsdb-analytics.eqiad.wmnet` Both service names provide access to all shards. The intended difference is for the labsdb-web to be more responsive for interactive queries and labsdb-analytics to be optimized for long running queries. NOTE: These new servers currently will **not** allow tools to create their own databases/tables co-located with the replicated content. If a tool is using this functionality on the current `*.labsdb` hosts we are recommending that it be updated to instead keep all tool specific data on toolsdb and perform any joining of replica data and tool specific data in application space rather than with cross-database joins. See T156869 for further discussion.