人大金仓KingbaseES 服务进程（backend process）终止问题处理

最新推荐文章于 2024-05-27 10:45:47 发布
最新推荐文章于 2024-05-27 10:45:47 发布
阅读量2.3k 收藏
点赞数
分类专栏： 数据库 文章标签： kingbase 数据库 金仓数据库 Powered by 金山文档
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/arthemis_14/article/details/128566785
版权

案例说明：

如下图所示：KingbaseES服务进程结构

KingbaseES使用客户端/服务器的模型。 对于每个客户端的连接，KingbaseES主进程接收到客户端连接后，会为其创建一个新的服务进程。 KingbaseES 用服务进程来处理连接到数据库服务的客户端请求。 该进程负责实际处理客户端的数据库请求，连接断开时退出。当Client连接到数据库时，会有对应的kingbase的服务进程为其提供服务，如以下Client查询访问：

如下所示，操作系统对应的服务进程（backend process）:

当Client结束访问正常退出数据库连接时，对应的kingbase的服务进程也将结束；但是当客户端异常退出时，会导致数据库端的kingbase服务进程没有正常结束，并占用数据库资源，本案例将详细描述手工方式对服务进程（backend process）终止。手工结束backend process可以使用数据库工具或者操作系统的kill进程方式，但是不同方式对数据库造成的影响不同。

适用版本：

KingbaseES V8R3/R6

系统架构：

一、客户端访问

[kingbase@node1 bin]$ ./ksql -h 192.168.8.201-U system-W prod
Password: 
ksql (V8.0)
Type "help" for help.

prod=#  selectcount(*) from t1;
 count  
--------100000
(1row)

二、backend process终止方案

1、pg_terminate_backend（pid）方式

Tips：函数 pg_terminate_backend() 实际上是给进程发送了一个 SIGTERM 信号。

# 查询backend process状态信息
prod=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname |  pid  | usesysid | usename | application_name |  client_addr  | client_hostname | client_port |         backend_start         | xact_start |          quer
y_start          |         state_change          | wait_event_type | wait_event | state | backend_xid | backend_xmin |          query           |  backend_type  
-------+---------+-------+----------+---------+------------------+---------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+--------------------------+----------------16385| prod    |17100|10|system| kingbase_*&+_    |192.168.8.200||57476|2022-11-2915:04:57.131987+08||2022-11-2915
:05:05.526379+08|2022-11-2915:05:05.539018+08| Client          | ClientRead | idle  |||selectcount(*) from t1; | client backend
(1row)

#终止backend process对应的pid
prod=# select pg_terminate_backend(17100);
 pg_terminate_backend 
----------------------
 t
(1row)

#进程被终止
prod=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname | pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | xact_start | query_start | state_change | wait
_event_type | wait_event | state | backend_xid | backend_xmin | query | backend_type 
-------+---------+-----+----------+---------+------------------+-------------+-----------------+-------------+---------------+------------+-------------+--------------+-----------------+------------+-------+-------------+--------------+-------+--------------
(0rows)

#如下所示，数据库进程正常，对应的backend pross被安全终止
[root@node2 sys_log]# ps -ef |grep kingbase
kingbase 130891014:39 ?        00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase -D /db/kingbase/v8r6_054/data
kingbase 1309013089014:39 ?        00:00:00 kingbase: logger   
kingbase 1647413089014:59 ?        00:00:00 kingbase: checkpointer   
kingbase 1647513089014:59 ?        00:00:00 kingbase: background writer   
kingbase 1647613089014:59 ?        00:00:00 kingbase: walwriter   
kingbase 1647713089014:59 ?        00:00:00 kingbase: autovacuum launcher   
kingbase 1647813089014:59 ?        00:00:00 kingbase: stats collector   
kingbase 1647913089014:59 ?        00:00:00 kingbase: ksh writer   
kingbase 1648013089014:59 ?        00:00:00 kingbase: ksh collector   
kingbase 1648113089014:59 ?        00:00:00 kingbase: kwr collector   
kingbase 1648213089014:59 ?        00:00:00 kingbase: logical replication launcher   
kingbase 1710013089015:04 ?        00:00:00 kingbase: system prod 192.168.8.200(57476) idle
kingbase 1721212416015:05 pts/000:00:00 ./ksql -U system test
kingbase 1721413089015:05 ?        00:00:00 kingbase: system prod [local] idle

