ORACLE 6节点组成的ACFS文件系统异常的分析思路

近期遇到多次6节点集群的ACFS文件系统环境异常问题;如24日中午12点附近出现ACFS文件系统访问异常,通过查看集群ALERT日志、CSSD进程日志及OSW监控软件的日志,可以发现OSW监控软件在11:55-12:40分时没有收集到虚拟机LINUX主机的监控数据,同期数据库的CSSD进程也有与其它节点的私网信息已经丢失网络心跳,因此可以推断当时主机已经HANG住。

前环境为VMWARE虚拟机环境搭建6节点ORACLE GRID集群,使用ACFS文件系统为应用程序提供数据共享目录 /DATA,应用程序同时部署在6节点ORACLE GRID集群的对应主机上;未在集群环境运行ORACLE数据库。

对于近期两次典型问题分析如下:6/24日中午12点附近出现ACFS文件系统访问异常,通过查看集群ALERT日志、CSSD进程日志及OSW监控软件的日志,可以发现OSW监控软件在11:55-12:40分时没有收集到主机的监控数据,同期数据库的CSSD进程也有与其它节点的私网信息已经丢失网络心跳,因此可以推断当时主机已经HANG住。7/2日上午9点附近ACFS文件系统无法访问,当时OSW监控未开启;从集群ALERT日志来看当时有应用进程在使用/DATA目录 无法UNMOUNT,操作系统日志中有NFO: task java:12227 blocked for more than 120 seconds.信息,因未有其它有效信息,暂无法判断当时何种原因导致ACFS文件系统访问异常。

从具体的问题来看,ORACLE集群软件做为操作系统上层的软件,会受到底层操作系统OS以及更底层的VMWARE虚拟机环境的影响;由于几层系统之间监控日志粒度也不同,对于问题的分析带来了较大的复杂度;许多信息无法向下追踪去查找根本原因;

如下为分析过程:

1.集群 alert日志信息

2019-06-24 11:32:43.138:

[ctssd(3268)]CRS-2408:The clock on host node5 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.

2019-06-24 12:17:40.220:

[cssd(3148)]CRS-1612:Network communication with node node2 (2) missing for 50% of timeout interval.  Removal of this node from cluster in 14.560 seconds

2019-06-24 12:17:48.222:

[cssd(3148)]CRS-1611:Network communication with node node2 (2) missing for 75% of timeout interval.  Removal of this node from cluster in 6.560 seconds

2019-06-24 12:17:52.223:

[cssd(3148)]CRS-1610:Network communication with node node2 (2) missing for 90% of timeout interval.  Removal of this node from cluster in 2.560 seconds

2019-06-24 12:17:54.790:

[cssd(3148)]CRS-1601:CSSD Reconfiguration complete. Active nodes are node1 node3 node4 node5 node6 .

2019-06-24 12:18:38.016:

[cssd(3148)]CRS-1601:CSSD Reconfiguration complete. Active nodes are node1 node2 node3 node4 node5 node6 .

2019-06-24 12:33:48.943:

[cssd(3148)]CRS-1662:Member kill requested by node node6 for member number 5, group ocr_oanew-cluster

2019-06-24 12:33:48.959:

2.OSW监控数据

部分输入如下:

zzz ***Mon Jun 24 11:55:04 CST 2019

Tasks: 520 total,   1 running, 519 sleeping,   0 stopped,   0 zombie

Cpu(s):  1.9%us,  1.4%sy,  0.1%ni, 96.5%id,  0.0%wa,  0.1%hi,  0.1%si,  0.0%st

Mem:  24608192k total, 24400720k used,   207472k free,   450168k buffers

Swap: 16383992k total,   149316k used, 16234676k free,  3719180k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            

21449 root      20   0 14.9g 6.5g  16m S 34.6 27.6 311:40.89 java               

25134 root      20   0  109m 1212  892 D  5.9  0.0   0:50.58 find               

25763 root      10 -10     0    0    0 S  4.0  0.0   1:33.21 oks_comm           

 2522 root      20   0  157m  19m 6044 S  2.0  0.1 296:44.37 Xorg               

