Erik Hollensbe
Erik Hollensbe
the problem with assuming pre-existing locks from a new process is that it's terribly hard to determine whether or not that lock is stale or not.
Yes, the TTL refresh accomplishes “punching the timer”. Look at the lock/lock.go code… AcquireTTLRefresh I think. What will happen is that if that code is no longer running, the lock...
If it doesn't terminate cleanly this doesn't work. On 17 Aug 2016, at 16:56, Yuva Shankar wrote: > Is it possible to free all the snap locks when volsupervisor gets...
@vvb right, I had previously made that the end-user's job but perhaps it is time to handle this ourselves. Perhaps using TTLs and then a lock for running volsupervisor would...
inline: > What actually happens in the case where a snapshot is triggered while > a snapshot is still running? I/O just gets punished until one/both > complete? > >...
if we use an expiry TTL it will automatically go away
as for ceph q's, like I explained this does not translate well to different storage architectures where we may or may not know whether a snapshot can be taken. I...
the former, imo. what do you think?
yep. I've updated the ticket with the design requirements. Please review @yuva29 @dseevr @vvb
to be clear, the former would _block_ new snap operations, not increase I/O