[15:35:39] If there are no objections, I'm going to de-pool sessionstore in codfw (currently < 400 req/sec) to upgrade Cassandra to 3.11.14 (very minor upgrade) [16:55:50] Ok, all done (and looks good). I'll monitor it, and plan to do eqiad a little later if possible. [20:24:15] Ok, same thing; If there are no objections, I'll proceed with eqiad, depooling sessionstore and upgrading Cassandra [20:44:17] curious, anyone know why we need to compile are own mariadb clients? see, https://gerrit.wikimedia.org/r/plugins/gitiles/operations/puppet/+/refs/heads/production/modules/profile/manifests/mariadb/packages_client.pp#11 [20:51:52] jhathaway- we don't, we did it just for maximum compatibility for production (linking to openssh) I belive the debian one link to another ssl library and doesn't necesarilly match the exact server version [20:52:18] in other words, it is a package we get for free when compiling the server [20:52:56] but unless you have mw db needs, you may use the debian one [20:53:11] got it, thanks! [20:53:45] packages_client.pp is only supposed to be used by cumin, not by random hosts [20:53:51] nod [20:54:45] and even that class allows for custom client packages [20:56:19] the fail message made me curious, as if providing your own vanilla client was dangerous [20:56:35] foor the root client profile, it is [20:57:16] (cumin), otherwise, there is a generic mariadb profile for random clients [20:58:05] ah, interesting [20:58:19] the idea being having 100 control for the stack for mw /production admin usage [20:58:23] 100% [20:58:35] about the version installed [21:03:28] make sense [21:03:32] *makes [21:05:20] for example, mysql broke the client protocol a few times, or to control tls compatiblity, specially back in the day [21:07:05] it is one of those things that was absolutely necesary years ago, and now it is nice to have but not a big deal [21:08:14] yeah, once you are bitten by those types of problems I can understand the extra caution