25569 root      30  10  238m  12m 5388 S  2.0  0.1   0:07.87 floaters           

32100 oracle    20   0  4636 1268  660 S  2.0  0.0   0:00.03 pidstat            

32110 oracle    20   0  4648 1284  660 S  2.0  0.0   0:00.03 pidstat            

32125 oracle    20   0 15300 1556  932 R  2.0  0.0   0:00.02 top                

32152 root      20   0 7407m  11m 7084 S  2.0  0.0   0:00.02 jstat              

  106 root      20   0     0    0    0 S  1.0  0.0   6:46.23 kblockd/0          

24801 oracle    20   0 1835m  38m  16m S  1.0  0.2   5:47.71 oraagent.bin       

25759 root      10 -10     0    0    0 S  1.0  0.0   0:04.91 oks_comm           

25760 root      10 -10     0    0    0 S  1.0  0.0   0:05.08 oks_comm           

25761 root      10 -10     0    0    0 S  1.0  0.0   0:04.99 oks_comm           

25762 root      10 -10     0    0    0 S  1.0  0.0   0:17.44 oks_comm           

27667 root      20   0  815m  19m  10m S  1.0  0.1 110:42.34 octssd.bin         

27731 root      RT   0  756m  90m  57m S  1.0  0.4 823:45.84 osysmond.bin       

    1 root      20   0 19364 1152  920 S  0.0  0.0   0:01.55 init               

    2 root      20   0     0    0    0 S  0.0  0.0   0:00.50 kthreadd           

    3 root      RT   0     0    0    0 S  0.0  0.0   1:37.36 migration/0        

    4 root      20   0     0    0    0 S  0.0  0.0   0:29.71 ksoftirqd/0        

    5 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0        

    6 root      RT   0     0    0    0 S  0.0  0.0   0:03.78 watchdog/0         

    7 root      RT   0     0    0    0 S  0.0  0.0   2:56.86 migration/1        

    8 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/1        

    9 root      20   0     0    0    0 S  0.0  0.0   0:40.01 ksoftirqd/1        

   10 root      RT   0     0    0    0 S  0.0  0.0   0:03.14 watchdog/1         

   11 root      RT   0     0    0    0 S  0.0  0.0   1:45.06 migration/2        

   12 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/2        

   13 root      20   0     0    0    0 S  0.0  0.0   0:30.71 ksoftirqd/2        

   14 root      RT   0     0    0    0 S  0.0  0.0   0:04.09 watchdog/2         

   15 root      RT   0     0    0    0 S  0.0  0.0   1:39.74 migration/3        

   16 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/3        

   17 root      20   0     0    0    0 S  0.0  0.0   0:15.30 ksoftirqd/3        

   18 root      RT   0     0    0    0 S  0.0  0.0   0:05.59 watchdog/3         

   19 root      RT   0     0    0    0 S  0.0  0.0   1:21.81 migration/4        

   20 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/4        

   21 root      20   0     0    0    0 S  0.0  0.0   0:24.62 ksoftirqd/4        

   22 root      RT   0     0    0    0 S  0.0  0.0   0:02.89 watchdog/4         

   23 root      RT   0     0    0    0 S  0.0  0.0   2:59.13 migration/5        

   24 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/5        

   25 root      20   0     0    0    0 S  0.0  0.0   0:29.33 ksoftirqd/5        

   26 root      RT   0     0    0    0 S  0.0  0.0   0:03.09 watchdog/5         

   27 root      RT   0     0    0    0 S  0.0  0.0   2:05.44 migration/6        

zzz ***Mon Jun 24 12:40:18 CST 2019

top - 12:40:19 up 38 days, 21:55,  7 users,  load average: 389.66, 349.33, 237.0

Tasks: 479 total,   2 running, 476 sleeping,   0 stopped,   1 zombie

Cpu(s): 12.3%us,  7.6%sy,  0.6%ni, 79.2%id,  0.2%wa,  0.0%hi,  0.1%si,  0.0%st