2、操作系统kill pid方式

#查询backend process状态信息
prod=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname |  pid  | usesysid | usename | application_name |  client_addr  | client_hostname | client_port |         backend_start         | xact_start |          quer
y_start          |         state_change          | wait_event_type | wait_event | state | backend_xid | backend_xmin |          query           |  backend_type  
-------+---------+-------+----------+---------+------------------+---------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+--------------------------+----------------16385| prod    |18424|10|system| kingbase_*&+_    |192.168.8.200||57480|2022-11-2915:15:26.813035+08||2022-11-2915
:15:28.912910+08|2022-11-2915:15:28.922719+08| Client          | ClientRead | idle  |||selectcount(*) from t1; | client backend
(1row)

#操作系统下执行kill pid结束进程
[root@node2 sys_log]# kill 18424

#如下所示，数据库进程正常，对应的backend pross被安全kill
[root@node2 sys_log]# ps -ef |grep kingbase
kingbase 130891014:39 ?        00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase -D /db/kingbase/v8r6_054/data
kingbase 1309013089014:39 ?        00:00:00 kingbase: logger   
kingbase 1647413089014:59 ?        00:00:00 kingbase: checkpointer   
kingbase 1647513089014:59 ?        00:00:00 kingbase: background writer   
kingbase 1647613089014:59 ?        00:00:00 kingbase: walwriter   
kingbase 1647713089014:59 ?        00:00:00 kingbase: autovacuum launcher   
kingbase 1647813089014:59 ?        00:00:00 kingbase: stats collector   
kingbase 1647913089014:59 ?        00:00:00 kingbase: ksh writer   
kingbase 1648013089014:59 ?        00:00:00 kingbase: ksh collector   
kingbase 1648113089014:59 ?        00:00:00 kingbase: kwr collector   
kingbase 1648213089014:59 ?        00:00:00 kingbase: logical replication launcher   
kingbase 1721212416015:05 pts/000:00:00 ./ksql -U system test
kingbase 1721413089015:05 ?        00:00:00 kingbase: system prod [local] idle

#在数据库视图中已经无此backend process记录
prod=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname | pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | xact_start | query_start | state_change | wait
_event_type | wait_event | state | backend_xid | backend_xmin | query | backend_type 
-------+---------+-----+----------+---------+------------------+-------------+-----------------+-------------+---------------+------------+-------------+--------------+-----------------+------------+-------+-------------+--------------+-------+--------------
(0rows)

3、操作系统kill -15 pid和数据库sys_ctl kill TERM PID

1）操作系统kill -15 pid

#查询backend process状态信息
test=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname |  pid  | usesysid | usename | application_name |  client_addr  | client_hostname | client_port |         backend_start         | xact_start |          quer
y_start          |         state_change          | wait_event_type | wait_event | state | backend_xid | backend_xmin |          query           |  backend_type  
-------+---------+-------+----------+---------+------------------+---------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+--------------------------+----------------16385| prod    |22955|10|system| kingbase_*&+_    |192.168.8.200||57498|2022-11-2915:44:29.993305+08||2022-11-2915
:44:32.090913+08|2022-11-2915:44:32.100617+08| Client          | ClientRead | idle  |||selectcount(*) from t1; | client backend
(1row)

#操作系统下执行kill -15 pid结束进程
[kingbase@node2 bin]$ kill -1522955 

[kingbase@node2 bin]$ ps -ef |grep kingbase

#如下所示，数据库进程正常，对应的backend pross被安全kill
kingbase 130891014:39 ?        00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase -D /db/kingbase/v8r6_054/data
kingbase 2219713089015:38 ?        00:00:00 kingbase: checkpointer   
kingbase 2219813089015:38 ?        00:00:00 kingbase: background writer   
kingbase 2219913089015:38 ?        00:00:00 kingbase: walwriter   
kingbase 2220013089015:38 ?        00:00:00 kingbase: autovacuum launcher   
kingbase 2220113089015:38 ?        00:00:00 kingbase: stats collector   
kingbase 2220213089015:38 ?        00:00:00 kingbase: ksh writer   
kingbase 2220313089015:38 ?        00:00:00 kingbase: ksh collector   
kingbase 2220413089015:38 ?        00:00:00 kingbase: kwr collector   
kingbase 2220513089015:38 ?        00:00:00 kingbase: logical replication launcher   
kingbase 2244412416015:40 pts/000:00:00 ./ksql -U system test
kingbase 2244513089015:40 ?        00:00:00 kingbase: system test [local] idle

#在数据库视图中已经无此backend process记录
test=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname | pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | xact_start | query_start | state_change | wait
_event_type | wait_event | state | backend_xid | backend_xmin | query | backend_type 
-------+---------+-----+----------+---------+------------------+-------------+-----------------+-------------+---------------+------------+-------------+--------------+-----------------+------------+-------+-------------+--------------+-------+--------------
(0rows)

2）数据库sys_ctl kill TERM pid

#查询backend process状态信息
test=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname |  pid  | usesysid | usename | application_name |  client_addr  | client_hostname | client_port |         backend_start         | xact_start |          quer
y_start          |         state_change          | wait_event_type | wait_event | state | backend_xid | backend_xmin |          query           |  backend_type  
-------+---------+-------+----------+---------+------------------+---------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+--------------------------+----------------16385| prod    |22443|10|system| kingbase_*&+_    |192.168.8.200||57494|2022-11-2915:40:42.804868+08||2022-11-2915
:40:44.972533+08|2022-11-2915:40:44.985340+08| Client          | ClientRead | idle  |||selectcount(*) from t1; | client backend
(1row)

#执行数据库命令kill进程
[kingbase@node2 bin]$ ./sys_ctl kill  TERM 22443

#如下所示，数据库进程正常，对应的backend pross被安全kill
[kingbase@node2 bin]$ ps -ef |grep kingbase     
kingbase 130891014:39 ?        00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase -D /db/kingbase/v8r6_054/data
kingbase 2219713089015:38 ?        00:00:00 kingbase: checkpointer   
kingbase 2219813089015:38 ?        00:00:00 kingbase: background writer   
kingbase 2219913089015:38 ?        00:00:00 kingbase: walwriter   
kingbase 2220013089015:38 ?        00:00:00 kingbase: autovacuum launcher   
kingbase 2220113089015:38 ?        00:00:00 kingbase: stats collector   
kingbase 2220213089015:38 ?        00:00:00 kingbase: ksh writer   
kingbase 2220313089015:38 ?        00:00:00 kingbase: ksh collector   
kingbase 2220413089015:38 ?        00:00:00 kingbase: kwr collector   
kingbase 2220513089015:38 ?        00:00:00 kingbase: logical replication launcher   
kingbase 2244412416015:40 pts/000:00:00 ./ksql -U system test
kingbase 2244513089015:40 ?        00:00:00 kingbase: system test [local] idle

#在数据库视图中已经无此backend process记录
test=# select*from sys_stat_activity where client_addr='192.168.8.200';
 datid | datname | pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | xact_start | query_start | state_change | wait
_event_type | wait_event | state | backend_xid | backend_xmin | query | backend_type 
-------+---------+-----+----------+---------+------------------+-------------+-----------------+-------------+---------------+------------+-------------+--------------+-----------------+------------+-------+-------------+--------------+-------+--------------
(0rows)

4、操作系统kill -3 pid和数据库sys_ctl kill QUIT PID

1）操作系统kill -3 pid

#查询backend process状态信息prod=#select*fromsys_stat_activitywhereclient_addr='192.168.8.200';datid|datname|pid|usesysid|usename|application_name|client_addr|client_hostname|client_port|backend_start|xact_start|query_start|state_change|wait_event_type|wait_event|state|backend_xid|backend_xmin|query|backend_type-------+---------+-------+----------+---------+------------------+---------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+---------------------------------------------------------------------+----------------16385|prod|18666|10|system|kingbase_*&+_|192.168.8.200||57486|2022-11-29 15:17:34.726155+08||2022-11-29 15:17:34.736202+08|2022-11-29 15:17:34.740584+08|Client|ClientRead|idle|||selectsettingfrompg_settingswherename='enable_u
pper_colname'|clientbackend(1row)#操作系统下执行kill -3 pid结束进程
[root@node2sys_log]# kill -3 18666#如下所示，除了对应的backend process被终止外，其余的后台辅助进程也被终止并重启
[root@node2sys_log]# ps -ef |grep kingbasekingbase130891014:39?00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase-D/db/kingbase/v8r6_054/datakingbase1309013089014:39?00:00:00 kingbase:loggerkingbase1721212416015:05pts/000:00:00./ksql-Usystemtestkingbase1879513089015:18?00:00:00 kingbase:startup#查看对应的sys_log日志（backend process被终止导致数据库的辅助进程也将重启）prod=#select*fromsys_stat_activitywhereclient_addr='192.168.8.200';WARNING:terminatingconnectionbecauseofcrashofanotherserverprocessDETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.serverclosedtheconnectionunexpectedlyThisprobablymeanstheserverterminatedabnormallybeforeorwhileprocessingtherequest.2022-11-29 15:18:06.741 CST [18666] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 15:18:06.741 CST [18666] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 15:18:06.741 CST [18666] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 15:18:06.742 CST [13089] LOG:serverprocess(PID18666)exitedwithexitcode22022-11-29 15:18:06.742 CST [13089] DETAIL:  Failed process was running:selectsettingfrompg_settingswherename='enable_upper_colname'2022-11-29 15:18:06.742 CST [13089] LOG:terminatinganyotheractiveserverprocesses2022-11-29 15:18:06.743 CST [17214] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 15:18:06.743 CST [17214] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 15:18:06.743 CST [17214] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 15:18:06.744 CST [16477] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 15:18:06.744 CST [16477] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 15:18:06.744 CST [16477] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 15:18:06.745 CST [13089] LOG:allserverprocessesterminated;reinitializing2022-11-29 15:18:06.823 CST [18795] LOG:databasesystemwasinterrupted;lastknownupat2022-11-29 14:59:17 CST2022-11-29 15:19:29.897 CST [18795] LOG:databasesystemwasnotproperlyshutdown;automaticrecoveryinprogress2022-11-29 15:19:30.063 CST [18795] LOG:redostartsat0/22935D82022-11-29 15:19:30.063 CST [18795] LOG:redowalsegmentcount22022-11-29 15:19:30.063 CST [18795] LOG:  invalid record length at 0/2293608:wanted24,got02022-11-29 15:19:30.063 CST [18795] LOG:redodoneat0/22935D82022-11-29 15:19:30.739 CST [13089] LOG:databasesystemisreadytoacceptconnections#数据库服务重启后
[root@node2sys_log]# ps -ef |grep kingbasekingbase130891014:39?00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase-D/db/kingbase/v8r6_054/datakingbase1309013089014:39?00:00:00 kingbase:loggerkingbase1721212416015:05pts/000:00:00./ksql-Usystemtestkingbase1895313089015:19?00:00:00 kingbase:checkpointerkingbase1895413089015:19?00:00:00 kingbase:backgroundwriterkingbase1895513089015:19?00:00:00 kingbase:walwriterkingbase1895713089015:19?00:00:00 kingbase:statscollectorkingbase1895813089015:19?00:00:00 kingbase:kshwriterkingbase1895913089015:19?00:00:00 kingbase:kshcollectorkingbase1896013089015:19?00:00:00 kingbase:kwrcollector

---如上所示，kill -3 pid用于终止backend process将给数据库带来极大的风险 。

2）数据库sys_ctl kill QUIT PID

#查询backend process状态信息test=#select*fromsys_stat_activitywhereclient_addr='192.168.8.200';datid|datname|pid|usesysid|usename|application_name|client_addr|client_hostname|client_port|backend_start|xact_start|query_start|state_change|wait_event_type|wait_event|state|backend_xid|backend_xmin|query|backend_type-------+---------+-------+----------+---------+------------------+---------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+--------------------------+----------------16385|prod|21894|10|system|kingbase_*&+_|192.168.8.200||57490|2022-11-29 15:36:10.034020+08||2022-11-29 15:36:13.902728+08|2022-11-29 15:36:13.917841+08|Client|ClientRead|idle|||selectcount(*)fromt1;|clientbackend(1row)#执行数据库命令sys_ctl kill QUIT终止backend process
[kingbase@node2bin]$./sys_ctlkillQUIT21894#如下所示，除了对应的backend process被终止外，其余的后台辅助进程也被终止并重启
[kingbase@node2bin]$ps-ef|grepkingbasekingbase130891014:39?00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase-D/db/kingbase/v8r6_054/datakingbase1309013089014:39?00:00:00 kingbase:loggerkingbase2189512416015:36pts/000:00:00./ksql-Usystemtestkingbase2207113089015:37?00:00:00 kingbase:startup#查看对应的sys_log日志（backend process被终止导致数据库的辅助进程也将重启）test=#select*fromsys_stat_activitywhereclient_addr='192.168.8.200';WARNING:terminatingconnectionbecauseofcrashofanotherserverprocessDETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.serverclosedtheconnectionunexpectedlyThisprobablymeanstheserverterminatedabnormallybeforeorwhileprocessingtherequest.2022-11-29 15:37:13.828 CST [21894] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 15:37:13.828 CST [21894] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 15:37:13.828 CST [21894] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 15:37:13.829 CST [13089] LOG:serverprocess(PID21894)exitedwithexitcode22022-11-29 15:37:13.829 CST [13089] DETAIL:  Failed process was running:selectcount(*)fromt1;2022-11-29 15:37:13.829 CST [13089] LOG:terminatinganyotheractiveserverprocesses2022-11-29 15:37:13.830 CST [21896] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 15:37:13.830 CST [21896] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 15:37:13.830 CST [21896] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 15:37:13.831 CST [18956] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 15:37:13.831 CST [18956] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 15:37:13.831 CST [18956] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 15:37:13.833 CST [13089] LOG:allserverprocessesterminated;reinitializing2022-11-29 15:37:13.933 CST [22071] LOG:databasesystemwasinterrupted;lastknownupat2022-11-29 15:19:30 CST2022-11-29 15:38:29.154 CST [22071] LOG:databasesystemwasnotproperlyshutdown;automaticrecoveryinprogress2022-11-29 15:38:29.232 CST [22071] LOG:redostartsat0/22936802022-11-29 15:38:29.232 CST [22071] LOG:redowalsegmentcount22022-11-29 15:38:29.232 CST [22071] LOG:  invalid record length at 0/22936B0:wanted24,got02022-11-29 15:38:29.232 CST [22071] LOG:redodoneat0/22936802022-11-29 15:38:29.767 CST [13089] LOG:databasesystemisreadytoacceptconnection

---如上所示，sys_ctl kill QUIT pid用于终止backend process将给数据库带来极大的风险 。

5、操作系统kill -9 pid

#查询backend process状态信息prod=#select*fromsys_stat_activitywhereclient_addr='192.168.8.200';datid|datname|pid|usesysid|usename|application_name|client_addr|client_hostname|client_port|backend_start|xact_start|query_start|state_change|wait_event_type|wait_event|state|backend_xid|backend_xmin|query|backend_type-------+---------+-------+----------+---------+-------------------+---------------+-----------------+-------------+-------------------------------+-------------------------------+-------------------------------+-------------------------------+-----------------+---------------------+--------+-------------+--------------+----------------------------------+------------------------------16385|prod|14114|10|system|kingbase_*&+_|192.168.8.200||57472|2022-11-29 14:48:06.372451+08|                          
     | 2022-11-29 14:50:16.618969+08 | 2022-11-29 14:50:16.627572+08 | Client          | ClientRead          | idle   |             |              | select count(*) from t1;
         | client backend
       
(1rows)#操作系统下执行kill -9 pid结束进程
[root@node2~]# kill -9  14114 #如下所示，除了对应的backend process被终止外，其余的后台辅助进程也被终止并重启
[root@node2~]# ps -ef |grep kingbase.......kingbase130891014:39?00:00:00/opt/Kingbase/ES/V8R6_054/KESRealPro/V008R006C005B0054/Server/bin/kingbase-D/db/kingbase/v8r6_054/datakingbase1309013089014:39?00:00:00 kingbase:loggerkingbase1401012416014:47pts/000:00:00./ksql-Usystemtestkingbase1565113089014:57?00:00:00 kingbase:startup#查看对应的sys_log日志（backend process被终止导致数据库的辅助进程也将重启）2022-11-29 14:58:00.093 CST [13089] LOG:serverprocess(PID14114)was terminated by signal 9:Killed2022-11-29 14:58:00.093 CST [13089] DETAIL:  Failed process was running:selectcount(*)fromt1;2022-11-29 14:58:00.093 CST [13089] LOG:terminatinganyotheractiveserverprocesses2022-11-29 14:58:00.093 CST [14602] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 14:58:00.093 CST [14602] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 14:58:00.093 CST [14602] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 14:58:00.095 CST [13095] WARNING:terminatingconnectionbecauseofcrashofanotherserverprocess2022-11-29 14:58:00.095 CST [13095] DETAIL:Thekingbasehascommandedthisserverprocesstorollbackthecurrenttransactionandexit,becauseanotherserverprocessexitedabnormallyandpossiblycorruptedsharedmemory.2022-11-29 14:58:00.095 CST [13095] HINT:Inamomentyoushouldbeabletoreconnecttothedatabaseandrepeatyourcommand.2022-11-29 14:58:00.384 CST [13089] LOG:allserverprocessesterminated;reinitializing2022-11-29 14:58:00.464 CST [15651] LOG:databasesystemwasinterrupted;lastknownupat2022-11-29 14:53:42 CST2022-11-29 14:59:16.706 CST [15651] LOG:databasesystemwasnotproperlyshutdown;automaticrecoveryinprogress2022-11-29 14:59:16.806 CST [15651] LOG:redostartsat0/22934882022-11-29 14:59:16.806 CST [15651] LOG:redowalsegmentcount22022-11-29 14:59:16.806 CST [15651] LOG:  invalid record length at 0/2293560:wanted24,got02022-11-29 14:59:16.806 CST [15651] LOG:redodoneat0/22935302022-11-29 14:59:17.563 CST [13089] LOG:databasesystemisreadytoacceptconnections

---如上所示，kill -9 pid用于终止backend process将给数据库带来极大的风险 。

三、总结

对于KingbaseES数据库中异常的backend proces可以采用手工方式终止，执行时选择的方式要注意对数据库带来的风险：

1）相对安全方式：pg_terminate_backend（pid）；kill pid；kill -15 pid；sys_ctl kill TERM pid。

2）不安全方式： kill -3 pid；sys_ctl kill QUIT pid；kill -9 pid。

注意：千万不要kill -9，SIGKILL没有信号处理函数，OS会直接停掉进程；Kingbase父进程发现子进程异常退出，会停掉所有进程，释放共享内存，

再重新申请共享内存，拉起所有进程。效果就等于异常重启，启动时肯定会需要时间redo，可能造成几分钟的停止服务。（除非后果可以接受，否则不要kill -9）。

沉舟侧畔千帆过_
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
人大金仓 KingbaseES V8驱动 kingbase8-8.2.0.jar
11-15
综上所述，"kingbase8-8.2.0.jar"是用于连接和操作人大金仓KingbaseES V8数据库的JDBC驱动程序，它提供了与数据库交互的全部功能，包括建立连接、执行SQL、处理结果集、事务管理和安全性控制等。在Java应用中使用此...
人大金仓KingbaseES V8R6完整文档
04-27
人大金仓KingbaseES是一款国内自主研发的高性能关系型数据库管理系统，尤其在政府和企事业单位中广泛应用。V8R6版本是其重要的一个迭代，提供了更加强大和稳定的数据存储与处理能力。本压缩包包含了一系列关于...
人大金仓数据库启动失败
rabbit_Q13的博客
05-02 1360
现象：发现是金仓数据库连接不上，通过客户端连接时出现类似的提示，如下：到服务里尝试启动服务，发现数据库服务无法启动，如下：尝试使用命令行启动，先查看应用路径：百度查询错误代码1063，发现原因很多，无从下手。
KingBase/人大金仓数据服务，linux及国产化服务器启动停止服务遇到的问题
小黄皇的博客
07-09 8122
重启服务器后，发现数据服务连接失败，先用 ps _ef|grep kingbase 查看了进程，果然服务没有启动，下到数据服务器安装目录下 /opt/Kingbase/ES/V8/Server/bin 打开终端，找到目录下的sys_ctl，运行 sys_ctl --help 可以看到该命令是用于初始化、启动、停止或控制Kingbase服务器的工具，例如启动金仓数据库服务： sys_ctl start _D /opt/Kingbase/ES/V8/data(自己的数据库路径) 再查看进程就可以看到服务已
人大金仓 KingBase查询死锁，释放死锁
最新发布
Xiaoweidumpb
05-27 444
【代码】人大金仓 KingBase查询死锁，释放死锁。
解决“本地计算机上的**服务启动后停止。某些服务在未由其他服务或程序使用时将自动停止”
abcjwg的专栏
11-06 1万+
最近在了解PostgreSQL相关，本地安装了PostgreSQL服务，创建一个函数通过pgAdmin进行调试，给函数设置断点时，提示 未启用调试器插件。请将插件添加到 shared_preload_libraries 并postgresql.conf文件中设置, 然后重新启动数据库服务器进行间接调试。 需在安装目录的文件“C:\PostgreSQL\10\data\postgresql.conf”设置shared_preload_libraries。10版本约在该文件的145行。当前设置...
解决：本地计算机上的MySQL服务启动后停止。某些服务在未由其他服务或程序使用时将自动停止
Yzz's blog
10-11 6131
新版MySQL免安装版未进行初始化，需要我们手动初始化
数据库人大金仓windows服务启动不了解决方案之一
曉儂
04-27 1万+
连接数据库提示 解决方案 进win服务启动kingbase8_instance启动该服务 手动启动不成功可以使用命令方式启动 找到数据库的安装目录。 data：数据库文件存放位置 Server\bin：数据库命令存放位置 切换到安装目录Server\bin文件夹目录下执行以下命令 cd D:\DBsoftware\KingbaseES_V008R003C002B0100_Win64_install\azbswj_\Server\bin 人大金仓安装data路径 sys_ctl.exe -D “人大金仓
已解决:本地计算机上的mysql服务启动停止后,某些服务在未由其他服务或程序使用时将自动停止
qq_45155853的博客
05-06 360
mysql版本：8.0.21 window10 解决方式： 找到my.ini文件 修改数据库存放目录文件夹名称（我的原为Data） 找到Data文件将重命名为data 重启动mysql服务 ​​​​​​​​​​​​​​​​​​​​​​​​​​​​ ...
【百试不厌】本地计算机上的mysql服务启动停止后,某些服务在未由其他服务或程序使用时将自动停止
weixin_44529753的博客
11-22 264
网上解决问题的方法涉及到数据库的还是谨慎考虑一下吧。。。 为了排错，三进宫了，为了方便，还是记录一下吧。 一、备份Mysql下的data文件和my.ini文件 二、删除这两个文件后在bin目录下输入cmd ****三、输入指令mysqld --initialize 初始化, 可能会卡一下，要等一下下，等下一行出来 四、初始化后，你会看到data文件夹，把之前的备份的替换上 五、wiin+r 后输入services.msc 打开服务Mysql（双击） 六、把保存my.ini粘贴回去，大工告成！，最好
人大金仓 KingbaseES V8 手册 及 sql语法手册
01-18
人大金仓KingbaseES是一款由中国人民大学开发的国产数据库管理系统，具有高性能、高安全性、高可用性等特点。KingbaseES V8是其第八个主要版本，提供了更加强大的功能和优化的性能。本手册和SQL语法手册是学习和操作...
人大金仓KingbaseES V7 V8快速安装指南.rar
09-10
人大金仓KingbaseES是一款由中国人民大学金仓信息技术股份有限公司开发的国产数据库管理系统，它在政府、企业等领域的数据存储和处理中广泛应用。本指南主要针对KingbaseES V7和V8版本，提供了详细的安装步骤和注意...
人大金仓KingbaseES V7参考手册
04-26
就是chm的手册，人大金仓的。手册我经常用，相比比较成熟的oracle、mysql手册差点意思，常用方法可参考，自定义函数什么的，请参考postgresql
基于 Windows 系统的 KingbaseES 数据库软件安装指南 (4.3. 静默安装、4.4. 服务管理）
arthemis_14的博客
07-11 549
4.3. 静默安装 4.3.1. 静默安装注意事项静默安装模式下，安装程序通过读取配置文件来安装数据库。安装包iso文件解压缩后，已存在silent.cfg模板文件，根据实际安装机器的情况修改参数值。配置文件的参数可参考下表修改。表 4.3.1 配置文件参数说明序号参数名默认值说明1CHOSEN_INSTALL _SETFull选择安装集，可选值包括：1）Full，完全安装2）Client，客户端安装3）Custom，定制安装2CHOSEN_FEATURE _LISTSERVER,MANAGER, DTS
本地计算机上的MySQL服务启动后停止。某些服务在未由其他服务或程序使用时将自动停止
m0_63717609的博客
11-22 177
在通过命令指示符下载MYSQL后，根本不能运行，提示 ”本地计算机上的MYSQL服务启动后停止xxxxx“ ，查了一下说要初始化数据库什么的，好麻烦！但是我在计算机管理-服务这里找到了一个叫MYSQL80的东西，本着试试的态度，对它点击启动后，navicat就能正常使用了。突然navicate打开爆出如题所示弹框，经过查询，那些什么通过 计算机管理-服务-找到MYSQL-没有就下载，有就启动，然后就能使用的方法，对我的情况没有用。
人大金仓KingbaseES V8R6 空闲事务会话超时自动终止机制
arthemis_14的博客
01-11 2308
以上演示了参数idle_in_transaction_session_timeout参数的功能。由此引申出另外一个参数，client_idle_timeout，这两个参数的区别在于client_idle_timeout规定了空闲会话超时中断时间，它不存在于事务里，默认是0，表示关闭。两个参数应该根据实际应用情况配合使用。可以由配置参数idle_in_transaction_session_timeout 事务处于空闲状态的时长，它有助于防止被遗忘的交易事务，避免长期持有锁，防止vacuum清理时间很长。
国产化适配之人大金仓数据库（一）安装启动测试
u013294657的博客
11-30 4656
本文章主要介绍金仓数据的安装、启动、数据库连接测试
服务异常：本地计算机上的服务启动后又停止。某些服务在未由其他服务或程序使用时将自动停止
热门推荐
My__CSDN的博客
05-13 1万+
1、安装服务成功之后启动服务报错，如下 2、主要问题还是代码报错，可以进入进入计算机管，选择：诊断-事件查看器-windows日志-应用程序，选择错误消息查看报错日志，如下 3、查看日志分析报错原因，解决错误，即可启动服务 ...
使用BENCHMARKSQL工具对kingbasees并发测试时kill掉主进程成功后存在子线程未及时关闭
arthemis_14的博客
07-01 263
关键字：Kingbase, benchmarksql,kill内容正文：问题：自动化进行TPCC测试时在第一次执行kill之后，主进程被kill掉有些子进程没kill 成功，因此触第二次检查进程时就发现还有kingbase的进程（实际是之前的子进程）在，第二次执行kill操作前有些被检测到的子进程又自动退出了，执行kill操作会出现找不到进程的错误解决方案：kill掉主进程后稍微等待时间让子线程结束后在进行下一步操作相关内容可参考官方产品用户文档中的路径：https://help.kingbase.com
KingBase(人大金仓)
08-18
KingBase(人大金仓)

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值