Hi David,
Once after file write completes (fd closed) bitrot process will wait for
120 seconds and if there no fd is opened for the file it will trigger the
signer process.
considering the signer, process start and end time file read speed was <
250KB/s.
To increase bitrot signer read speed
Hi David,
I have also tested the bitrot signature process by default it takes < 250
KB/s.
regards
Amudhan P
On Fri, Mar 1, 2019 at 1:19 PM David Spisla wrote:
> Hello folks,
>
> I did some observations concerning the bitrot daemon. It seems to be that
> the bitrot signer is signing files
Hello Amudhan,
Am Fr., 1. März 2019 um 14:56 Uhr schrieb Amudhan P :
> Hi David,
>
> Once after file write completes (fd closed) bitrot process will wait for
> 120 seconds and if there no fd is opened for the file it will trigger the
> signer process.
>
Yes, I already know this. But there is
Hello Amudhan,
What does exactly mean "it takes < 250KB/s"?
I figured out this discussion between you and Kotresh:
https://lists.gluster.org/pipermail/gluster-users/2016-September/028354.html
Kotresh mentioned there that the problem is because for some files fd
process are still up in the brick
