This is inferior to the Manatee design: https://github.com/joyent/manatee
Funnily enough I ran into this yesterday when Mist was posted and I looked at what other projects were under the umbrella.
Funnily enough I ran into this yesterday when Mist was posted and I looked at what other projects were under the umbrella.
Manatee didn't work for our use cases, which should not be interpreted as "manatee is bad". Here are a few of the reasons we forged a different solution:
- While node.js is a great language for many things, we didn't want the overhead of running the node.js/v8 runtime alongside postgres. 50M might seem negligible, but with thousands of postgres clusters for our clients every MB adds up.
- We didn't want the administrative overhead of managing a zookeeper cluster, and instead built the cluster management semantics directly into the yoke project.
- This may be different now, but at the time manatee was very heavily integrated into illumos/smartos. We really love smartos, but recognize that not all clients are able to use this tech.
For example, in this case it's not at all clear how the cluster management works, or even what the semantics are.
Technically you don't need ZFS to use the Manatee state machine. You could swap out the ZFS snapshot transfer service to use pg_basebackup instead.
For anyone interested I have made the appropriate alterations to Manatee to get it to run on Ubuntu with the standard ubuntu-zfs packages.
The fork is here: https://github.com/josephglanville/manatee
Chef cookbook to help you get started along with the other dependencies: https://github.com/josephglanville/cookbook-manatee