Issues with Pump Scaling

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

Original topic: pump扩容问题

| username: TiDBer_yUoxD0vR

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed to cause the issue


The documentation states that when deploying a pump node, you need to update and restart tidb_servers. Is restarting the tidb server only necessary because the documentation sets enable_binlog = True? If the existing cluster already has enable_binlog = True, and you are just expanding the pump, is it unnecessary to restart the tidb server? I tested expanding the pump without restarting the tidb server and didn’t notice any issues in the monitoring and logs. Are there any potential risks?
[Encountered Issues: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

| username: Ming | Original post link

Yes, if you expand the pump, restarting it will only be to enable the binlog. You can see that using the tiup command to expand the pump alone will not involve restarting the tidb_server. However, this is somewhat complementary. If your cluster did not have a pump initially, you wouldn’t be able to enable the binlog alone. This is probably why it was written together.

| username: ShawnYan | Original post link

However, are you still using v3 now? When do you plan to upgrade?

| username: system | Original post link

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