[argvzero]

Chief Architect at Basho here:

Saying Riak is categorically non-operations-oriented is a bit hyperbolic, but I will be the first to acknowledge that we need even more visibility into failure-recovery / degraded mode situations. I've spoken to a few customers who have "cheat sheets" of Erlang console commands they use to debug things like handoff slowness or poor performance in general. This alone means we need to do better,

On the other hand, Riak continues to function in scenarios where other databases would be completely unavailable. I'll take immature visibility during those situations over complete unavailability any day,

I appreciate your feedback - I can assure you that this is something we're constantly working on and you'll see improvements with each release.

Finally, if you've been bitten by anything specific you'd like to see fixed, we do all our development in the open at http://github.com/basho, so github issues, pull requests, etc go right into our internal tools and workflows.

Cheers,

Andy Gross

[rubyrescue]

Would love to give some feedback. I like Riak and I believe in it - over the long haul I'm 100% sure it will be an amazing product.

Let's grab beers at Erlang Factory!

Chad

[argvzero]

Sounds good - I'll see you there!