Change Details

The master database for phabricator has been failed over to a larger, newer host (we almost doubled the memory). However, it is know some functionality happened on the phabricator replicas. As the master has been switched, so has the replica. The DNS has been updated accordingly. However- **the new replica for phabricator runs on port `3323`**, not the standard one 3306. We warned some weeks in advance, misc services had to be prepared for different port configuration, and in the case of phabricator, a new separate option has to be puppetized (mysql.port), and I would recommend exposing it at ``` hieradata/role/*/phabricator.yaml:phabricator::mysql::slave::port ``` For example (details are left to the phabricator owners). There are plans to change the master port at some point, so I recommend fixing the master configuration, too, even if we will leave it on port default/3306 at the moment.

The master database for phabricator has been failed over to a larger, newer host (we almost doubled the memory). However, it is know some functionality happen to break on the phabricator replicas. As the master has been switched, so has the replica. The DNS has been updated accordingly. However- **the new replica for phabricator runs on port `3323`**, not the standard one 3306. We warned some weeks in advance, misc services had to be prepared for different port configuration, and in the case of phabricator, a new separate option has to be puppetized (mysql.port), and I would recommend exposing it at ``` hieradata/role/*/phabricator.yaml:phabricator::mysql::slave::port ``` For example (details are left to the phabricator owners). There are plans to change the master port at some point, so I recommend fixing the master configuration, too, even if we will leave it on port default/3306 at the moment.

The master database for phabricator has been failed over to a larger, newer host (we almost doubled the memory). However, it is know some functionality happened to break on the phabricator replicas. As the master has been switched, so has the replica. The DNS has been updated accordingly. However- **the new replica for phabricator runs on port `3323`**, not the standard one 3306. We warned some weeks in advance, misc services had to be prepared for different port configuration, and in the case of phabricator, a new separate option has to be puppetized (mysql.port), and I would recommend exposing it at ``` hieradata/role/*/phabricator.yaml:phabricator::mysql::slave::port ``` For example (details are left to the phabricator owners). There are plans to change the master port at some point, so I recommend fixing the master configuration, too, even if we will leave it on port default/3306 at the moment.