Got it, that seems entirely reasonable.
Anthony
> On Dec 3, 2021, at 7:37 AM, Jakov Varenina wrote:
>
> Hi Anthony,
>
> Not sure normally, but at the moment when we were investigating the issue
> there were 21 .crf files in disk-store (on one server) with default
> max-oplog-size (1GB) and
.apache.org<mailto:dev@geode.apache.org>
mailto:dev@geode.apache.org>>
*Subject:* Re: Question related to orphaned .drf files in disk-store
Hi Dan and all,
Just to provide you the additional picture that better represents the severity
of the problem with pendingKrfsTag. So when after you check
2021 5:53 AM
*To:* dev@geode.apache.org<mailto:dev@geode.apache.org>
mailto:dev@geode.apache.org>>
*Subject:* Re: Question related to orphaned .drf files in disk-store
Hi Dan and all,
Just to provide you the additional picture that better represents the severity
of the problem with pendingKr
21 5:53 AM
*To:* dev@geode.apache.org
*Subject:* Re: Question related to orphaned .drf files in disk-store
Hi Dan and all,
Just to provide you the additional picture that better represents the
severity of the problem with pendingKrfsTag. So when after you check
the second picture in below
add up.
-Dan
From: Jakov Varenina
Sent: Tuesday, November 30, 2021 5:53 AM
To: dev@geode.apache.org
Subject: Re: Question related to orphaned .drf files in disk-store
Hi Dan and all,
Just to provide you the additional picture that better represents the
The .drf file contains destroy records for entries in any older oplog. So even
if the corresponding .crf file has been deleted, the .drf file with the same
number still needs to be retained until the older .crf files are all deleted.
7680 does seem like a lot of oplogs. That data structure is ju
