非常感谢,使用这个方法,我在测试环境成功了,但在线上环境失败了.
在线上环境失败的原因是测试环境和线上环境的版本不同.
测试环境版本: Nebula Graph (Version 1.2.0)
线上环境版本:Nebula Graph (Version 2020.04.01-nightly)
在测试环境,调用 metad 服务的 replace 接口,然后重启 nebula 服务后,成功解决了问题,输出如下:
$ curl -Gs "http://172.16.43.103:11000/replace?from=172.16.43.198&to=172.16.43.103"
Replace Host successfully
$ ~/server/nebula/nebula/scripts/nebula.service restart all
[INFO] Stopping nebula-metad...
[INFO] Done
[INFO] Starting nebula-metad...
[INFO] Done
[INFO] Stopping nebula-graphd...
[INFO] Done
[INFO] Starting nebula-graphd...
[INFO] Done
[INFO] Stopping nebula-storaged...
[INFO] Done
[INFO] Starting nebula-storaged...
[INFO] Done
但在线上环境,当我调用 metad 服务的 replace 接口时,发生了错误,输出如下:
$ curl -G "http://172.16.0.40:45500/replace?from=172.16.0.21&to=172.16.0.40"
curl: (52) Empty reply from server
同时,在调用 metad 服务的 replace 接口时, metad 服务输出如下错误日志:
E0419 15:17:20.581399 21685 GeneratedCodeHelper.cpp:116] received invalid message from client: No version identifier... old protocol client in strict mode? sz=1195725856
E0419 15:17:20.581521 21685 GeneratedCodeHelper.cpp:73] invalid message from client in function process
E0419 15:17:20.581599 21685 HeaderServerChannel.cpp:114] Received invalid request from client: N6apache6thrift9transport19TTransportExceptionE: Header transport frame is too large: 1718775661 (hex 0x66726f6d, ascii 'from') (transport N6apache6thrift5async12TAsyncSocketE, address 172.16.0.40, port 48484)
我该如何解决这个错误呢,或者有没有办法修改 Nebula Graph (Version 2020.04.01-nightly) 中 metad 服务中的机器信息呢