Yes. Actually we [cassandra] are seeing a fair number of people switching to Cassandra from hbase because of speed and reliability (no single points of failure).
I just looked at couchdb-lounge because I'm very interested in partitioning and hadn't heard about it.
The wiki unfortunately left the important questions unanswered. Does lounge handle the rebalancing when new shards are added/removed? Do I have to take the cluster offline to add new nodes? What are the failure modes (e.g. a node failing and coming back)? How is a replacement node bootstrapped?
Since none of that is mentioned I have my doubts that lounge is handling it adequately. But I'd be glad to hear otherwise!
13 comments
[ 2.1 ms ] story [ 35.6 ms ] threadMongoDB is heading that way, but its support for partitioning, which couchdb-lounge is performing adequately already, is in alpha.
The wiki unfortunately left the important questions unanswered. Does lounge handle the rebalancing when new shards are added/removed? Do I have to take the cluster offline to add new nodes? What are the failure modes (e.g. a node failing and coming back)? How is a replacement node bootstrapped?
Since none of that is mentioned I have my doubts that lounge is handling it adequately. But I'd be glad to hear otherwise!
"I update this blog a few times a month. Don't worry -- I'm worth waiting for."
User gsteph22 has only submitted two articles, both from this crappy blog.