Clust_mgr is an important compnent of KunlunBase. It provides a HTTP API for KunlunBase users to do cluster management, provisioning and monitor work, so that uses can install a cluster, a kunlun-server node, a storage shard or a kunlun-storage node by calling such APIs. Such capability enables users to integrate KunlunBase management and provisioning as part of their existing application or GUIs. Cluster_mgr also provide other important cluster maintenance background work to make sure the KunlunBase clusters it serves can work efficiently and reliably.
2022-05-17 12:18:15: zhangjindong@zettadb.com created the issue
Currently, cluster_mgr first connects to the meta shard using account of pgx/pgx_pwd, then connects to the data shards using records in shard_nodes, this is not okay, since the recorded account is pgx/pgx_pwd, while this account does not have privileges for managing group repllication.
We need to use the account(clustmgr/clustmgr_pwd currently) recorded in cluster_mgr.cnf to connect all shards, and this accout is promised to have enough privileges.
The same rule applies to node_mgr, it can use acccount recorded in node_mgr.cnf to connect meta shard.
Issue migrated from trac ticket # 698 www.kunlunbase.com
component: cluster manager | priority: trivial
2022-05-17 12:18:15: zhangjindong@zettadb.com created the issue