-
Problem report
-
Resolution: Unresolved
-
Major
-
None
-
7.0.17, 8.0.0alpha1 (master)
-
None
-
PgSQL 16.9/TSDB 2.20
-
Support backlog
Steps to reproduce:
- Decide to migrate from 1.3TB size installation to TSDB one
- follow official guide
Result:
- up to 2x of space can be required
Expected:
- Documentation states that up to 2x space required during migration (documentation)
- Server uses optimised approach with job 'config.maxchunks_to_compress' for initial compression, since default limit is 0 which means (unlimited) https://docs.tigerdata.com/api/latest/jobs-automation/alter_job/#optional-arguments (Server part). For example:
- if db is small - don't use adjustment (<100G)
- if db is bigger - adjust how many jobs can be needed initially to keep space usage below 30% level of a already used size.
- part of
-
ZBXNEXT-10189 Add information to the Frontend - System information, which version of the TSDB extension it can support
-
- Open
-