On Tue, Feb 14, 2012 at 8:01 PM, aaron morton wrote:
> And the output from tpstats is ?
>
I can't reproduce it at the moment ;-(
nodetool is throwing 'Failed to retrieve RMIServer stub:' - which I'm
guessing/hoping is related to the stalled bootstrap.
>
> A
>
> -
> Aaron Mo
And the output from tpstats is ?
A
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 14/02/2012, at 12:43 PM, Franc Carter wrote:
> On Tue, Feb 14, 2012 at 6:06 AM, aaron morton wrote:
> What CL are you reading at ?
>
> Quorum
>
>
> Write ops g
On Tue, Feb 14, 2012 at 6:06 AM, aaron morton wrote:
> What CL are you reading at ?
>
Quorum
>
> Write ops go to RF number of nodes, read ops go to RF number of nodes 10%
> (the default probability that Read Repair will be running) of the time and
> CL number of nodes 90% of the time. With 2 no
What CL are you reading at ?
Write ops go to RF number of nodes, read ops go to RF number of nodes 10% (the
default probability that Read Repair will be running) of the time and CL number
of nodes 90% of the time. With 2 nodes and RF 2 the QUOURM is 2, every request
will involve all nodes.
A
Hi,
I've been looking at tpstats as various test queries run and I noticed
something I don't understand.
I have a two node cluster with RF=2 on which I run 4 parallel queries, each
job goes through a list of keys doing a multiget for 2 keys at a time. If
two of the queries go to one node and the
