Re: archive status ".ready" files may be created too early

On 8/6/21, 12:42 AM, "Kyotaro Horiguchi" <horikyota.ntt@gmail.com> wrote:
> In v5, NotifySegmentsReadyForArchive() still holds ArchNotifyLock
> including .ready file creations. Since the notification loop doesn't
> need the hash itself, the loop can be took out of the lock section?

I think that works.  This creates another opportunity for archive
status files to be created out of order, but as discussed elsewhere, I
think we have to be prepared for that regardless.  I moved the
notification loop out of the lock section in v6.

Nathan