How to enable sync_log? Where to check?

Translated
1

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

Original topic: sync_log 如何开启？在哪里查询

| username: yulei7633

How to enable sync_log? Where to check it?
Using the query show config where name like '%sync%'; does not show the relevant parameter configuration.

2
| username: 啦啦啦啦啦 | Original post link

This is the pump setting, it should be true by default.

3
| username: 友利奈绪 | Original post link

TiDB’s sync_log refers to whether TiDB uses synchronous mode when writing Binlog to ensure the durability of the write. In TiDB, sync_log is enabled by default, which means that synchronous mode is used when writing Binlog to ensure the durability of the write.

If you need to check or modify the sync_log setting, you can edit TiDB’s configuration file tidb.toml. You can find the following parameter in the configuration file:

[binlog]
# ...
sync-log = true  # true means enabling synchronous mode for writing Binlog, false means disabling synchronous mode for writing Binlog
# ...

If sync_log is set to true, it means that synchronous mode for writing Binlog is enabled. If you want to disable synchronous mode for writing Binlog, you can set it to false.

After making the changes, save the configuration file and restart the TiDB service to make the configuration take effect. Please ensure to back up the original configuration before making any changes and proceed with caution.

4
| username: stephanie | Original post link

How can I find the configuration parameter sync-log?

5
| username: yulei7633 | Original post link

tiup cluster edit-config tidb-test
Indeed, it was found here, and it was written during the previous deployment.

image
image904×349 11.1 KB

But there is a problem, why can’t this parameter be found using show config where name like ‘%sync-log%’;?

6
| username: Kongdom | Original post link

I’m sorry to inform you that this configuration parameter has been removed starting from version V5.0.

7
| username: yulei7633 | Original post link

Thank you very much.

8
| username: Kongdom | Original post link

:handshake: :handshake: :handshake:
We used to rely heavily on this configuration to run TiDB on low-spec servers. However, after the configuration was removed, customers were forced to upgrade their servers and experienced a better user experience. Overall, it’s still great~ :yum:

9
| username: dba远航 | Original post link

Outdated parameters

10
| username: yulei7633 | Original post link

Forcing this parameter to true is a good thing and will not cause data loss issues. Thank you.

11
| username: 考试没答案 | Original post link

Version 7.5 still has it, there’s no deprecation notice.

12
| username: Soysauce520 | Original post link

In SQL, the show config command can only retrieve parameters for TiKV, TiDB, PD, and TiFlash. It cannot retrieve parameters for Pump, Drainer, or CDC. Use tiup show-config to see the configuration; if it is not found, it means the default configuration is being used, or you can find the config in the dashboard debugging section.

13
| username: Kongdom | Original post link

This directory no longer exists. Note that it is a configuration item in the raftstore section of the tikv configuration file.

14
| username: DBAER | Original post link

You can make a documentation suggestion and mark it.

15
| username: 路在何chu | Original post link

You cannot adjust this version. You can adjust it in version 4.0.

16
| username: virvle | Original post link

In the V7.5 documentation, it is already commented out.

17
| username: TiDBer_21wZg5fm | Original post link

The parameter has been deprecated and can be ignored.

18
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.