RE: Repairs on 2.1.12

2017-05-11 Thread Mark Furlong
The repair on the DC has completed in 308 hours. What would be helpful is if 
anyone has a good way of monitoring a manual ‘antientropy’ repair.

Thanks
Mark
801-705-7115 office

From: kurt greaves [mailto:k...@instaclustr.com]
Sent: Thursday, May 11, 2017 1:06 AM
To: Mark Furlong <mfurl...@ancestry.com>
Cc: user@cassandra.apache.org
Subject: Re: Repairs on 2.1.12

to clarify, what exactly was your repair command, and in reference to a ring 
did you mean the DC or the cluster, and has the repair been running for 2 weeks 
or is that in reference to the "ring"?

It would be helpful if you provided the relevant logs as well, also, the 
cassandra version you are running.
​


Re: Repairs on 2.1.12

2017-05-11 Thread kurt greaves
to clarify, what exactly was your repair command, and in reference to a
ring did you mean the DC or the cluster, and has the repair been running
for 2 weeks or is that in reference to the "ring"?

It would be helpful if you provided the relevant logs as well, also, the
cassandra version you are running.
​


Re: Repairs on 2.1.12

2017-05-10 Thread kurt greaves
never seen a repair loop, seems very unlikely. when you say "on a ring"
what do you mean? what arguments are you passing to repair?

On 10 May 2017 03:22, "Mark Furlong"  wrote:

I have a large cluster running a -dc repair on a ring which has been
running for nearly two weeks. When I review the logs I can see where my
tables are reporting as ‘fully synced’ multiple times. I’m looking for some
information to help me confirm that my repair is not looping and is running
properly.



*Mark Furlong*

Sr. Database Administrator

*mfurl...@ancestry.com *
M: 801-859-7427 <(801)%20859-7427>

O: 801-705-7115 <(801)%20705-7115>

1300 W Traverse Pkwy

Lehi, UT 84043





​[image: http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]


Repairs on 2.1.12

2017-05-09 Thread Mark Furlong
I have a large cluster running a -dc repair on a ring which has been running 
for nearly two weeks. When I review the logs I can see where my tables are 
reporting as ‘fully synced’ multiple times. I’m looking for some information to 
help me confirm that my repair is not looping and is running properly.

Mark Furlong

Sr. Database Administrator

mfurl...@ancestry.com
M: 801-859-7427
O: 801-705-7115
1300 W Traverse Pkwy
Lehi, UT 84043





​[http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]