truncate to the end, do not subtract fsw. This was actually truncating the log too short, which was recorrupting the log! this meant it would restore once, but then corrupt itself again - and also, it would rewind the log to before the views. Which I think was causing the flume locking bug
truncate to the end, do not subtract fsw. This was actually truncating the log too short, which was recorrupting the log! this meant it would restore once, but then corrupt itself again - and also, it would rewind the log to before the views. Which I think was causing the flume locking bug

flumedb/flumelog-offset