[00:03:16] ryankemper: I think maybe tee -a was needed? if it's easy to return it to normal, that seems sensible. Now, I think we should have a couple hosts for the next split graph loads, so that we can keep the existing ones up and running while doing those loads. We should spend some time figuring out next week how we want to do that...maybe we ought to consider doing the next loads for any updated graph definition (and more triples since [00:03:16] the last split was defined) in codfw first. So, we'd presumably come back to use wdqs2023 again for that purpose. But, yeah, if it's easy to bring it back to normal for know that makes sense to me. [00:03:58] s/know/now/ [00:19:50] dr0ptp4kt: okay, sounds like we should keep as is. no pressing need to return to service since codfw is overprovisioned anyway [00:19:51] thanks! [11:48:46] r.yankemper that works, too! thx [12:47:39] dr0ptp4kt, ryankemper : note that we also have wdqs1009/1010 that are test hosts and can be used for whatever testing we need [12:53:18] thx gehel [13:26:59] headed to my co-work space and to run a few errands, should be back in ~1h [15:00:56] \o [16:52:51] Lunch, back in ~1h [17:44:23] gehel: dr0ptp4kt: actually we don't, those hosts are gone now. it's just 1022-1024 (and 2023) [18:40:15] * ebernhardson finally remembers to copy everything off the old stats hoss [18:40:18] s/hoss/hosts/ [19:18:05] 🐴 [19:18:21] thx ryankemper [19:26:18] LOL @ 🐴 [19:50:26] heading home from co-work space, back in ~30 [19:52:38] * ebernhardson is surprised at how long conda has been building this test environment... [19:53:08] 429s and finished :S i guess could be worse [20:14:10] back]