Frame Migration about featurebase HOT 4 CLOSED

Is this for expanding the cluster?

from featurebase.

Yes

-Todd

On Feb 19, 2016, at 2:57 PM, Ben Johnson [email protected] wrote:

Is this for expanding the cluster?

—
Reply to this email directly or view it on GitHub.

from featurebase.

@tgruben I was trying to implement this in-process but it gets ugly really fast. The server essential needs two configurations to try to manage and then it has to cut over.

I'm looking at doing a much simpler solution where we spin up a separate cluster and do a restore into the new cluster from the old one. Nodes in the new cluster, btw, can live on the same machine but just have different ports. Although since you're on AWS it probably makes the most sense to create a cluster with new machines, restore to that cluster, switch over the load balancer, and then remove the old machines.

The benefits of this approach are:

• the original cluster is operational during the whole process
• we can validate that the new cluster is working properly before cutting over
• if an error occurs halfway through then we don't need to try to clean up

We'll need to be able to have the input stream write to the old and new clusters though.

@tgruben @travisturner how does that sound?

from featurebase.

Closed via #62.

from featurebase.