Mem:  24608192k total, 13600176k used, 11008016k free,   450344k buffers

Swap: 16383992k total,   121744k used, 16262248k free,  3679644k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            

 2079 root      20   0 1925m  60m 8280 R 195.2  0.3   0:01.97 java              

25787 root      20   0     0    0    0 S 29.7  0.0   0:13.62 acfsvol1           

 1785 root      30  10  233m 8240 5356 S 10.9  0.0   0:00.18 floaters           

 1780 root      20   0 1434m  33m  15m S  2.0  0.1   0:00.11 orarootagent.bi    

 1848 oracle    20   0  4660 1292  660 S  2.0  0.0   0:00.03 pidstat            

 1784 oracle    20   0  4708 1344  660 S  1.0  0.0   0:00.02 pidstat            

 2522 root      20   0  156m  17m 6044 S  1.0  0.1 296:44.88 Xorg               

23104 root      20   0 1914m  34m  16m S  1.0  0.1 168:20.21 ohasd.bin          

27384 oracle    RT   0 1346m 115m  54m S  1.0  0.5 390:41.65 ocssd.bin          

27731 root      RT   0  756m  90m  57m S  1.0  0.4 823:47.37 osysmond.bin       

    1 root      20   0 19364 1152  920 S  0.0  0.0   0:01.59 init               

    2 root      20   0     0    0    0 S  0.0  0.0   0:00.50 kthreadd           

    3 root      RT   0     0    0    0 S  0.0  0.0   1:37.36 migration/0        

    4 root      20   0     0    0    0 S  0.0  0.0   0:29.89 ksoftirqd/0        

    5 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0        

    6 root      RT   0     0    0    0 S  0.0  0.0   0:03.79 watchdog/0         

    7 root      RT   0     0    0    0 S  0.0  0.0   2:56.86 migration/1        

    8 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/1        

    9 root      20   0     0    0    0 S  0.0  0.0   0:40.02 ksoftirqd/1        

   10 root      RT   0     0    0    0 S  0.0  0.0   0:03.14 watchdog/1         

   11 root      RT   0     0    0    0 S  0.0  0.0   1:45.06 migration/2        

   12 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/2        

   13 root      20   0     0    0    0 S  0.0  0.0   0:30.72 ksoftirqd/2        

   14 root      RT   0     0    0    0 S  0.0  0.0   0:04.10 watchdog/2         

   15 root      RT   0     0    0    0 S  0.0  0.0   1:39.82 migration/3        

   16 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/3        

   17 root      20   0     0    0    0 S  0.0  0.0   0:15.30 ksoftirqd/3        

   18 root      RT   0     0    0    0 S  0.0  0.0   0:05.60 watchdog/3         

   19 root      RT   0     0    0    0 S  0.0  0.0   1:21.81 migration/4        

   20 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/4        

   21 root      20   0     0    0    0 S  0.0  0.0   0:24.64 ksoftirqd/4        

   22 root      RT   0     0    0    0 S  0.0  0.0   0:02.89 watchdog/4         

   23 root      RT   0     0    0    0 S  0.0  0.0   2:59.15 migration/5        

   24 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/5   

3.节点1 CSSD进程日志信息

2019-06-24 12:17:46.238: [    CSSD][2716677888]clssnmSendingThread: sent 5 status msgs to all nodes

2019-06-24 12:17:46.631: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349866/3359336954

2019-06-24 12:17:47.132: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349867/3359337454

2019-06-24 12:17:47.631: [    CSSD][2718254848]clssnmPollingThread: node node2 (2) at 75% heartbeat fatal, removal in 7.150 seconds

2019-06-24 12:17:47.631: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349867/3359337954

2019-06-24 12:17:48.132: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349868/3359338454

2019-06-24 12:17:48.631: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349868/3359338954

2019-06-24 12:17:49.132: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349869/3359339454

2019-06-24 12:17:49.631: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349869/3359339954

2019-06-24 12:17:50.132: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349870/3359340454

2019-06-24 12:17:50.631: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349870/3359340954

