Currently the underlying database uses an amount of replication as set by
the person who implemented the database calls for that database (HBase,
Hypertable = 3, Cassandra = 4, Voldemort = 2). Need to allow this parameter
to be set by the user or fall back on a known value otherwise.
Tested and working. The -n flag allows the user to set the replication
amount for all databases except for MySQL, which is restricted to 3x
replication due to static sharding configuration.
If -n is specified, that is taken as the number of replicas to set up for
all data in the system. If -n is not specified, we take the minimum of (min
images - 1) and (3) as the number of replicas. We do (min - 1) to
accomodate databases that use a single head node to store metadata, and cap
off replication at 3x since that is generally good enough (and if not, the
user will specify a greater number).
Load balancer also shows the name of the database and the replication
amount currently specified on the cloud status page.
Will be in next release.
Original issue reported on code.google.com by shattere...@gmail.com on 21 Jul 2009 at 8:10
Original issue reported on code.google.com by
shattere...@gmail.comon 21 Jul 2009 at 8:10