Hi. I am running Influxdb 2.1 on a pi4 in docker. I am trying to create a backup via command line
Influx CLI 2.2.1 (git: 31ac783) build_date: 2021-11-09T21:24:22Z.
The command is:
then the backup starts, but 18 shards are “removed during backup” - and missing afterwards in the backup.
2022/01/02 18:47:09 INFO: Backing up TSM for shard 1
2022/01/02 18:47:59 INFO: Backing up TSM for shard 3
2022/01/02 18:49:17 INFO: Backing up TSM for shard 10
2022/01/02 18:50:25 INFO: Backing up TSM for shard 19
2022/01/02 18:52:18 INFO: Backing up TSM for shard 28
2022/01/02 18:54:09 INFO: Backing up TSM for shard 37
2022/01/02 18:55:47 INFO: Backing up TSM for shard 46
2022/01/02 18:56:41 INFO: Backing up TSM for shard 26
2022/01/02 18:56:41 WARN: Shard 26 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 27
2022/01/02 18:56:41 WARN: Shard 27 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 30
2022/01/02 18:56:41 WARN: Shard 30 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 31
2022/01/02 18:56:41 WARN: Shard 31 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 32
2022/01/02 18:56:41 WARN: Shard 32 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 33
2022/01/02 18:56:41 WARN: Shard 33 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 34
2022/01/02 18:56:41 WARN: Shard 34 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 35
2022/01/02 18:56:41 WARN: Shard 35 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 36
2022/01/02 18:56:41 WARN: Shard 36 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 39
2022/01/02 18:56:41 WARN: Shard 39 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 40
2022/01/02 18:56:41 WARN: Shard 40 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 41
2022/01/02 18:56:41 WARN: Shard 41 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 42
2022/01/02 18:56:41 WARN: Shard 42 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 43
2022/01/02 18:56:41 WARN: Shard 43 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 44
2022/01/02 18:56:41 WARN: Shard 44 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 45
2022/01/02 18:56:41 WARN: Shard 45 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 48
2022/01/02 18:56:41 INFO: Backing up TSM for shard 49
2022/01/02 18:56:41 WARN: Shard 49 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 50
2022/01/02 18:56:41 INFO: Backing up TSM for shard 51
2022/01/02 18:56:41 WARN: Shard 51 removed during backup
2022/01/02 18:56:41 INFO: Backing up TSM for shard 2
2022/01/02 18:56:41 INFO: Backing up TSM for shard 4
2022/01/02 18:56:42 INFO: Backing up TSM for shard 11
2022/01/02 18:56:42 INFO: Backing up TSM for shard 20
2022/01/02 18:56:42 INFO: Backing up TSM for shard 29
2022/01/02 18:56:42 INFO: Backing up TSM for shard 38
2022/01/02 18:56:42 INFO: Backing up TSM for shard 47
Is that inteded behaviour? How can I fix that? If tried this over several days, after rebooting and while stopping the other docker tasks (that access the database) - its always the (same?) 18 shards that fail.
I got the same today (using 2.1.1) . Is it possible that the shard that are being removed are not supposed to be there in the first place? I mean, that those shared should have been deleted because, for example, they fall outside of the Retention policy? Has anyone checked this?