Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Support traffic replay

オープン
  • 何か問題がありますか？
#642 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@djshow832 がすでに取り組んでいます。

2024年8月26日 から。

評価

この issue はまだ評価されていません。

説明

feature request

Feature Request

Describe your feature request related problem

There are some cases when users want to capture the traffic on the production cluster and replay the traffic on a testing cluster:

  • A new TiDB version may have compatibility breakers, such as the statements failing, running slower, or resulting in different query results.
  • When the cluster runs unexpectedly, users want to capture the traffic so that they can investigate it later by replaying the traffic.
  • Test the maximum throughput of a scaled-up or scaled-down cluster using the real workload instead of Sysbench or TPCC.

Some traffic replay tools are widely used, including tcpcopy, mysql-replay, and query-playback. Tcpcopy and mysql-replay capture data like tcpdump, while query-playback is based on slow logs. Although some of them are built for MySQL, deploying them on the proxy instance also works.

However, they have some limitations:

  • Users need to learn the deployment and usage of these tools.
  • Tcpcopy only captures new connections, which is unfriendly for persistent connections. Mysql-replay can capture existing connections but it loses session states such as prepared statements and session variables, which may make replay fail.
  • The tools replay the traffic with one username and one current schema, which requires modification to the testing cluster.
  • Tcpcopy and mysql-replay don't support TLS because they can't decode the encrypted data.
  • Users need to verify the results and performance manually.

Describe the feature you'd like

Capturing traffic on one TiDB cluster and replaying the traffic on a new TiDB cluster to verify the SQL compatibility and performance of the new TiDB cluster.

Tasks

Design
  • #643
Traffic Capture

P1:

  • #645
  • #647
  • #674
  • #676
  • #672
  • #681

P2:

  • #726
  • #717
  • #719
  • #729
  • #722

P3:

  • Support more command types
Traffic Replay

P1:

  • #652
  • #654
  • #657
  • #659
  • #678
  • #687
  • #700

P2:

  • #711

P3:

  • Streaming reading and sending large commands
  • Track and limit the memory of pending commands
  • Support more auth plugins
  • Support replaying as fast as possible
  • #866
  • Support reading from MySQL slow logs
  • Support reading from tcpdump files
  • Support reading from TiDB statements summary tables
  • Support reading from MySQL statements summary tables
Comparison and Report

P1:

  • #661
  • #683
User Interface

P1:

  • #665
  • #667
  • #669
  • #685

P2:

  • #723
  • #735
  • #737
  • #740
  • #744
  • #742
  • #748

P3:

  • Show the estimated disk usage of the traffic files
  • Run as a replayer client
主要言語
Go
スター
73
フォーク
41
平均マージ
12時間 38分
マージ済み PR（30日）
21

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pingcap/tiproxy のほかの issue

pingcap/tiproxy の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。