idea to proactively cause GCing to happen? (I.e. take a node out
of the haproxy LB pool, somehow cause it to gc, and then put the node back
in... repeat at intervals for each node?)
Simon Smith
Do you have your Amazon security policy set to allow that port? If
you were accessing internally before, the internal security policy may
have allowed that traffic, but the default external one doesn't (at
least that is how it worked for my account).
On Tue, Dec 8, 2009 at 10:09 AM, Sunil Khedar
The company I'm with is still small and in the early stages, but we're
planning on using Cassandra for user profile information (in
development right now), and possibly other uses later on. We
evaluated CouchDB and Voldermort, and both of those were great as well
- for CouchDB, I really liked
I'm sorry if this was covered before, but if you lose a node and
cannot bring it (or a replacement) back with the same IP address or
DNS name, is your only option to restart the entire cluster? E.g. if
I have nodes 1, 2, and 3 with replication factor 3, and then I lose
node 3, is it possible to
I don't have an opinion on the default timeout. But in my experience
with other applications, you want to consciously make a choice about
what your timeout, based on your architecture and performance
requirements. You're much better off explicitly setting a timeout
that will cause your
-gathering step should be for me?
Thank you,
Simon Smith
Arcode Corporation
