版本升级问题
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 115
Description
我正在尝试将 IoTDB 从 1.3.2 升级到 2.0.4,过程中遇到几个问题:
1. 版本1.3.2的数据结构是否与2.0.4兼容?
2. 由于数据量较大,是否可以绕过 tools/export-data.sh 和 tools/import-data.sh 这个导入/导出数据工具,而是使用flush和load的方法直接将旧版 1.3.2 的 data 和 conf 目录指向 2.0.4 中?
3. 当前集群部署在三台服务器(1、2、3),其中 2 和 3 的 seed_config_node 配置为服务器 1。在升级过程中,是否应该按顺序升级并启动:先服务器 1 → 再服务器 2 → 最后服务器 3?
Contributor guide
Research direction
The issue asks about upgrading IoTDB 1.3.2 to 2.0.4, including compatibility of the data and conf directories, bypassing tools/export-data.sh and tools/import-data.sh, and the order for upgrading three servers. Start by locating the migration and cluster-upgrade guidance for these versions. Done means documenting confirmed compatibility, supported migration steps, and the safe server upgrade sequence.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100