Honestly the holding back of replication from Riak OS is the only real downside
to the product. Reminds me of the old adage there's those that will never pay
for OS software...and those that can't afford not to (because of things like
Sox).
-J
Sent via iPhone
Is your e-mail Premiere?
On Jul
On Wed, Jul 21, 2010 at 2:01 PM, Alan McConnell wrote:
> I'm curious about this as well. Say I have a ten node cluster. Could I
> just schedule a midnight copy of each bitcask data directory every night,
> then restore to another ten node cluster by dropping one of each data
> directories on ea
I'm curious about this as well. Say I have a ten node cluster. Could I
just schedule a midnight copy of each bitcask data directory every night,
then restore to another ten node cluster by dropping one of each data
directories on each new node? How close does the timing needs to be? What
if the
Hey Justin,
Since Riak is lockless, what is the best approach to pulling a
distributed FS snapshot of the bitcask files across nodes? I assume if
they're not close to each other, you'll have an issue if you have to
restore a cluster.
-J
On Sun, Jul 11, 2010 at 8:14 PM, Justin Sheehy wrote:
> H
Great! Thanks for the info.
On Jul 12, 2010, at 10:14 AM, Justin Sheehy wrote:
> Hi, Jan.
>
> On Sun, Jul 11, 2010 at 8:53 PM, Jan Vincent wrote:
>
>> Given that riak is new in the database field, if ever I use riak in
>> production,
>> what would be the best way to back it up? I know that t
Hi, Jan.
On Sun, Jul 11, 2010 at 8:53 PM, Jan Vincent wrote:
> Given that riak is new in the database field, if ever I use riak in
> production,
> what would be the best way to back it up? I know that there's redundancy
> on the different nodes and NRW may be modifiable per request, but I'm
> w
