influxdb/generated_types/protos
Marco Neumann a5fc1c7d38 fix: collect min AND max in database checkpoints
This is required to correctly handle the following case:

1. There are two partitions A and B w/ a single write each (from the same
   sequencer).
2. We persist A:
   - The partition checkpoint for A will be empty because after persistence
     there will be nothing to replay (the single write is persisted and
     we're ready).
   - The database checkpoint that contains the global minimum of all ranges
     recognizes that for the sequencer there is indeed something left (the
     minimum sequence number from B).
3. DB restart happens, replay starts
4. We scan all persisted files, figure out that we have a DB checkpoint
   with a sequence minimum but (w/o the change in this commit) there is no
   maximum. Only partition checkpoints contain maxima, and the only partition
   checkpoint that was persisted was the one for partition A and that one was
   empty (see above).
5. So now how do we recover partition B?
2021-07-21 14:48:29 +02:00
..
com/github/influxdata/idpe/storage/read refactor: fix style errors 2021-02-23 10:55:09 +00:00
google feat: add google longrunning operations stubs (#959) 2021-03-10 17:34:07 +00:00
grpc/health/v1 feat: add basic gRPC health service (#862) 2021-02-25 13:24:12 +00:00
influxdata fix: collect min AND max in database checkpoints 2021-07-21 14:48:29 +02:00