Skip to content

Latest commit

 

History

History
141 lines (101 loc) · 6.11 KB

binlog-control.md

File metadata and controls

141 lines (101 loc) · 6.11 KB
Raw
title summary aliases
binlogctl
Learns how to use `binlogctl`.
/docs/dev/tidb-binlog/binlog-control/

binlogctl

Binlog Control (binlogctl for short) is a command line tool for TiDB Binlog. You can use binlogctl to manage TiDB Binlog clusters.

You can use binlogctl to:

  • Check the state of Pump or Drainer
  • Pause or close Pump or Drainer
  • Handle the abnormal state of Pump or Drainer

The following are its usage scenarios:

  • An error occurs during data replication or you need to check the running state of Pump or Drainer.
  • You need to pause or close Pump or Drainer when maintaining the cluster.
  • A Pump or Drainer process exits abnormally, while the node state is not updated or is unexpected. This affects the data replication task.

Download binlogctl

{{< copyable "shell-regular" >}}

wget https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz &&
wget https://download.pingcap.org/tidb-{version}-linux-amd64.sha256

To check the file integrity, execute the following command. If the result is OK, the file is correct.

{{< copyable "shell-regular" >}}

sha256sum -c tidb-{version}-linux-amd64.sha256

For TiDB v2.1.0 GA or later versions, binlogctl is integrated into the TiDB download package. For earlier versions, you need to download binlogctl separately:

{{< copyable "shell-regular" >}}

wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz &&
wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256

To check the file integrity, execute the following command. If the result is OK, the file is correct.

{{< copyable "shell-regular" >}}

sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256

Descriptions

Command line parameters:

Usage of binlogctl:
  -V    prints version and exit
  -cmd string
        operator: "generate_meta", "pumps", "drainers", "update-pump", "update-drainer", "pause-pump", "pause-drainer", "offline-pump", "offline-drainer", "encrypt" (default "pumps")
  -data-dir string
        meta directory path (default "binlog_position")
  -node-id string
        id of node, used to update some nodes with operations update-pump, update-drainer, pause-pump, pause-drainer, offline-pump and offline-drainer
  -pd-urls string
        a comma separated list of PD endpoints (default "http://127.0.0.1:2379")
  -show-offline-nodes
        include offline nodes when querying pumps/drainers
  -ssl-ca string
        Path of file that contains list of trusted SSL CAs for connection with cluster components.
  -ssl-cert string
        Path of file that contains X509 certificate in PEM format for connection with cluster components.
  -ssl-key string
        Path of file that contains X509 key in PEM format for connection with cluster components.
  -state string
        set node's state, can be set to online, pausing, paused, closing or offline.
  -text string
        text to be encrypted when using encrypt command
  -time-zone Asia/Shanghai
        set time zone if you want to save time info in savepoint file; for example, Asia/Shanghai for CST time, `Local` for local time

Command examples:

  • Check the state of all the Pump or Drainer nodes.

    Set cmd to pumps or drainers. For example:

    {{< copyable "shell-regular" >}}

    bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd pumps
    [2019/04/28 09:29:59.016 +00:00] [INFO] [nodes.go:48] ["query node"] [type=pump] [node="{NodeID: 1.1.1.1:8250, Addr: pump:8250, State: online, MaxCommitTS: 408012403141509121, UpdateTime: 2019-04-28 09:29:57 +0000 UTC}"]

    {{< copyable "shell-regular" >}}

    bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd drainers
    [2019/04/28 09:29:59.016 +00:00] [INFO] [nodes.go:48] ["query node"] [type=drainer] [node="{NodeID: 1.1.1.1:8249, Addr: 1.1.1.1:8249, State: online, MaxCommitTS: 408012403141509121, UpdateTime: 2019-04-28 09:29:57 +0000 UTC}"]

  • Pause or close Pump or Drainer.

    You can use the following commands to pause or close services:

    Command Description Example
    pause-pump Pause Pump bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd pause-pump -node-id ip-127-0-0-1:8250
    pause-drainer Pause Drainer bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd pause-drainer -node-id ip-127-0-0-1:8249
    offline-pump Close Pump bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd offline-pump -node-id ip-127-0-0-1:8250
    offline-drainer Close Drainer bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd offline-drainer -node-id ip-127-0-0-1:8249

    binlogctl sends the HTTP request to the Pump or Drainer node. After receiving the request, the node executes the exiting procedures accordingly.

  • Modify the state of a Pump or Drainer node in abnormal states.

    When a Pump or Drainer node runs normally or when it is paused or closed in the normal process, it is in the normal state. In abnormal states, the Pump or Drainer node cannot correctly maintain its state. This affects data replication tasks. In this case, use binlogctl to repair the state information.

    To update the state of a Pump or Drainer node, set cmd to update-pump or update-drainer. The state can be paused or offline. For example:

    {{< copyable "shell-regular" >}}

    bin/binlogctl -pd-urls=http://127.0.0.1:2379 -cmd update-pump -node-id ip-127-0-0-1:8250 -state paused

    Note:

    When a Pump or Drainer node runs normally, it regularly updates its state to PD. The above command directly modifies the Pump or Drainer state saved in PD; therefore, do not use the command when the Pump or Drainer node runs normally. For more information, refer to TiDB Binlog FAQ.