- Closes influxdata/DAR/issues/534
- Contact Support for assistance
- Add risks and technical details to truncate-shard command
- Add cautions to rebalance guide
- Add planning guidance for future data in schema_and_data_layout
Although a longer shard duration is more efficient whilst backfilling that's only true if the backfill is a one-off. If the shard is updated (whether via another backfill, deletion etc) again in future it will need to be recompacted - larger shards incur a larger resource cost.
Closes DAR#356
- having to force push to fix conflicts after the reorg.
Co-authored-by: Ben Tasker btasker@users.noreply.github.com
Co-authored-by: Jason Stirnaman <stirnamanj@gmail.com>
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
Jason Stirnaman
Jason Stirnaman
Ben Tasker
Scott Anderson