[Toolserver-l] s3 replication is halted

[Mashiah Davidson]

River,

Good news, does it mean we might have s1 and s3 separated within around a
month and it is a good time to adopt scripts  and tools for this change?
Mashiah

2009/1/5 River Tarnell <river at loreley.flyingparchment.org.uk>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Platonides:
> > Move mysql data files to the new box
>
> i usually try to avoid that when splitting a database, since it means the
> innodb data file is much larger than it needs to be (yarrow has both s1 and
> s3,
> but the new server will only have s1).  it's also a good opportunity to
> defragment/reindex the tables, which helps performance a bit.
>
> > > there isn't enough disk space
> > > on the master to store the logs longer than they are now.
>
> > And on other servers? Or even copying the binlogs to knams/toolserver.
> > After all, binlog deletion is a manual process.
>
> yes, this would be nice, if Wikimedia would warn us before deleting the
> binlogs.
>
> > The same problem arises every few months. The procedures aren't good
> > enough yet. :-(
>
> yes, i agree.
>
>        - river.
> -----BEGIN PGP SIGNATURE-----
>
> iD8DBQFJYlJcIXd7fCuc5vIRAredAJ9FPsBvbZ5RGxWUNPtkTkTZ4VqIGACfdwEH
> pViyrITfCQDIlejBy7h64ls=
> =MBPK
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Toolserver-l mailing list
> Toolserver-l at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/toolserver-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikimedia.org/pipermail/toolserver-l/attachments/20090105/393c84e5/attachment.htm