Gary fwiw I get oom with Cl one quite commonly if I'm not careful with my
writes
On Jun 11, 2010 8:48 PM, "Jonathan Ellis" wrote:
We give you enough rope to hang yourself. Don't use ZERO if that's
not what you want. :)
On Fri, Jun 11, 2010 at 9:23 AM, William Ashley wrote:
> Would it be reas
We give you enough rope to hang yourself. Don't use ZERO if that's
not what you want. :)
On Fri, Jun 11, 2010 at 9:23 AM, William Ashley wrote:
> Would it be reasonable to have (possibly configurable) caps on the maximum
> size of any internal Cassandra queues that are directly populated by cli
Would it be reasonable to have (possibly configurable) caps on the maximum size
of any internal Cassandra queues that are directly populated by client
requests? I understand this might mean sometimes breaking the API contract for
writers using CL.ZERO by blocking on those calls, but on the other
On Fri, Jun 11, 2010 at 10:14, Julie wrote:
> Ran Tavory gmail.com> writes:
>
>>
>> I can't say exactly how much memory is the correct amount, but surely 1G is
> very little. By replicating 3 times your cluster now makes 3 times more work
> than it used to do, both on reads and on writes while th
Ran Tavory gmail.com> writes:
>
> I can't say exactly how much memory is the correct amount, but surely 1G is
very little. By replicating 3 times your cluster now makes 3 times more work
than it used to do, both on reads and on writes while the readers/writers
continue hammering it the same pace
I am running an 8 node cassandra cluster with each node on its own dedicated VM.
My app very quickly populates the database with about 100,000 rows of data
(each row is about 100K bytes) times the number of nodes in my cluster so
there's about 100,000 rows of data on each node (seems very evenly d
I can't say exactly how much memory is the correct amount, but surely 1G is
very little.
By replicating 3 times your cluster now makes 3 times more work than it used
to do, both on reads and on writes while the readers/writers continue
hammering it the same pace.
So once you've upped your memory (