greptimedb
greptimedb copied to clipboard
GreptimeTeam
Remove MySQL server in standalone mode
What type of enhancement is this?
Configuration
What does the enhancement do?
In standalone mode, there is no need to start MySQL server in both frontend and datanode. We can check running mode in datanode::server::Services and start MySQL server only in distribuited mode.
Implementation challenges
NA
@v0y4g3r just to clarify, is this designed to disable mysql server in datanode, or to remove mysql protocol support in standalone mode?
@v0y4g3r just to clarify, is this designed to disable mysql server in
datanode, or to remove mysql protocol support in standalone mode?
Both frontend and datanode will start MySQL server in standalone mode cuerently. This issue is about to disable MySQL only in datanode.
In standalone mode, why dn needs a mysql server? dn could only expose local grpc service for fe.
To be clarify:
- In standalone mode, dn starts grpc only
- In distributed mode, dn starts grpc and mysql
- In either mode, fe is communicating with dn via grpc
Mysql server in dn is only used for debugging purpose in distributed mode. Since the underlying env is unstable when dn and fe are deployed distributed, it’s good to directly manually check dn’s data. In standalone mode, because dn and fe are “packed” in one process, I think we don’t need to do that.
2022年11月19日 19:46，Lei, HUANG @.***> 写道：
@v0y4g3r https://github.com/v0y4g3r just to clarify, is this designed to disable mysql server in datanode, or to remove mysql protocol support in standalone mode?
Both frontend and datanode will start MySQL server in standalone mode. This issue is about to disable MySQL only in datanode.
— Reply to this email directly, view it on GitHub https://github.com/GreptimeTeam/greptimedb/issues/556#issuecomment-1320867165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHR2D2QXR5SE6NB5ZCQQETWJC4XVANCNFSM6AAAAAASDBYLBQ. You are receiving this because you are subscribed to this thread.
In standalone mode, why dn needs a mysql server? dn could only expose local grpc service for fe.
To be clarify:
- In standalone mode, dn starts grpc only
- In distributed mode, dn starts grpc and mysql
- In either mode, fe is communicating with dn via grpc
Mysql server in dn is only used for debugging purpose in distributed mode. Since the underlying env is unstable when dn and fe are deployed distributed, it’s good to directly manually check dn’s data. In standalone mode, because dn and fe are “packed” in one process, I think we don’t need to do that.
2022年11月19日 19:46，Lei, HUANG @.***> 写道：
@v0y4g3r https://github.com/v0y4g3r just to clarify, is this designed to disable mysql server in datanode, or to remove mysql protocol support in standalone mode?
Both frontend and datanode will start MySQL server in standalone mode. This issue is about to disable MySQL only in datanode.
— Reply to this email directly, view it on GitHub https://github.com/GreptimeTeam/greptimedb/issues/556#issuecomment-1320867165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHR2D2QXR5SE6NB5ZCQQETWJC4XVANCNFSM6AAAAAASDBYLBQ. You are receiving this because you are subscribed to this thread.
That's exactly what this issue is about 🙃