El mié, 20-04-2011 a las 07:59 +1200, aaron morton escribió:
> The dynamic snitch only reduces the chance that a node used in a read
> operation, it depends on the RF, the CL for the operation, the partitioner
> and possibly the network topology. Dropping read messages is ok, so long as
> your o
The dynamic snitch only reduces the chance that a node used in a read
operation, it depends on the RF, the CL for the operation, the partitioner and
possibly the network topology. Dropping read messages is ok, so long as your
operation completes at the requested CL.
Are you using either a key
Shouldn't the dynamic snitch take into account response times and ask a
slow node for less requests? It seems that at node startup, only a
handfull of requests arrive to the node and it keeps up well, but
there's moment where there's more than it can handle with a cold cache
and starts droping mess
How difficult do you think this could be? I would be interested into
developing this if it's feasible.
El vie, 15-04-2011 a las 16:19 +0200, Peter Schuller escribió:
> > Hi everyone, is there any recommended procedure to warm up a node before
> > bringing it up?
>
> Currently the only out-of-the-
> Hi everyone, is there any recommended procedure to warm up a node before
> bringing it up?
Currently the only out-of-the-box support for warming up caches is
that implied by the key cache and row cache, which will pre-heat on
start-up. Indexes will be indirectly preheated by index sampling, to
t
Hi everyone, is there any recommended procedure to warm up a node before
bringing it up?
Thanks!
