To clarify: I understand that's about SWAP (the internal analytics notebooks platform for accessing private data like the webrequest table in Hive and EventLogging tables in MySQL), not the public PAWS platform, correct?

 

It sounded like the second machine was actually more intended and needed for stability and maintainability, rather than for load balancing? (The instructions at https://wikitech.wikimedia.org/wiki/SWAP#Access only mention notebook1001 as access point, so it wouldn't be surprising if fewer users went to notebook1002.) So does this recommissioning have implications on the stability and maintainability of SWAP? Just as an example, would we still be able to upgrade the Jupyter version without hassle (it runs 4.2.0 which is one and a half years old at this point, and quite a few bug fixes and features behind the current version, 5.2.1)? 

Is there a Phab ticket for this? (At https://www.mediawiki.org/wiki/Wikimedia_Technology/Goals/2017-18_Q2 there is a link labeled "Hardware refresh jupyter notebooks", but it is 404.)

In any case, thanks for your work in this area (and for posting the heads-up here)! SWAP is a really important tool for the work of myself and the other data analysts in the Audiences department, and other people's as well.