Re: node: 4 failed to seize
We still face this problem....
In the meantime, we changed the Multithreading configuration
from
MaxNoOfExecutionThreads=8
to
ThreadConfig=ldm={count=4,cpubind=1,2,6,7},main={cpubind=8},io={cpubind=8},rep={cpubind=9},tc={cpubind=10},recv={cpubind=11}
This shows that the 'failed to seize' message seems to coincide with a significant raising of the CPU load (24% up to 40%) of CPU 10, which serves the Transaction Coordinator.
It does not nescessary apears only at high load situations... sometimes also during off peek hours.
I'm wondering whether anybody has seen something similar...
Any hint is highly appreciated.
Best regards
Stefan
Subject
Views
Written By
Posted
4398
March 21, 2014 07:08AM
801
March 21, 2014 01:38PM
Re: node: 4 failed to seize
758
April 18, 2014 10:02AM
2108
April 18, 2014 11:09AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.