返回首页

gbase数据、南大通用产品文档:GBase8a_gbase_or_recursion_depth

更新日期:2024年09月11日

取值:调用递归深度
默认值:10
说明:调用递归深度,大于1 时为为最大递归深度,默认值为10。
修改方式:
可使用set 语句修改值也可在配置文件中修改值。
适用于session、
global
范围均可。

此项统计为访问频率最高的前10 个表的列表,
包括该表名称、
所在库名称、
访问该表的用户名列表及各自的访问占比。
开始时间和结束时间的跨度不得超过90 天。

GBaseDataStudio 管理工具手册
南大通用数据技术股份有限公司
- 113 -
图5- 454 TOP10 热点表

检查节点状态,集群状态应为normal,Coordinator 节点状态正常,确认被替换节点
是纯coordinator 节点后设置被替换节点状态为unavailable 状态。
操作步骤
步骤1:检查节点状态,集群状态应为normal,Coordinator 节点状态正常,确定被
替换的节点仅为Coordinator 节点。
$ gcadmin
CLUSTER STATE:
ACTIVE
===========================================================
=====
|
GBASE COORDINATOR CLUSTER INFORMATION
|
===========================================================
=====
|
NodeName
|
IpAddress
| gcware | gcluster | DataState |
----------------------------------------------------------------
| coordinator1 | 172.168.83.11 |
OPEN
|
OPEN
|
0
|
----------------------------------------------------------------
| coordinator2 | 172.168.83.12 |
OPEN
|
OPEN
|
0
|
----------------------------------------------------------------
| coordinator3 | 172.168.83.13 |
OPEN
|
OPEN
|
0
|
----------------------------------------------------------------
===========================================================
|
GBASE VIRTUAL CLUSTER INFORMATION
|
===========================================================
|
VcName
| DistributionId |
comment
|
-----------------------------------------------------------
|
vc1
|
1
| comment message for vc1 |
-----------------------------------------------------------
|
vc2
|
2
| comment message for vc2 |
-----------------------------------------------------------
2 virtual cluster: vc1, vc2
3 coordinator node

GBase 8a MPP Cluster 产品手册
4 管理员指南
文档版本953(2022-04-10)
南大通用数据技术股份有限公司
323
0 free data node
$ gcadmin showcluster vc vc1
CLUSTER STATE:
ACTIVE
VIRTUAL CLUSTER MODE:
NORMAL
==========================================================
|
GBASE VIRTUAL CLUSTER INFORMATION
|
==========================================================
|
VcName
| DistributionId |
comment
|
----------------------------------------------------------
|
vc1
|
1
| comment message for vc1 |
----------------------------------------------------------
===========================================================
=======
|
VIRTUAL CLUSTER DATA NODE INFORMATION
|
===========================================================
=======
|NodeName|
IpAddress
|DistributionId|gnode|syncserver|DataState|
------------------------------------------------------------------
| node1
|172.168.83.11|
1
|OPEN |
OPEN
|
0
|
------------------------------------------------------------------
| node2
|172.168.83.12|
1
|OPEN |
OPEN
|
0
|
------------------------------------------------------------------
2 data node
$ gcadmin showcluster vc vc2
CLUSTER STATE:
ACTIVE
VIRTUAL CLUSTER MODE:
NORMAL
===========================================================
|
GBASE VIRTUAL CLUSTER INFORMATION
|
===========================================================
|
VcName
| DistributionId |
comment
|
-----------------------------------------------------------
|
vc2
|
2
| comment message for vc2 |
-----------------------------------------------------------
===========================================================
=======
|
VIRTUAL CLUSTER DATA NODE INFORMATION
|
===========================================================

GBase 8a MPP Cluster 产品手册
4 管理员指南
文档版本953(2022-04-10)
南大通用数据技术股份有限公司
324
=======
|NodeName|
IpAddress
|DistributionId|gnode|syncserver|DataState|
------------------------------------------------------------------
| node1
|172.168.83.14|
2
|OPEN |
OPEN
|
0
|
------------------------------------------------------------------
| node2
|172.168.83.15|
2
|OPEN |
OPEN
|
0
|
------------------------------------------------------------------
2 data node
步骤2:
设置被替换节点状态为unavailable:
在操作系统的DBA 用户
(demo.options
文件中dbauser 参数指定的用户)下运行gcadmin setnodestate 命令设置要替换的节
点状态为unavailable。
$ gcadmin setnodestate 172.168.83.13 unavailable
after set node state into unavailable,can not set the state into normal,
must run gcadmin replacenodes to replace this node ,after that command node state
can return into normal.
you realy want to set node state into unavailable(yes or no)?
yes
get node data state by ddl fevent log start ......
get node data state by ddl fevent log end ......
get node data state by dml storage fevent log start ......
get node data state by dml storage fevent log end ......
check coordinator node data state by fevent log start ......
check coordinator node data state by fevent log end ......
set node [172.168.83.13] state to unavailable successful
查看集群状态:
$ gcadmin showcluster
CLUSTER STATE:
ACTIVE
===========================================================
=====
|
GBASE COORDINATOR CLUSTER INFORMATION
|
===========================================================
=====
|
NodeName
|
IpAddress
|
gcware
| gcluster|DataState |
----------------------------------------------------------------
| coordinator1| 172.168.83.11|
OPEN
|
OPEN
|
0
|
----------------------------------------------------------------
| coordinator2| 172.168.83.12|
OPEN
|
OPEN
|
0
|
----------------------------------------------------------------
| coordinator3| 172.168.83.13| UNAVAILABLE|
|
|
----------------------------------------------------------------

GBase 8a MPP Cluster 产品手册
4 管理员指南
文档版本953(2022-04-10)
南大通用数据技术股份有限公司
325
===========================================================
|
GBASE VIRTUAL CLUSTER INFORMATION
|
===========================================================
|
VcName
| DistributionId |
comment
|
-----------------------------------------------------------
|
vc1
|
1
| comment message for vc1 |
-----------------------------------------------------------
|
vc2
|
2
| comment message for vc2 |
-----------------------------------------------------------
2 virtual cluster: vc1, vc2
3 coordinator node
0 free data node
步骤3:删除被替换节点的feventlog。
$ gcadmin rmfeventlog 172.168.83.13
after rmfeventlog 172.168.83.13, fevent log will be removed, must run gcadmin
replacenodes to replace this node.
you realy want to remove node 172.168.83.13 fevent log(yes or no)?
yes
delete ddl event log on node 172.168.83.13 start
delete ddl event log on node 172.168.83.13 end
delete dml event log on node 172.168.83.13 start
delete dml event log on node 172.168.83.13 end
delete dml storage event log on node 172.168.83.13 start
delete dml storage event log on node 172.168.83.13 end