2019-06-24 12:17:51.132: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349871/3359341454

2019-06-24 12:17:51.240: [    CSSD][2716677888]clssnmSendingThread: sending status msg to all nodes

2019-06-24 12:17:51.240: [    CSSD][2716677888]clssnmSendingThread: sent 5 status msgs to all nodes

2019-06-24 12:17:51.632: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349871/3359341954

2019-06-24 12:17:52.133: [    CSSD][2727913216]clssnmvDiskPing: Writing with status 0x3, timestamp 1561349872/3359342454

2019-06-24 12:17:52.632: [    CSSD][2718254848]clssnmPollingThread: node node2 (2) at 90% heartbeat fatal, removal in 2.150 seconds,

seedhbimpd 1

    1. 7/2日问题分析

7/2日上午9点附近ACFS文件系统无法访问,当时OSW监控未开启;从集群ALERT日志来看当时有应用进程在使用/DATA目录 无法UNMOUNT,操作系统日志中有NFO: task java:12227 blocked for more than 120 seconds.信息,因未有其它有效信息,暂无法判断当时何种原因导致ACFS文件系统访问异常。

1.集群ALERT日志信息

2019-07-02 08:49:03.484:

[ctssd(3257)]CRS-2408:The clock on host node1 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.

[client(17179)]CRS-10001:02-Jul-19 09:04 ACFS-9153: Program '/app/weaver/jdk1.6.0_27/bin/java -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djava.system.class.loader=com.caucho.loader.SystemClassLoader -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Xmx6000m -Xms6000m -Xss256k -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+DisableExplicitGC -javaagent:wagent.jar -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremote -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremo

WARNING:Alert message too long

[client(17188)]CRS-10001:02-Jul-19 09:04 ACFS-9153: Program '/app/weaver/jdk1.6.0_27/bin/java -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djava.system.class.loader=com.caucho.loader.SystemClassLoader -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Xmx6000m -Xms6000m -Xss256k -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+DisableExplicitGC -javaagent:wagent.jar -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremote -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremo

WARNING:Alert message too long

[client(17190)]CRS-10001:02-Jul-19 09:04 ACFS-9252: The following process IDs have open references on mount point '/data':

[client(17192)]CRS-10001:5822

[client(17194)]CRS-10001:02-Jul-19 09:04 ACFS-9253: Failed to unmount mount point '/data'.  Mount point likely in use.

[client(17196)]CRS-10001:02-Jul-19 09:04 ACFS-9254: Manual intervention is required.

[client(17219)]CRS-10001:02-Jul-19 09:04 ACFS-9153: Program '/app/weaver/jdk1.6.0_27/bin/java -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djava.system.class.loader=com.caucho.loader.SystemClassLoader -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Xmx6000m -Xms6000m -Xss256k -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+DisableExplicitGC -javaagent:wagent.jar -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremote -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremo

WARNING:Alert message too long

[client(17225)]CRS-10001:02-Jul-19 09:04 ACFS-9153: Program '/app/weaver/jdk1.6.0_27/bin/java -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djava.system.class.loader=com.caucho.loader.SystemClassLoader -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Xmx6000m -Xms6000m -Xss256k -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+DisableExplicitGC -javaagent:wagent.jar -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremote -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Djava.awt.headless=true -Dresin.home=/app/weaver/Resin/ -Dresin.root=/app/weaver/Resin/ -Dcom.sun.management.jmxremo

WARNING:Alert message too long

[client(17227)]CRS-10001:02-Jul-19 09:04 ACFS-9252: The following process IDs have open references on mount point '/data':

[client(17229)]CRS-10001:5822

2.操作系统日志

Jul  2 08:59:49 node1 kernel: [<ffffffff81185d29>] do_sys_open+0x69/0x140

Jul  2 08:59:49 node1 kernel: [<ffffffff81185e40>] sys_open+0x20/0x30

Jul  2 08:59:49 node1 kernel: [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b

Jul  2 09:01:49 node1 kernel: INFO: task java:12227 blocked for more than 120 seconds.

Jul  2 09:01:49 node1 kernel:      Tainted: P           --------------- H  2.6.32-431.el6.x86_64 #1

Jul  2 09:01:49 node1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Jul  2 09:01:49 node1 kernel: java          D 000000000000000c     0 12227   5821 0x00000000

Jul  2 09:01:49 node1 kernel: ffff88033e49d8c8 0000000000000082 0000000200001000 ffff88062d4742c0

Jul  2 09:01:49 node1 kernel: ffff8803432b6d70 ffff880635ced090 ffff88062d4316c0 ffff8800283968a8

Jul  2 09:01:49 node1 kernel: ffff8805c7f25af8 ffff88033e49dfd8 000000000000fbc8 ffff8805c7f25af8

Jul  2 09:01:49 node1 kernel: Call Trace:

Jul  2 09:01:49 node1 kernel: [<ffffffff8109b4ee>] ? prepare_to_wait_exclusive+0x4e/0x80

Jul  2 09:01:49 node1 kernel: [<ffffffffa052cdb5>] OfsWaitEvent+0x225/0x290 [oracleacfs]

Jul  2 09:01:49 node1 kernel: [<ffffffff81065df0>] ? default_wake_function+0x0/0x20

Jul  2 09:01:49 node1 kernel: [<ffffffff8152784d>] ? bictcp_cong_avoid+0x2d/0x390

3.数据库CHM相关日志

[oracle@node6 node6]$ cat 02-JUL-2019-09:20:20.txt|grep "spent too much time"

dm-1 ior: 0.000 iow: 1117.912 ios: 279 qlen: 304 wait: 7914;';3:Time=07-02-19 09.15.20, Disk dm-1 spent too much time (7914 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdb ior: 0.000 iow: 1654.062 ios: 152 qlen: 23 wait: 573;';3:Time=07-02-19 09.15.20, Disk sdb spent too much time (573 msecs) waiting for I/O (> 100 msecs)' type: SYS

sda ior: 0.000 iow: 11.182 ios: 1 qlen: 0 wait: 119;';3:Time=07-02-19 09.15.40, Disk sda spent too much time (119 msecs) waiting for I/O (> 100 msecs)' type: SWAP

sda3 ior: 0.000 iow: 11.182 ios: 1 qlen: 0 wait: 119;';3:Time=07-02-19 09.15.40, Disk sda3 spent too much time (119 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-0 ior: 0.000 iow: 11.182 ios: 2 qlen: 1 wait: 412;';3:Time=07-02-19 09.15.40, Disk dm-0 spent too much time (412 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdc ior: 192.196 iow: 1.996 ios: 7 qlen: 2 wait: 377;';3:Time=07-02-19 09.15.40, Disk sdc spent too much time (377 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdc ior: 106.347 iow: 2.101 ios: 14 qlen: 0 wait: 148;';3:Time=07-02-19 09.16.20, Disk sdc spent too much time (148 msecs) waiting for I/O (> 100 msecs)' type: SYS

sda ior: 0.000 iow: 13.605 ios: 3 qlen: 3 wait: 937;';3:Time=07-02-19 09.16.40, Disk sda spent too much time (937 msecs) waiting for I/O (> 100 msecs)' type: SWAP

sda3 ior: 0.000 iow: 13.605 ios: 3 qlen: 3 wait: 937;';3:Time=07-02-19 09.16.40, Disk sda3 spent too much time (937 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-1 ior: 0.000 iow: 24.811 ios: 6 qlen: 14 wait: 1565;';3:Time=07-02-19 09.16.40, Disk dm-1 spent too much time (1565 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-0 ior: 0.000 iow: 15.206 ios: 3 qlen: 4 wait: 838;';3:Time=07-02-19 09.16.40, Disk dm-0 spent too much time (838 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdc ior: 0.899 iow: 2.000 ios: 3 qlen: 1 wait: 382;';3:Time=07-02-19 09.16.40, Disk sdc spent too much time (382 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdb ior: 0.000 iow: 18.407 ios: 1 qlen: 3 wait: 770;';3:Time=07-02-19 09.16.40, Disk sdb spent too much time (770 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-1 ior: 0.000 iow: 737.072 ios: 184 qlen: 10 wait: 1060;';3:Time=07-02-19 09.16.55, Disk dm-1 spent too much time (1060 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdb ior: 0.000 iow: 1011.573 ios: 15 qlen: 0 wait: 1210;';3:Time=07-02-19 09.16.55, Disk sdb spent too much time (1210 msecs) waiting for I/O (> 100 msecs)' type: SYS

sda ior: 0.000 iow: 8.803 ios: 1 qlen: 0 wait: 3992;';3:Time=07-02-19 09.17.00, Disk sda spent too much time (3992 msecs) waiting for I/O (> 100 msecs)' type: SWAP

sda3 ior: 0.000 iow: 8.803 ios: 1 qlen: 0 wait: 3992;';3:Time=07-02-19 09.17.00, Disk sda3 spent too much time (3992 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-0 ior: 0.000 iow: 7.202 ios: 1 qlen: 0 wait: 4436;';3:Time=07-02-19 09.17.00, Disk dm-0 spent too much time (4436 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdc ior: 2.596 iow: 1.896 ios: 3 qlen: 1 wait: 370;';3:Time=07-02-19 09.17.40, Disk sdc spent too much time (370 msecs) waiting for I/O (> 100 msecs)' type: SYS

sda ior: 0.000 iow: 21.602 ios: 3 qlen: 1 wait: 1943;';3:Time=07-02-19 09.18.45, Disk sda spent too much time (1943 msecs) waiting for I/O (> 100 msecs)' type: SWAP

sda3 ior: 0.000 iow: 21.602 ios: 3 qlen: 1 wait: 1943;';3:Time=07-02-19 09.18.45, Disk sda3 spent too much time (1943 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-1 ior: 0.000 iow: 1968.174 ios: 492 qlen: 77 wait: 202;';3:Time=07-02-19 09.18.45, Disk dm-1 spent too much time (202 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-0 ior: 0.000 iow: 8.801 ios: 2 qlen: 2 wait: 4660;';3:Time=07-02-19 09.18.45, Disk dm-0 spent too much time (4660 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdc ior: 5.700 iow: 2.899 ios: 6 qlen: 0 wait: 1033;';3:Time=07-02-19 09.18.45, Disk sdc spent too much time (1033 msecs) waiting for I/O (> 100 msecs)' type: SYS

dm-1 ior: 0.000 iow: 274.506 ios: 68 qlen: 208 wait: 12512;';3:Time=07-02-19 09.20.05, Disk dm-1 spent too much time (12512 msecs) waiting for I/O (> 100 msecs)' type: SYS

sdb ior: 0.000 iow: 579.425 ios: 47 qlen: 39 wait: 2515;';3:Time=07-02-19 09.20.05, Disk sdb spent too much time (2515 msecs) waiting for I/O (> 100 msecs)' type: SYS

三、总结与后续处理建议

3.1 问题总结

当前环境为VMWARE虚拟机环境搭建6节点ORACLE GRID集群,使用ACFS文件系统为应用程序提供数据共享目录 /DATA,应用程序同时部署在6节点ORACLE GRID集群的对应主机上;未在集群环境运行ORACLE数据库。

对于近期两次典型问题分析如下:6/24日中午12点附近出现ACFS文件系统访问异常,通过查看集群ALERT日志、CSSD进程日志及OSW监控软件的日志,可以发现OSW监控软件在11:55-12:40分时没有收集到主机的监控数据,同期数据库的CSSD进程也有与其它节点的私网信息已经丢失网络心跳,因此可以推断当时主机已经HANG住。7/2日上午9点附近ACFS文件系统无法访问,当时OSW监控未开启;从集群ALERT日志来看当时有应用进程在使用/DATA目录 无法UNMOUNT,操作系统日志中有NFO: task java:12227 blocked for more than 120 seconds.信息,因未有其它有效信息,暂无法判断当时何种原因导致ACFS文件系统访问异常。

从具体的问题来看,ORACLE集群软件做为操作系统上层的软件,会受到底层操作系统OS以及更底层的VMWARE虚拟机环境的影响;由于几层系统之间监控日志粒度也不同,对于问题的分析带来了较大的复杂度;许多信息无法向下追踪去查找根本原因;

3.2 后续处理建议

因此结合历次问题及整体架构的考虑建议如下:

1.加强对LINUX虚拟主机运行情况的监控,如开启OSW监控,开启ZABBIX监控。

2.建议联系VMWARE虚拟机维护人员沟通是否可以从VMWARE虚拟机层面对LINUX主机进行监控,同时对VMWARE虚拟机本身及底层的物理机能有更加细粒度的监控。

3.ASM实例的memory_max_target内存参数当前为默认的1076M;后续建议调整到2048M,提升ASM实例的性能。

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.mzph.cn/web/15511.shtml

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

【OceanBase诊断调优】—— 直连普通租户时遇到报错:Tenant not in this server

本文介绍了直连 OceanBase 数据库中的普通租户时&#xff0c;出现报错&#xff1a;ERROR 5150 (HY000) : Tenant not in this server 的处理方法。 问题描述 在 n-n 或者 n-n-n (n>1) 的部署架构中&#xff0c;使用 2881 端口 直连 OceanBase 集群的普通租户&#xff0c;可…

ChatGPT大语言模型发展历史

技术背景与OpenAI成立 2010年代初&#xff1a;随着深度学习技术的突破&#xff0c;特别是循环神经网络(RNN)和长短时记忆网络(LSTM)的成功应用&#xff0c;自然语言处理(NLP)领域开始经历一场革命。2015年12月&#xff1a;OpenAI作为一个旨在确保人工智能(AI)研究造福全人类的…

Java并行流

Java并行流 什么是并行流&#xff1f;并行流的优缺点优点缺点 如何使用&#xff1f;1.创建流2.转换为并行流3.流操作4.收集结果5.关闭流 并行流的本质1.任务划分和调度2.并发处理数据3.任务结果合并4.性能优化 参考文献官方文档 什么是并行流&#xff1f; 并行流&#xff08;p…

【C++风云录】揭秘医疗机器人:技术解析与应用探索

打造智能医疗&#xff1a;医疗机器人技术与手术辅助 前言 本文将在深度和广度上探讨六种尖端医疗机器人系统&#xff0c;并重点介绍其应用、C控制接口及其功能。这些机器人系统分别是ROSA Robot、Da Vinci Surgical SystemSDK、Intuitive Surgical’s da Vinci Xi、Medroboti…

黑龙江等保测评新要求下的政府信息化安全实践案例分析

在数字化转型的浪潮中&#xff0c;政府机构作为社会管理和公共服务的核心&#xff0c;其信息安全的重要性日益凸显。近期&#xff0c;黑龙江省积极响应国家网络安全战略&#xff0c;依据最新的等级保护测评&#xff08;简称“等保测评”&#xff09;要求&#xff0c;对政府信息…

SpringBoot运维篇(打包,多环境,日志)

文章目录 一、SpringBoot程序的打包与运行二、配置高级三、多环境开发四、日志 一、SpringBoot程序的打包与运行 刚开始做开发学习的小伙伴可能在有一个知识上面有错误的认知&#xff0c;我们天天写程序是在Idea下写的&#xff0c;运行也是在Idea下运行的。 ​但是实际开发完成…

CDH6.3.2集成Flink1.17

直接运行脚本即可&#xff0c;一键输出相关依赖包 运行步骤已给到文档 下载地址

Html基础笔记

Html超文本标记语言 (HyperText Markup Language) 超文本 指的是网页中可以显示的内容(图片,超链接,视频,) 标记语言 标记–>标签(标注) 例如:买东西的时候—>商品具有标签,看到标签就知道商品的属性(价格,材质,型号等,) 标记语言就是提供了很多的标签,不同的标签…

若依框架对于后端返回异常后怎么处理?

1、后端返回自定义异常serviceException 2、触发该异常后返回json数据 因为若依对请求和响应都封装了&#xff0c;所以根据返回值response获取不到Code值但若依提供了一个catch方法用来捕获返回异常的数据 3、处理的方法

antd design 自定义表头

<template><a-card :bordered"false"><div class"contentWrap"><!-- 查询区域 --><div class"table-page-search-wrapper"><a-form layout"inline" keyup.enter.native"searchQuery">&…

云端智享——记移动云手写docker-demo

目录 前言什么是移动云&#xff1f;为何我会使用移动云&#xff1f;移动云“好”在哪里&#xff1f;资源大屏显示继续项目部署其他细节 移动云产品的评价未来展望 前言 在如今这个万物都上云的时代&#xff0c;我们需要选择合适的云产品&#xff0c;而移动云有着独特的优势和广…

TypeScript-联合类型和别名类型

联合类型 作用&#xff1a;将多个类型合并为一个类型对变量进行注解 // 数组里面既有字符串类型 也有数字类型 let arr:(string | number)[] [20,lily] 别名类型 通过type关键词给写起来较复杂的类型起一个其它的名字 好处&#xff1a;用来简化和复用类型 说明&#xff…

golang中chan的高级用法

在阅读k8s的源代码中&#xff0c;发现了一些比较有意思的用法。 在Go语言中&#xff0c;chan&#xff08;通道&#xff09;是一种用于在不同的goroutine之间进行通信的机制。WaitForCacheSync(stopCh <-chan struct{}) error方法中的参数stopCh <-chan struct{}表示一个…

1.存储部分

1.Flash Memory--闪速存储器&#xff08;注&#xff1a;U盘&#xff0c;SD卡就是闪存&#xff09;在EEPROM基础上发展而来的&#xff0c;断电后也能保存信息&#xff0c;且可进行多次 快速擦除重写。注意&#xff1a;由于闪存需要先擦除再写入&#xff0c;因此闪存写的速度要比…

达梦数据库学习笔记

架构、特点和基本概念 达梦数据库&#xff08;DM Database&#xff09;是中国达梦数据库有限公司自主研发的关系型数据库管理系统。它广泛应用于政府、金融、电信、能源等行业&#xff0c;具备高性能、高可靠性和高安全性的特点。 架构 达梦数据库的架构设计注重高性能和高可…

python-绘制五星红旗(非标准)

完整代码如下&#xff1a; #五星红旗&#xff08;非标准版&#xff09; from turtle import* import math from random import* tracer(0) penup() goto(-640,220) pendown() color(gold,gold) begin_fill() for i in range(5): fd(150) right(144) # 大五角星 penup(…

基于UDP的网络多人聊天室

UDP服务器 #include <myheader.h>//宏定义打印错误信息 #define PRINT_ERR(msg) \do \{ \printf("%S,%D,%S\n",__FI…

java单元测试:编写可测试性好的代码

写出可测试性好的代码是编写高质量软件的关键。以下是一些有助于提高代码可测试性的最佳实践&#xff1a; 1. 单一职责原则 (Single Responsibility Principle) 每个类或方法应只负责一个功能。这样可以让测试更容易集中于单一功能。 2. 依赖注入 (Dependency Injection) 通…

【一个糟糕的词:省流】

今日思考&#xff0c;博主分享&#x1f4dd;&#xff0c;原文如下&#xff0c; 我最近听到了一个特别糟糕的词叫省流。我甚至认为这个词可以用来衡量一个人的智商啊&#xff0c;我们可以把一个知识简单的分成三部分问题&#xff0c;答案思维方式就是这个答案是怎么推导出来的啊…

Python数据可视化(二)

Patches绘制几何图形 模块 patches 主要用来完成多边形的绘制工作。这些多边形都是以类&#xff08;Class&#xff09;的形式出现的&#xff0c; 主要包括圆&#xff08;Circle&#xff09;、椭圆&#xff08;Ellipse&#xff09;、矩形&#xff08;Rectangle&#xff09;、圆…