201.1 Trial Learning Assignment Post

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 201.1 试学作业贴

| username: rogerwang

This is the assignment submission post for course 201.1 lab operations.

Background:

Course link: https://learn.pingcap.com/learner/course/600003

Assignment Instructions:

  1. Please complete Lab 1 of the course: Introduction to Creating a Sandbox Cluster. Choose one of the methods from a/b/c/d.
  2. Follow the steps of the chosen method to complete the lab.
  3. Save a screenshot after the following steps.
Check the database version, connection ID, random number, and current time:

select version(), connection_id(), rand(), now();

Example screenshot:

Note: Please use a larger terminal font if possible, and only capture the “select version(), connection_id(), rand(), now();” command and its output.
4) Reply to this post with the screenshot.
5) After replying, use your connection_id() value as the answer and fill it in the exam lab question. In this example, it is 659827.

That’s it.

| username: TiDBer_L89 | Original post link

The tidb_gc_life_time parameter is used to control the garbage collection (GC) life cycle of TiDB. The default value is 10m, which means that data older than 10 minutes will be considered for GC. You can adjust this parameter according to your needs. For example, if you want to keep data for 24 hours, you can set it to 24h.

| username: ZhouRundong | Original post link

The default value of tidb_distsql_scan_concurrency is 15. You can adjust it according to your actual situation.

| username: TiDBer_FijKJb9n | Original post link

Submission

| username: kakaraka | Original post link

The default value of tidb_gc_life_time is 10m, which means that the data deleted 10 minutes ago can still be read. If you want to read data deleted 1 hour ago, you need to set tidb_gc_life_time to a value greater than 1 hour.

| username: TiDBer_xvp5MnTB | Original post link

| username: TiDBer_OoUWx9Iz | Original post link

| username: wuyu | Original post link

I think the main reason is that the default value of tidb_distsql_scan_concurrency is 15, which is relatively high. You can try reducing this value to see if it helps.

| username: TiDBer_3Rk6D1tc | Original post link

The default value of tidb_dml_batch_size is 2000. You can adjust it according to your needs.

| username: TiDBer_4L5f1rnK | Original post link

The image is not visible. Please provide the text you need translated.

| username: wuyu | Original post link

| username: TiDBer_sb7boGqA | Original post link

The image is not visible. Please provide the text you need translated.

| username: quan170 | Original post link

| username: TiDBer_nqxKNSWW | Original post link

The default value of tidb_enable_clustered_index is INT_ONLY in version 5.0.

| username: TiDBer_WOjcnfgd | Original post link

The image is not visible. Please provide the text you need translated.

| username: TiDBer_E5Ub18i8 | Original post link

The image is not available for translation. Please provide the text content directly.

| username: TiDBer_gePsrm50 | Original post link

The image you provided is not accessible. Please provide the text you need translated.

| username: TiDBer_xuxu | Original post link

The default value of tidb_dml_batch_size is 2000. You can adjust it according to your needs.

| username: TiDBer_iQFSh9zk | Original post link

The image you provided is not accessible. Please provide the text content for translation.

| username: TiDBer_aie47rih | Original post link

The image you provided is not accessible. Please provide the text content you need translated.