Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 【TiDBer 唠嗑茶话会 67】不懂就问系列，你有哪些 TiDB 的问题不管你当提不提，你都可以提出来~
Does anyone have any questions about TiDB? In this session, no matter what aspect or dimension of TiDB you have questions about, you can bring them up! Questions that you usually “don’t dare to ask” can be asked in this session! (PS: No guarantee of answers 
)
In this chat session, all TiDBers have the chance to be selected as: [Question Master] and [Ti Expert]
Selection Rules:
[Question Master]: Ask whenever you don’t understand
Selection criteria: The person who asks the most TiDB-related questions in this chat session, based on the quantity and quality of the questions (excluding unrelated questions).
[Ti Expert]: Quick (fast response), Accurate (precise answers), and Thorough (most comprehensive responses)
Selection criteria: The person who answers the most questions from others in this chat session, based on the three dimensions of quick, accurate, and thorough responses.
[Question Master] and [Ti Expert] will each receive a choice of either [Ti Red Camping Gear] or [TiDB Large Smart Leather Mouse Pad (Heatable)].
This Session’s Topic:
Ask anything you don’t understand about TiDB, whether you usually ask it or not, you can bring it up~
Event Rewards:
Participation Award:
Participate in this chat session to earn 30 points~
[Master and Expert] Rewards
[Ti Red Camping Gear] & [TiDB Large Smart Leather Mouse Pad (Heatable)], choose one
Ti Red Camping Gear:
TiDB Large Smart Leather Mouse Pad (Heatable):
Event Duration:
2023.4.19-2023.4.28~
How much has the performance improved in TiDB 6.6 or 7.0 compared to previous versions (even though they are not LTS versions)?
The scenarios it adapts to have increased, and the new capabilities also offer more uses. You can also wait for the 7.1.X LTS, which is about to be released…
Here’s a design question:
If one of the TiKV nodes has a disk failure and cannot write, the 3 replicas seem perfect and can temporarily support for a while, but over time, the entire cluster becomes unavailable.
I upgraded from v4.0.11 to v6.5.1 and used count(id) to count the entire table data. Why is there no significant improvement? I’ve upgraded two versions already.
I am currently facing a situation: 3 TiKVs are taking turns to restart the service (TiKV) due to server issues. For now, it seems there are no problems, but I am not sure if this phenomenon has any major hidden risks?
Is it possible to use the fix method to add new features without affecting compatibility (although it might be a bit far-fetched 
)
Some people are already ahead
[Question Master] emphasizes @Ask if you don’t understand
Isn’t the major version iteration of TiDB too fast? Last year we just started using v5 in production, and this year v7 has been released. It makes me constantly hesitate whether to upgrade or not.
Are there many people using the commercial version of TiDB? I feel that Chinese companies still tend to use the free community version…
Some bugs have fix versions for commercial users, but not yet for community users.
If you can keep up with the version, do so. My suggestion is that the latest version minus 2 is the minimum requirement. For example, if version 7.0 is released, you can update to version 5.
Whether to choose the new version depends on:
- Whether the current version you are using has issues,
- Whether the issues can be resolved,
- Whether the new version has new features you need,
- Whether there are performance requirements.
Many banks and financial industries use the commercial version, while the internet and new economy industries tend to use the community version more. After POC abroad, they are more willing to purchase the commercial version.
My guess is that 3 replicas refer to 3 replicas without any issues. When one has a problem, it can be scaled up or down to maintain 3 healthy nodes. If one has a problem (it feels like only 2 replicas are available, which is no longer considered 3 replicas).
We understand that some users may feel a bit uncomfortable with the speed of TiDB version updates, but our version updates are aimed at continuously optimizing TiDB’s performance, fixing known issues, and adding new features to meet the ever-changing needs of users.
Before releasing a new version, we conduct thorough testing to ensure the stability and reliability of the new version. We also provide documentation and community support to ensure that users can smoothly upgrade to the new version. We hope to continuously provide a better experience for everyone. If you encounter any issues, feel free to post them on asktug~
Unresolved issues on askTUG, please help take a look, experts:
When we first started using TiDB, we had a setup of 3 TiDB and PD mixed nodes, 3 KV nodes, and 1 Dash node, totaling 7 machines. As our business grew, we frequently encountered OOM issues, IO, or load overload problems. The number of users and the amount of data didn’t increase much, but the machine configurations were upgraded multiple times, and the number of KV nodes increased to 6. It’s too resource-intensive for small and micro enterprises to handle.
Does anyone else in the TiDB community have similar experiences? Is it true that only those who are not short of money use TiDB?
|
username: TiDB社区小助手
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: