On Tue, Jun 15, 2010 at 3:55 PM, Charles Butterfield <charles.butterfi...@nextcentury.com> wrote: > Benjamin Black <b <at> b3k.us> writes: > >> >> Then write slower. There is no free lunch. >> >> b > > Are you implying that clients need to throttle their collective load on the > server to avoid causing the server to fail? That seems undesirable. Is this > a > side effect of a server bug, or is it part of the intended design? >
I am only saying something obvious: if you don't have sufficient resources to handle the demand, you should reduce demand, increase resources, or expect errors. Doing lots of writes without much heap space is such a situation (whether or not it is happening in this instance), but there are many others. This constraint it not specific to Cassandra. Hence, there is no free lunch. b
