cruzdb/zlog

add throttle and timeout to view refreshing

dotnwat opened this issue · 1 comments

add throttle and timeout to view refreshing

the idea here is to identify when we want to update immediately (e.g. right after a proposal) and when we want to go with a back off algorithm. for instance if we see a newish epoch in an object then we can then wake up immediately and start a backoff if we are the first waiter. if we aren't the first waiter, then we can piggy pack on the existing back off instance / round. if a waiter shows up with a new max epoch then do an immediate refresh. this last part is really just a heuristic maybe not needed or may need improving.