>
> Currently the value of phi_convict_threshold is not set which makes it to
> 8 (default) .
> Can this also cause hints buildup even when we can see that all nodes are
> UP ?
You can bump it up to 12 to reduce the sensitivity but it's likely GC
pauses causing it. Phi convict is the
Hi,
Full repair triggers anticompaction as well.
Only subrange repair doesn't trigger anticompaction, and in 4.0, AFAIK,
full repairs won't involve anticompaction anymore.
Cheers,
Le lun. 10 févr. 2020 à 19:17, Krish Donald a écrit :
> Thanks Jeff, But we are running repair using below
Thanks Jeff, But we are running repair using below command , how do we know
if incremental repair is enabled?
repair -full -pr
Thanks
KD
On Mon, Feb 10, 2020 at 10:09 AM Jeff Jirsa wrote:
> Incremental repair is splitting the data it repaired from the data it
> didnt repair so it can mark the
Incremental repair is splitting the data it repaired from the data it didnt
repair so it can mark the repaired data with a repairedAt timestamp
annotation on the data file / sstable.
On Mon, Feb 10, 2020 at 9:39 AM Krish Donald wrote:
> Hi,
>
> I noticed few messages in system.log like below:
Hi,
I noticed few messages in system.log like below:
INFO [CompactionExecutor:21] 2020-02-08 17:56:16,998
CompactionManager.java:677 - [repair #fb044b01-4ab5-11ea-a736-a367dba4ed71]
SSTable BigTableReader(path='xyz/mc-79976-big-Data.db')
((-8828745000913291684,8954981413747359495]) will be
Just to add , we are using 24GB heap size.
On Mon, 10 Feb 2020 at 09:08, Surbhi Gupta wrote:
> Hi Jon,
>
> We are on multi datacenter(On Prim) setup.
> We also noticed too many messages like below:
>
> DEBUG [GossipStage:1] 2020-02-10 09:38:52,953 FailureDetector.java:457 -
> Ignoring interval
Hi Jon,
We are on multi datacenter(On Prim) setup.
We also noticed too many messages like below:
DEBUG [GossipStage:1] 2020-02-10 09:38:52,953 FailureDetector.java:457 -
Ignoring interval time of 3258125997 for /10.x.x.x
DEBUG [GossipStage:1] 2020-02-10 09:38:52,954 FailureDetector.java:457 -
