Frank Filz

Does this also occur on V5.x?

Please check if it's possible there are any patches since V4.3 that might have fixed this. Note that upstream we no longer support V4.x.

The server restart cases are handled by the fact that on restart, Ganesha reads the set of clients allowed to reclaim locks from the recovery data base. It then empties...

Ah, OK, you're concerned about the case where the client has started reclaiming (or at least done a new SETCLIENTID or EXCHANGEID but not completed reclaim after the first server...

Code contributions are always welcome. Otherwise, it's in my backlog.

Client preferably would not try to reclaim if it detects an edge case, but we can't totally trust client... So we should take more care, and I think we can...

I'm wondering exactly how this is going to work... We need to track clients that started to reclaim, but we need to make an atomic switch at the point we...

@zhitaoli-6 could you lay out a design for this covering all the recovery DB activity and how that relates to client activity and grace period etc. Perhaps in something like...

OK, I think that design looks good. I would like some additional opinions though.

At this point, the best bet might be to submit a patch and get review there.