Anthony Romano f1ead43482 wal: zero out wal tail past its first zero record ...

Whenever the WAL is opened for writes, it should write zeroes to its tail
starting from the first zero record. Otherwise, if there are entries past
the first zero record due to a torn write, any new writes that overlap the
old entries will lead to a garbage record on the tail and cause a CRC
mismatch.

2016-08-25 14:24:46 -07:00

..

walpb

*: regenerate proto with latest grpc-gateway

2016-07-27 13:21:03 -07:00

decoder.go

wal: update LICENSE header

2016-05-12 20:50:04 -07:00

doc.go

wal: update LICENSE header

2016-05-12 20:50:04 -07:00

encoder.go

wal: minor fixes

2016-06-06 09:43:19 -07:00

file_pipeline.go

wal: PrivateFileMode/DirMode as in pkg/fileutil

2016-06-10 15:20:57 -07:00

metrics.go

wal: update LICENSE header

2016-05-12 20:50:04 -07:00

record_test.go

wal: update LICENSE header

2016-05-12 20:50:04 -07:00

repair_test.go

wal: update LICENSE header

2016-05-12 20:50:04 -07:00

repair.go

wal: PrivateFileMode/DirMode as in pkg/fileutil

2016-06-10 15:20:57 -07:00

util.go

wal: don't warn when opening wal directory with stale tmp files

2016-05-31 06:25:23 -07:00

wal_bench_test.go

wal: use bytes.Equal, other minor updates

2016-06-13 01:33:53 -07:00

wal_test.go

wal: test for truncation on torn writes

2016-08-25 14:24:46 -07:00

wal.go

wal: zero out wal tail past its first zero record

2016-08-25 14:24:46 -07:00