7353884-OCSSD spends 590 seconds for Local Join starting crs stack_7353884.8
Bug 7353884 - OCSSD spends 590 seconds for 'Local Join' when starting crs stack (Doc ID 7353884.8)
Bug 7353884 OCSSD spends 590 seconds for 'Local Join' when starting crs stackThis note gives a brief overview of bug 7353884.The content was last updated on: 07-JAN-2013 Click here for details of each of the sections below. Affects:
Fixed:
DescriptionRestarting the clusterware on one node, after the nodes have been manually stopped spends 590 secs. Rediscovery Notes: The OCSSD log shows similar messages to: [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmRcfgMgrThread: Local Join [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: begin on node(1), waittime 590000 [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: curTime (8165381) - LAT (8164840) = 541, for node (1), waittime 590000 [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: curTime (8165381) - LAT (8157770) = 7611, for node (2), waittime 590000 [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: set curtime (8165381) for my node [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: scan 3 nodes [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: node(1), state(1), cont (1), sleep (0), diskHB 1, diskinfo 6000000000546320 [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: No sleeping for mynode(1) [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: node(2), state(0), cont (1), sleep (0), diskHB 0, diskinfo 6000000000546320 [ CSSD]2009-01-20 14:52:44.086 [16] >TRACE: clssnmLocalJoinEvent: node(2), LAT (0) [ CSSD]2009-01-20 14:52:44.546 [7] >TRACE: clssnmvReadDskHeartBeat: read ALL for Joining [ CSSD]2009-01-20 14:52:44.549 [8] >TRACE: clssnmvReadDskHeartBeat: read ALL for Joining [ CSSD]2009-01-20 14:52:44.556 [10] >TRACE: clssnmvReadDskHeartBeat:read ALL for Joining << the previous msgs repeats >> Workaround Start all the nodes around the same time.
ReferencesBug:7353884 (This link will only work for PUBLISHED bugs) |
|
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1266591/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- RX590顯示卡怎麼樣?AMD RX 590顯示卡評測:加“頻”不加價
- join、inner join、left join、right join、outer join的區別
- Starting & Stopping SAP
- Starting HAL daemon:[FAILED]AI
- 30-seconds-code——adapterAPT
- MySQL LEFT JOIN/ INNER JOIN/RIGHT JOINMySql
- 【JZOJ 3749】【Srm590】Fox And City
- sql中的join、left join、right joinSQL
- ORACLE程式之LOCAL=NO和LOCAL=YESOracle
- crs_stat -t CRS-0184: Cannot communicate with the CRS daemon
- 【譯】30 Seconds of ES6 (一)
- [MySQL管理] Seconds_Behind_Master 解析MySqlAST
- slave之Seconds_Behind_Master析AST
- 10g 11g 檢視是否DISABLE CRS和10g 11g LOCAL listener的區別
- Mysql join 的本質,Nested Loop Join 和 Hash JoinMySqlOOP
- mysql left join轉inner joinMySql
- 微星MPG Z590 ACE主機板怎麼樣?微星MPG Z590 ACE主機板評測
- Android Starting Window(Preview Window)AndroidView
- .join()
- sql之left join、right join、inner join的區別SQL
- 連線查詢簡析 join 、 left join 、 right join
- hash join\nest loop join\sort merge join的實驗OOP
- ZT:簡單介紹join,outer-join,semi-join,anti-join的區別
- CRS-0184 Cannot communicate with the CRS daemon
- CRS-0184: Cannot communicate with the CRS daemon
- crs之上的resource管理總結(CRS_PROFILE)
- LEFT JOIN 和JOIN 多表連線
- HASH JOIN ,MERGE JOIN ,NESTED LOOPOOP
- sql:left join和join區別SQL
- SQL中聯表查詢操作(LEFT JOIN, RIGHT JOIN, INNER JOIN)SQL
- LOCAL_SHARED_LIBRARIES 與 LOCAL_LDLIBS,LOCAL_LDFLAGS的區別
- Starting httpd: httpd: Could not reliably determine the serverhttpdServer
- 數倉工具—Hive語法之map join、reduce join、smb join(8)Hive
- sql的left join 、right join 、inner join之間的區別SQL
- mysql中的left join、right join 、inner join的詳細用法MySql
- CRS-0184: Cannot communicate with the CRS daemon.
- CRS-1205:Auto-start failed for the CRS resourceAI
- Kill Oracle Local=NOOracle