This is to include OS, Puppet, and database server running.
|Resolved||jcrespo||T140788 Labs databases rearchitecture (tracking)|
|Resolved||jcrespo||T141097 Implement a frontend failover solution for labsdb replicas|
|Resolved||Cmjohnson||T136860 rack/setup/install/deploy labsdb1009-labsdb1011|
|Resolved||jcrespo||T140452 Initial setup and provision of labsdb1009, labsdb1010 and labsdb1011|
|Resolved||jcrespo||T149422 Prepare for mariadb 10.1|
- Mentioned In
- T74931: Add el_timestamp to the externallinks table
T126946: disk failure on labsdb1002
rOPUP4d37c15d6895: Setup the new labsdb hosts with a new role
rOPUP0b2b801754ea: Setup the new labsdb hosts with a new role
rOPUP1d48ebcd297d: Setup the new labsdb hosts with a new role
T141097: Implement a frontend failover solution for labsdb replicas
rOPUPd971d1db7e4e: [WIP] Setup the new labsdb hosts with a new role
rOPUPa0cdecfbe182: [WIP] Setup the new labsdb hosts with a new role
rOPUPe0640cfe632c: Prepare hosts for labsdb1009, -10 and -11
rOPUP6ffa8b8d4748: Prepare hosts for labsdb1009, -10 and -11
- Mentioned Here
- T141097: Implement a frontend failover solution for labsdb replicas
T147051: Provide at least 2 separate service endpoints: one for slow, long running queries; and another for quick, web requests
T147052: Provision with data the new labsdb servers and provide replica service with at least 1 shard from a sanitized copy from production
T140788: Labs databases rearchitecture (tracking)
T142807: Migrate all users to new Wiki Replica cluster and decommission old hardware
@chasemp @yuvipanda This already needs your input, as I am editing "your" class hierarchy. I am creating a different role for the replicas as it will probably need very different config than a db::slave. Although maybe db::slave is now a bad name.
This is the smallest of the things pending here- I would like to discuss architecture, versions, user handling, proxies. Please meet with me soon.
@jcrespo one problem w/ T142807 being a subtask here is we have associated this task as a key result for the goal, and we have said T142807 is not part of that. Depending on how strictly you want to interpret the task/subtask relationship it may be better for T142807 to be a subtask of the main parent task itself at T140788
I am also curious!
One small thought -- I think we should strive to contain that convo to T147052 if we can. Not meant to be pedantic or annoying :) I think this task can be closed as scoped in the description actually. Since we did tie in key results with specific tasks (down to exact titles) I would like to try to keep their scopes locked down.
Socket authentication allow for easier administration:
$ sudo mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 80 Server version: 10.1.18-MariaDB MariaDB Server Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Monitoring of the new hosts can be seen at:
And private monitoring (query monitoring) at:
Slow queries are identified with no problem.
We will have to do some tuning in the future of the monitoring, but the original scope (OS, Puppet, and database server running) is done.