数据订阅 拉取耗时太长
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 25.1k
- Forks
- 5k
- Avg merge
- 4d 59m
- Merged PRs (30d)
- 7
Description
网络也正常
社区版 3.3.8.1
目前的架构是 6台服务器，其中5台tdengine server，第6台服务器 从其他5台通过数据订阅拉取数据，
每台服务器拉取开了5个线程，一共25个线程，
参数：
properties.setProperty(TMQConstants.CONNECT_TYPE, "ws");
properties.setProperty(TMQConstants.CONNECT_USER, "root");
properties.setProperty(TMQConstants.CONNECT_PASS, "taosdata");
properties.setProperty(TMQConstants.AUTO_OFFSET_RESET, "latest");
properties.setProperty(TMQConstants.MSG_WITH_TABLE_NAME, "true");
properties.setProperty(TMQConstants.ENABLE_AUTO_COMMIT, "true");
properties.setProperty(TMQConstants.AUTO_COMMIT_INTERVAL, "1000");
5台服务器的数据库创建语句
CREATE DATABASE tpih PRECISION 'ns' KEEP 150 VGROUPS 10 CACHEMODEL 'both' DURATION 24h BUFFER 16;
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported 17-second data-subscription pull in TDengine 3.3.8.1, reviewing the six-server topology, 25 consumer threads, WebSocket connection, auto-commit settings, and database definition. Compare pull latency and logs across the five source servers; done means identifying a supported cause or a reproducible performance issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100