tidb

Error 报告

This repository is ONLY used to solve problems related to DOCS-CN.
For other issues (TiDB, TiKV, etc), please move to other repositories.

Please answer the following questions before submitting your issue. Thanks!

最近测试 titan 性能，部署了 3 个节点的 tikv 集群，单独部署 titan，然后压测时发现，相同的数据，每个节点平均 30+ region 时，GET qps 大概 7w。调整 region 数后，每个 节点的 region 为1300+个，再次用同样的命令压测，GET qps 能达到 13w，请问 titan 是否有根据 region 数做并发控制呢？

Feature Request

Is your feature request related to a problem? Please describe:

The shared informer factory has called the WaitForCacheSync method, and it is no longer need to call it separately for each controller. We can remove Informer ().HasSynced because it will not be used.

It would be great to implement test case reduction strategies in SQLancer itself. The advantage of doing this in SQLancer, rather than an external tool like C-Reduce, is that we have all the information on whether a specific bug is still triggered (e.g., that two queries should yield the same result) and that the reduction can likely go further than when having an external interestingness test (e.

Error Report

This repository is ONLY used to solve issues related to DOCS.
For other issues (related to TiDB, PD, etc), please move to other repositories.

Please answer the following questions before submitting your issue. Thanks!

1. What is the URL/path of the document related to this issue?

   https://pingcap.com/docs/v2.1/releases/2.1.17/

Question

TiDB-Lightning doesn't need data to keep in order of _tidb_rowid, but we still sort data in the order of _tidb_rowid. This may increase TiDB's memory usage because we'll need a global sort in TiDB.

Please answer these questions before submitting your issue. Thanks!

1. What did you do?
   If possible, provide a recipe for reproducing the error.
   we didn't record store id when download/ingest sst failed.

2. What did you expect to see?
   the error log with store id.

3. What did you see instead?
   only the error.

4. What version of BR and TiDB/TiKV/PD are you using?

all version.

The best practices of reporting errors:

1. The error message should be more user-friendly. Bad case: The table 101 exceeds table size. Good case: The table tbl exceeds table size.
2. Provide workarounds if necessary. Bad case: The table tbl exceeds table size. Good case: The table tbl exceeds table size. Please try to turn up the value of the system variable tmp_table_size.
3. Define