Hi,
I would like to do a quick maintenance on the eventlogging mysql servers for security and certificates upgrades. This means that queries done sent there will not be temporarily available. I mentioned the need for maintenance to several members of Analytics team some time ago, and would like to coordinate the stop of the eventlogging schema inserts and the queries sent there (I know not only analytics, but research, mobile and more use those databases).
Only a mere rolling restart of the database servers is needed this time, which should not cause more than 20 minutes of unavailability and will be done on each server alternatively.
Probably this Friday is a good moment to do it, before we enter the deployment freeze window announced by release engineering, but I would like to confirm this with you and have someone from Analytics available, in case something goes wrong.
We’ll need to stop the eventlogging-consumer-mysql process on eventlog1001 while the master restart happens. I’m not working this Friday, but anyone on the Analytics team can do this.
On Wed, Dec 7, 2016 at 1:27 PM, Jaime Crespo jcrespo@wikimedia.org wrote:
Hi,
I would like to do a quick maintenance on the eventlogging mysql servers for security and certificates upgrades. This means that queries done sent there will not be temporarily available. I mentioned the need for maintenance to several members of Analytics team some time ago, and would like to coordinate the stop of the eventlogging schema inserts and the queries sent there (I know not only analytics, but research, mobile and more use those databases).
Only a mere rolling restart of the database servers is needed this time, which should not cause more than 20 minutes of unavailability and will be done on each server alternatively.
Probably this Friday is a good moment to do it, before we enter the deployment freeze window announced by release engineering, but I would like to confirm this with you and have someone from Analytics available, in case something goes wrong.
-- Jaime Crespo http://wikimedia.org
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
ping a-team when you do it on Friday, Jaime, one of us will be there.
On Wed, Dec 7, 2016 at 1:28 PM, Andrew Otto otto@wikimedia.org wrote:
We’ll need to stop the eventlogging-consumer-mysql process on eventlog1001 while the master restart happens. I’m not working this Friday, but anyone on the Analytics team can do this.
On Wed, Dec 7, 2016 at 1:27 PM, Jaime Crespo jcrespo@wikimedia.org wrote:
Hi,
I would like to do a quick maintenance on the eventlogging mysql servers for security and certificates upgrades. This means that queries done sent there will not be temporarily available. I mentioned the need for maintenance to several members of Analytics team some time ago, and would like to coordinate the stop of the eventlogging schema inserts and the queries sent there (I know not only analytics, but research, mobile and more use those databases).
Only a mere rolling restart of the database servers is needed this time, which should not cause more than 20 minutes of unavailability and will be done on each server alternatively.
Probably this Friday is a good moment to do it, before we enter the deployment freeze window announced by release engineering, but I would like to confirm this with you and have someone from Analytics available, in case something goes wrong.
-- Jaime Crespo http://wikimedia.org
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics
Analytics mailing list Analytics@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics