Igor Gaponenko: to report on the last round of negotiation with Yee
preliminarily agreement on the following configuration of workers: 2U server, single-socket CPU 32C/64HT, 256 GB, 24 disk slots, 12 slots will be populated with NVMe drives of 3.5 GB each. So the total amount of the raw storage per worker would be 42 TB. The usable amount after setting up RAID would be 2 drives less.
Fritz Mueller: any news on the development machines?
The qserv-ingest is meant for testing the Kubernetes-based ingest framework. At the end of the ingest workflow the result validation test based on DB Bench is being run. It's used for various purposes, including performance.
The qserv itest is meant for testing Qserv in the Docker compose environment.
Are we going to merge both packages into qserv? What implications of this move we should expect?
There are still uncertainties about what needs to be retained in the persistent state (new table qservmeta.QMessages. How many details we should retain?
What needs to be done in the long term to improve error reporting to users and to make it usable for Qserv data administrators?
Fritz Mueller is going to look for the use of the column code by mysql-proxy. If it's not used then we should eliminate it.
Partitioning director and child tables
team
Context:
there is a little bit of confusion on the overlap tables of the child tables
Igor Gaponenko will run extensive tests and report results on the Confluence page (TBC)