Re: Yet another repair solution

you want to try it out. Best Regards Marcus Olsson On tis, 2018-09-11 at 13:35 +, Marcus Olsson wrote: > Sure thing! > > Up until now it has been running in an OSGi environment, so among > other > things I'm working towards both OSGi and a standalone application. >

Re: Yet another repair solution

(and LWT) as a default backend for the lease management. It utilizes the repair history from Cassandra to determine repair state of tables in order to prioritize and schedule them. This also means that a manual "nodetool repair" would be counted towards the repair state of the tables. Best R

Re: Yet another repair solution

Great to see that there is an interest! As there currently are some internal dependencies etc. in place there is still some work to be done before we can publish it. I would expect this to take at least a few weeks, to try set the correct expectations. Best Regards Marcus Olsson On tis, 2018

Yet another repair solution

scussion? Best Regards Marcus Olsson

Re: JIRAs in Review

epair is completed. The applied patch is for 3.0.x, but before creating patches for 4.0 I thought it might be best to agree on the way forward (two solution proposals have been provided). Best Regards Marcus Olsson On fre, 2018-07-20 at 15:42 +1000, kurt greaves wrote: > Cheers Dinesh, not too

Re: STCS in L0 behaviour

Hi, In reply to Dikang Gu: For the run where we incorporated the change from CASSANDRA-11571 the stack trace was like this (from JMC): *Stack Trace* *Sample Count* *Percentage(%)* org.apache.cassandra.db.compaction.LeveledCompactionStrategy.getNextBackgroundTask(int) 229 11.983 -org.apach

STCS in L0 behaviour

the impact that repair has on LCS. For what version this could get in I think trunk would be enough since compaction is pluggable. -- Fwd: Footer Ericsson <http://www.ericsson.com/> *MARCUS OLSSON * Software Developer *Ericsson* Sweden marcus.ols...@ericsson.com <mailto

Re: Automatic scheduling & execution of repair

Added a JIRA for this where it can be discussed further: https://issues.apache.org/jira/browse/CASSANDRA-10070 BR Marcus Olsson On 08/13/2015 05:15 PM, Jonathan Ellis wrote: Now that we have LWT I think it could be self-coordinated. On Thu, Aug 13, 2015 at 6:45 AM, Marcus Olsson wrote: Hi

Automatic scheduling & execution of repair

have inside of Cassandra? To automatically schedule and run repairs, so that when you start up your cluster it basically maintains itself in terms of normal anti-entropy, with the possibility for manual configuration. BR Marcus Olsson

Re: Problem with upgrade to 2.1.3

We encountered the same problem, I put in a comment on the JIRA that caused it: https://issues.apache.org/jira/browse/CASSANDRA-8677 On 02/20/2015 09:38 AM, Jan Kesten wrote: Hi, I put this into an JIRA issue:CASSANDRA-8839