davidby-influx

One thing to note is that issue is really two issues: OSS backup and enterprise backup (there is an engineering assistance request that has been closed in favor of tracking...

Backup timings in seconds comparing the default localhost:8088 and the `-host 127.0.0.1:8088` parameter. Backups are about 6 GB. There may be differences between `localhost` and 127.0.0.1 in going through the...

@lesam - we have the private issue mentioned above, which is a clearly pathological case, and a bug of some sort, then we have the general inefficiency of the backup...

My tests were just to check the comment above that the `-host` parameter made a huge difference, not an attempt to replicate the private issue linked above.

Internal developer notes: The use of `io.CopyN` [here](https://github.com/influxdata/influxdb/blob/888f82c9c80f77076c4d29032c736a2d2d7ffe93/pkg/tar/stream.go#L93) wraps the io.Writer in a `LimitReader` which prevents it from using alternate, perhaps faster interfaces, like `ReaderFrom`. The `io.CopyN` seems like a...

This is a known issue to the Flux team. Thanks for reporting it. You will see it in the release notes when it is fixed.

@foobar - can you make a unit test for this showing the problem?

With your logging turned up to `DEBUG`, look for any failures to open shards one Influx starting. This may be caused by a corrupt shard.

We have seen this when a disk fills up. That can cause corrupt files which persist after a disk resize or move to a larger disk.

@jeffreyssmith2nd - why would the default be `dbname` without an rp, instead of `dbname/autogen`?