obproxy部署完后如何修改listen_port

【 使用环境 】生产环境
【 OBproxy】
【 obproxy (OceanBase 4.3.4.0 1) 】
【问题描述】使用obd cluster edit-config DataWarehouse修改 obproxy-ce的listen_port后,在执行obd cluster reload DataWarehouse时候,报:


打印日志:

# obd display-trace a2b9cec8-5632-11f0-ab3a-000c29f9bdb3
[2025-07-01 12:19:52.693] [DEBUG] - cmd: ['DataWarehouse']
[2025-07-01 12:19:52.693] [DEBUG] - opts: {}
[2025-07-01 12:19:52.693] [DEBUG] - mkdir /root/.obd/lock/
[2025-07-01 12:19:52.693] [DEBUG] - unknown lock mode 
[2025-07-01 12:19:52.693] [DEBUG] - try to get share lock /root/.obd/lock/global
[2025-07-01 12:19:52.693] [DEBUG] - share lock `/root/.obd/lock/global`, count 1
[2025-07-01 12:19:52.693] [DEBUG] - Get Deploy by name
[2025-07-01 12:19:52.693] [DEBUG] - mkdir /root/.obd/cluster/
[2025-07-01 12:19:52.694] [DEBUG] - mkdir /root/.obd/config_parser/
[2025-07-01 12:19:52.694] [DEBUG] - try to get exclusive lock /root/.obd/lock/deploy_DataWarehouse
[2025-07-01 12:19:52.694] [DEBUG] - exclusive lock `/root/.obd/lock/deploy_DataWarehouse`, count 1
[2025-07-01 12:19:52.700] [DEBUG] - Deploy status judge
[2025-07-01 12:19:52.700] [ERROR] Deploy `DataWarehouse` need restart
[2025-07-01 12:19:52.700] [ERROR] Use `obd cluster restart DataWarehouse --wp` to make changes take effect.
[2025-07-01 12:19:52.703] [DEBUG] - exclusive lock /root/.obd/lock/deploy_DataWarehouse release, count 0
[2025-07-01 12:19:52.703] [DEBUG] - unlock /root/.obd/lock/deploy_DataWarehouse
[2025-07-01 12:19:52.703] [DEBUG] - share lock /root/.obd/lock/global release, count 0
[2025-07-01 12:19:52.703] [DEBUG] - unlock /root/.obd/lock/global
[2025-07-01 12:19:52.703] [INFO] See https://www.oceanbase.com/product/ob-deployer/error-codes .
[2025-07-01 12:19:52.703] [INFO] Trace ID: a2b9cec8-5632-11f0-ab3a-000c29f9bdb3
[2025-07-01 12:19:52.703] [INFO] If you want to view detailed obd logs, please run: obd display-trace a2b9cec8-5632-11f0-ab3a-000c29f9bdb3

我尝试了 obd cluster restart DataWarehouse时候,能成功重启,但listen_port 依然是2883.
我又尝试使用连入obclient -uroot@sys#DataWarehouse -h10.10.10.1 -P2883 -p 后使用 ALTER PROXYCONFIG SET listen_port = '3306'; 然后重启集群后 又恢复了 2883端口,请问obproxy真正配置在哪个地方或如何正确配置。

1 个赞

这边测试一下稍等

1 个赞

已经复现出来了,这边咨询下研发看看是什么原因

好的谢谢,我尝试解决了一天,发现可能是底层bug,故此寻求帮助。

等下个版本的obd发版后,可以进行edit-config方式进行修改