I know it doesn't. But is this a valid enhancement request?
On Tue, Jul 5, 2011 at 1:32 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
On Tue, Jul 5, 2011 at 1:27 PM, Raj N raj.cassan...@gmail.com wrote:
Hi experts,
Are there any benchmarks that quantify how long nodetool repair
On Tue, Apr 5, 2011 at 9:03 PM, Maki Watanabe watanabe.m...@gmail.com wrote:
Thanks Sylvain, it's very clear.
But should I still need to force major compaction regularly to clear
tombstones?
I know that minor compaction clear the tombstones after 0.7, but
maximumCompactionThreshold limits
On Tue, Apr 5, 2011 at 12:01 AM, Maki Watanabe watanabe.m...@gmail.com wrote:
Hello,
On reading O'Reilly's Cassandra book and wiki, I'm a bit confusing on
nodetool repair and compact.
I believe we need to run nodetool repair regularly, and it synchronize
all replica nodes at the end.
Thanks Sylvain, it's very clear.
But should I still need to force major compaction regularly to clear tombstones?
I know that minor compaction clear the tombstones after 0.7, but
maximumCompactionThreshold limits the maximum number of sstable which
will be merged at once, so to GC all tombstones
On Mon, Mar 21, 2011 at 8:33 PM, A J s5a...@gmail.com wrote:
I am trying to estimate the time it will take to rebuild a node. After
loading reasonable data,
...
For some reason, the repair command runs forever. I just have 3G of
data per node but still the repair is running for more than an
0.7.4
On Tue, Mar 22, 2011 at 11:49 AM, Robert Coli rc...@digg.com wrote:
On Mon, Mar 21, 2011 at 8:33 PM, A J s5a...@gmail.com wrote:
I am trying to estimate the time it will take to rebuild a node. After
loading reasonable data,
...
For some reason, the repair command runs forever. I just
Are you monitoring the progress http://wiki.apache.org/cassandra/Streaming ?
or with nodetool netstats
Aaron
On 22 Mar 2011, at 16:33, A J wrote:
I am trying to estimate the time it will take to rebuild a node. After
loading reasonable data, I brought down a node and manually removed
all
Thanks Jonathan, Aaron, Daniel! I have a related question.
I would like to get a copy of data from these 12-server cluster with
manually assigned babanced server tokens, and set it up on a new cluster. I
would like to minimize the number of the server on the new cluster without
having to build
At least if you are using RackUnawareStrategy
Cheers,
Daniel
On Mar 15, 2011, at 6:44 PM, Huy Le wrote:
Hi,
We have a cluster with 12 servers and use RF=3. When running nodetool
repair, do we have to run it on all nodes on the cluster or can we run on
every 3rd node? Thanks!
Huy
AFAIK you should run it on every node.
http://wiki.apache.org/cassandra/Operations#Repairing_missing_or_inconsistent_data
Aaron
On 16 Mar 2011, at 06:58, Daniel Doubleday wrote:
At least if you are using RackUnawareStrategy
Cheers,
Daniel
On Mar 15, 2011, at 6:44 PM, Huy Le wrote:
right, every 3rd node is adequate w/ RUS/SimpleStrategy since each
node repairs all the ranges it has replicated to it.
On Tue, Mar 15, 2011 at 12:58 PM, Daniel Doubleday
daniel.double...@gmx.net wrote:
At least if you are using RackUnawareStrategy
Cheers,
Daniel
On Mar 15, 2011, at 6:44 PM,
I just saw repair hang here too, it's actually very easy to reproduce. I'm
looking at it right now.
--
Sylvain
On Tue, Mar 8, 2011 at 4:30 PM, Karl Hiramoto k...@hiramoto.org wrote:
I never saw this before upgrading to 0.7.3 but now I do nodetool repair and
it sits there for hours.
On 08/03/2011 16:34, Sylvain Lebresne wrote:
I just saw repair hang here too, it's actually very easy to reproduce.
I'm looking at it right now.
--
Thanks. Should i bump GCGraceSeconds since i can no longer repair?
I tried repair on 3 nodes of a 6 node cluster and they all hang.
I suspect you are in the case of
https://issues.apache.org/jira/browse/CASSANDRA-2290.
That is some neighbor node died or was unable to perform its part of the
repair. You can always
retry making sure all node are and stay alive to see if it is the former
one. But seeing the
other exception in
Hi all,
just wanted to make sure that I get this right:
What this means is that I have to schedule repairs only on every RFs node?
So with 4 nodes and RF=2 I would repair nodes 1 and 3
and with 6 nodes and RF=3 I would repair nodes 1 and 4
and that would lead to a synched cluster?
On Thu, Jul
if you're using RackUnawareStrategy that should work.
On Wed, Sep 22, 2010 at 5:27 AM, Daniel Doubleday
daniel.double...@gmx.net wrote:
Hi all,
just wanted to make sure that I get this right:
What this means is that I have to schedule repairs only on every RFs node?
So with 4 nodes and
On Thu, Jul 15, 2010 at 1:54 PM, B. Todd Burruss bburr...@real.com wrote:
if i have N=3 and run nodetool repair on node X. i assume that merkle
trees (at a minimum) are calculated on nodes X, X+1, and X+2 (since
N=3). when the repair is finished are nodes X, X+1, and X+2 all in sync
with
201 - 217 of 217 matches
Mail list logo
