Proxy resource reports unknown state during VCS startup
Article ID: 100021008
Updated On:
Description
Error Message
From: Notifier
Subject: VCS Warning, Resource state is unknown
Event Time: Thu 19 Mar 2009 07:09:12 PM PDTEntity Name: proxy_2
Entity Type: Resource
Entity Subtype: Proxy
Entity State: Resource state is unknown
Resolution
The Proxy agent obtains the state of the target resource directly from the VCS engine (the "had" process), there is no actual monitor process for the Proxy resource itself. During the startup of the VCS, the target resource (e.g. NIC, NFS) needs to run the actual monitor program and it will take a certain amount of time. When the Proxy agent queries the VCS engine for the state of the target resource, the target resource's state will most likely still be UNKNOWN. The Proxy agent will then correctly declare the Proxy resource's state as UNKNOWN.
Since an UNKNOWN state is treated by the VCS Notifier as a warning, a notification will be sent if the Notifier is configured accordingly.
In order to minimize such warnings the Proxy agent was enhanced to delay the first probe of the Proxy resource state. It is achieved by sleeping at the Open Entry Point before querying the VCS engine of the target resource's state. This enhancement was introduced in 5.0MP3 Rolling Patch 2.
In the event of multiple proxy resources, the number of threads in the Proxy agent may may need to be increased in order to correctly handle the first probe of all the proxy resources. If all the agent worker threads are sleeping in the Open Entry Point, there may be insufficient worker threads available to handle the target resource state update. This will also cause the Proxy agent to send an unnecessary "state unknown" notification. To avoid this, increase the NumThreads attribute for the Proxy agent to the sum of the number of Proxy resources and target resources.
For example, if there are 20 Proxy resources referencing a total of 3 target resources, it is recommended to increase the NumThreads attribute to 23. i.e.
# haconf -makerw
# hatype -modify ProxyNumThreads 23
# haconf -dump -makero
Since an UNKNOWN state is treated by the VCS Notifier as a warning, a notification will be sent if the Notifier is configured accordingly.
In order to minimize such warnings the Proxy agent was enhanced to delay the first probe of the Proxy resource state. It is achieved by sleeping at the Open Entry Point before querying the VCS engine of the target resource's state. This enhancement was introduced in 5.0MP3 Rolling Patch 2.
In the event of multiple proxy resources, the number of threads in the Proxy agent may may need to be increased in order to correctly handle the first probe of all the proxy resources. If all the agent worker threads are sleeping in the Open Entry Point, there may be insufficient worker threads available to handle the target resource state update. This will also cause the Proxy agent to send an unnecessary "state unknown" notification. To avoid this, increase the NumThreads attribute for the Proxy agent to the sum of the number of Proxy resources and target resources.
For example, if there are 20 Proxy resources referencing a total of 3 target resources, it is recommended to increase the NumThreads attribute to 23. i.e.
# haconf -makerw
# hatype -modify ProxyNumThreads 23
# haconf -dump -makero
Issue/Introduction
Proxy resource reports unknown state during VCS startup
Additional Information
ETrack: 1668609
Was this article helpful?
Yes
No
Powered by
