Thanks to everybody that worked on this project! Please let me or the
Analytics team know if you have any problem.
If there are none, I would propose the following: would it be feasible for
everybody if dbstore1002 was decommed (i.e. mysql stopped for good) in two
weeks time (March 5th more or less) ?
Thanks in advance,
Luca
Il giorno mar 19 feb 2019 alle ore 07:12 Manuel Arostegui <
marostegui(a)wikimedia.org> ha scritto:
The migration finished. These are the times in UTC
from 18th Feb 2019:
- Read only on dbstore1002: 05:53
- mysqldump start: 05:54:44
- mysqldump finished: 15:18:15
- data import in dbstore1005 start: 15:18:15
- data import dbstore1005 finished: 21:43:54
- read only OFF on dbstore1005: 21:43:54
Remember that dbstore1002 remain read-only.
Thanks
Manuel.
On Mon, Feb 18, 2019 at 6:58 AM Manuel Arostegui <marostegui(a)wikimedia.org>
wrote:
> Hello,
>
> I am setting dbstore1002 on read-only now, to start the migration.
>
> Thanks
> Manuel.
>
> On Tue, Feb 12, 2019 at 10:11 AM Luca Toscano <ltoscano(a)wikimedia.org>
> wrote:
>
>> Hi everybody,
>>
>> as described in here (
https://phabricator.wikimedia.org/T215589#4946535)
>> I am proposing a maintenance window to allow the Data Persistence and
>> Analytics teams to move the staging database from dbstore1002 to
>> dbstore1005 (its new home) on Monday 18th during the EU morning. This will
>> mean that the staging database on dbstore1002 will become read-only
>> (permanently), but an up to date copy with read/write capabilities will be
>> present on dbstore1005.
>>
>> Some notes:
>> - dbstore1002 will not be shutdown/decommissioned yet, you'll be able to
>> query tables as you are used to.
>> - as described in
>>
https://wikitech.wikimedia.org/wiki/Analytics/Data_access#MariaDB_replicas
>> several DNS CNAME/SRV records have been created to ease the use of the new
>> systems, please check them out :)
>>
>> Let me know if this is feasible or if you need more time for a specific
>> use case (let's coordinate in the task).
>>
>> Thanks!
>>
>> Luca (on behalf of the Analytics team)
>>
>