Zach BrownandZach Brown e88b5732ad scoutfs: track trans seq in btree ...

Currently the server tracks the outstanding transaction sequence numbers
that clients have open in a simple list in memory.  It's not properly
cleaned up if a client unmounts and a new server that takes over
after a crash won't know about open transaction sequence numbers.

This stores open transaction sequence numbers in a shared persistent
btree instead of in memory.  It removes tracking for clients as they
send their farewell during unmount.  A new server that starts up will
see existing entries for clients that were created by old servers.

This fixes a bug where a client who unmounts could leave behind a
pending sequence number that would never be cleaned up and would
indefinitely limit the visibility of index items that came after it.

Signed-off-by: Zach Brown <zab@versity.com>

2019-04-12 10:54:07 -07:00

kmod

scoutfs: track trans seq in btree

2019-04-12 10:54:07 -07:00

S

Description

No description provided

7.7 MiB

Languages

C 86.4%

Shell 10%

Roff 2.5%

TeX 0.8%

Makefile 0.3%