In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
Phenomenon description: 12.1.0.2 Cluster process ocssd.bin occupies a higher CPU:
PID USER PR NI VIRT RES SHR S% CPU% MEM TIME+ COMMAND 27647 grid RT 05002m 2.8g 86m S 117.6 0.6209825 MEM TIME+ COMMAND 27 ocssd.bin
The overall CPU usage of the system is not high, resulting in the high CPU utilization of the above single thread is caused by the clsdadr_bucketThread thread.
# 5 0x00007f0b76feb0bc in clsdadr_process_bucket () from / u01/app/12.1.0.2/grid/lib/libhasgen12.so#6 0x00007f0b76feac23 in clsdadr_bucketThread () from / u01/app/12.1.0.2/grid/lib/libhasgen12.so
At the same time, looking at the ocssd.trc file, you can find a large number of the following prompts:
2018-10-12 14 group OSM_ALL member 33 not found2018 04.342374: CSSD:3886925568: clssgmMemberPublicInfo: group OSM_ALL member 1 not found2018-10-12 14 33 group OSM_ALL member 04.435152: CSSD:3886925568: clssgmMbrDataUpdt: Processing member data change type 1, size 4 for group HB+ASM, memberID 11 Vista 12018-10-12 14 Switzerland 33 Switzerland 04.435164: CSSD:3886925568: clssgmMbrDataUpdt: Sending member data change to GMP for group HB+ASM MemberID 12018-10-12 14 clssgmpcMemberDataUpdt clssgmpcMemberDataUpdt: grockName HB+ASM memberID 11:2:1 Datatype 1 datasize 42018-10-12 14 CSSD:3883771648 33 clssnmSendingThread: CSSD:3883771648: clssgmcpDataUpdtCmpl: Status 0 mbr data updt memberID 11:2:1 from clientID 1V 16010-10-12 14 33 V 04.552308: CSSD:3848582912: clssnmSendingThread: sending status msg to all nodes2018-10-12 14 33 V V 04.553123: CSSD:3848582912: clssnmSendingThread: sent 4 status msgs to all nodes2018-10-12 14 33 V V 05.353496: CSSD:3886925568: clssgmMemberPublicInfo group OSM_ALL member: 1 not found2018-10-12 14 clssgmMemberPublicInfo 33 not found2018 06.346352: CSSD:3886925568: clssgmMemberPublicInfo: group OSM_ALL member 1 not found2018-10-12 14 clssgmMemberPublicInfo 33 Swiss 06.488828: CSSD:3886925568: clssgmMbrDataUpdt: Processing member data change type 1 Size 4 for group HB+ASM, memberID 11 memberID 2mer 12018-10-12 14315 3315 06.488842: CSSD:3886925568: clssgmMbrDataUpdt: Sending member data change to GMP for group HB+ASM, memberID 1112018-10-12 1433 memberID 06.492775: CSSD:3889161984: clssgmpcMemberDataUpdt: grockName HB+ASM memberID 11:2:1 Datatype 1 datasize 42018-10-12 14 CSSD:3883771648 33 06.499862: CSSD:3883771648: clssgmcpDataUpdtCmpl: Status 0 mbr data updt memberID 11:2:1 from clientID 1 Vera 160 42018-10-12 14 CSSD:3883771648 33 Switzerland 07.233537: GIPCHTHR:3878508288: gipchaDaemonWork: DaemonThread heart beat Time interval since last heartBeat 30020loopCount 372018-10-12 14 not found2018 33 clssgmMbrDataUpdt 07.349067: CSSD:3886925568: clssgmMemberPublicInfo: group OSM_ALL member 1 not found2018-10-12 14 33 clssgmMbrDataUpdt 3315 1711: CSSD:3886925568: clssgmMemberPublicInfo: group OSM_ALL member 1 not found2018-10-12 14 14 Processing member data change type 338.548780: CSSD:3886925568: clssgmMbrDataUpdt: Processing member data change type 1, size 4 for group HB+ASM, memberID 112 Processing member data change type 12018-10-12 14 14 Switzerland 3308.548794: CSSD:3886925568: Sending member data change to GMP for group HB+ASM: MemberID 112clssgmpcMemberDataUpdt clssgmpcMemberDataUpdt: grockName HB+ASM memberID 11:2:1, datatype 1 datasize 42018-10-12 1414 3331: CSSD:3883771648: clssgmcpDataUpdtCmpl: Status 0 mbr data updt memberID 11:2:1 from clientID 1lav 160lav 4
A similar situation was found by querying MOS. Refer to MOS document ID 2235698.1 for details. This problem is caused by Bug 26513709 and can be avoided by applying patches 20302006 and 25211209. At the same time, it is officially announced that the bug has been fixed in 12.2.0.2.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.