ORACLE CRS日志中的ClssnmPollingThread Missed Checkins Messages

最近发现CRS日志中的missed checkin很多，有时候有连着将近20次，之前有过一次RAC的宕机记录，所以对这个咚咚很警觉。CRS中，会定期的去读取VOTING DISK上的信息来判断CLUSTER中的每个节点的活动状态，如果出现多次的读取失败，则认为这个节点已经死掉，机会把它赶出CLUSTER了。读取失败的参数是可以通过CRSCTL命令设置的，这个值缺省是60次。crsctl get css misscount命令可以返回当前设置的值，crsctl set css misscount 120则是把失败次数设置为120次。一般是不需要调整这个值的，如果调整也不要调的太大。还是来看看metalink上是怎么说的吧。

[@more@]

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.2
This problem can occur on any platform.
SymptomsThe ocssd.log contains irregular messages about missed checkins from the remote nodes(s) or the local node. The missed checkins are not increasing.

Extract from ocssd.log:

[ CSSD]2006-06-01 14:10:25.138 [10] >TRACE: clssgmClientConnectMsg: Connect from con(100aca070) proc(100acd0f0) pid() proto(10:2:1:1)
[ CSSD]2006-06-01 14:11:24.288 [14] >TRACE: clssnmPollingThread: node myrac2 (2) missed(2) checkin(s)
[ CSSD]2006-06-01 14:11:25.547 [10] >TRACE: clssgmClientConnectMsg: Connect from con(100aca070) proc(100ae74e0) pid() proto(10:2:1:1)
[ CSSD]2006-06-01 14:11:50.468 [14] >TRACE: clssnmPollingThread: node myrac1 (1) missed(2) checkin(s)
[ CSSD]2006-06-01 14:12:25.960 [10] >TRACE: clssgmClientConnectMsg: Connect from con(100acd800) proc(100acd0f0) pid() proto(10:2:1:1)

Changes Install/upgrade to 10.2.
CauseThe missed checkins are printed for diagnostic purpose only.
SolutionThe harmless messages can be ignored. It has been removed with the patch for bug 5037871, which will be included in 10.2.0.3.

基本上如果出现问题的话，那missed(2)就会变成missed(3)、missed(4)等一路累加，直到超过MISSCOUNT的值，导致节点被赶出CLUSTER

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/25016/viewspace-1005674/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/25016/viewspace-1005674/