Questions about the state of mysos within twitter? about mysos

[xujyan]

Hey! Sorry about the confusion as we were transitioning code/docs into the new home: https://github.com/apache/incubator-cotton

I have now updated this repo's code and README to point to the new repo. You should use [email protected] and I have just updated the README page with the new links.

w.r.t to the failover issue, it's not solved in the codebase and at Twitter we are going to leverage 5.6 GTID for this and therefore don't have plans to make this work on pre-5.6. The currently deployed code doesn't support failover and our initial use cases don't need it. We'd be happy to accept contributions for it though.

Regarding BackupStore and more generally "gradually open sourcing more internal features", the truth is that we don't have more internal features that have yet to be open sourced. We merely have our custom implementations of BackupStore and Installer, etc. that handle our internal backup workflow and internal MySQL packages. Given how other organizations manage backups and package installation, implementations of BackupStore and Installer can be very simple and a reference implementation may not be necessary. And yes we store the backups on HDFS we pull them down by using hadoop commands directly. What's your workflow?

I have updated https://github.com/apache/incubator-cotton with details about mailing list and JIRA, etc. Please subscribe and post questions over there! Thanks for your interest!

Admittedly documentation is terribly lacking currently and we'll improve on this.