- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: The resource hash table is sparse ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 06:33 AM
тАО07-27-2009 06:33 AM
But seriously ... I am seeing this message occasionaly being displayed in HP Operations Manager (OVO) on our ES47's eg:
The resource hash table is sparse (19702 resources found while SYSGEN parameter RESHASHTBL=65536)
The message doesn't get reset by whatever resource coming back above a threshold. The message is typically generated while the Data Protector backups are running.
The only reference to this error text I can find is in the Availability Manager manual where it lists it in a "lock contention" group of messages.
Is this something to be concerned about? Something that can be tuned up?
VMS v8.3 - relatively current on patches.
Cheers,
Art
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 07:50 AM
тАО07-27-2009 07:50 AM
Re: The resource hash table is sparse ...
Files being backed up or restored are always locked regardless of whether the Lock files during backup (-lock) option
is enabled or disabled. With the -lock option enabled any file opened for write is not backed up. With the -lock option disabled
any open file is backed up as well. No message is issued when an open file is saved.
May be a lot of very small or empty files that are locked in bulk ?
Or may be the process quotas allow too much files to be backuped in paralel ?
Wim (no knowledge of DP)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 07:59 AM
тАО07-27-2009 07:59 AM
Re: The resource hash table is sparse ...
In the following "Availability manager User's Guide" link, it says:
http://h71000.www7.hp.com/openvms/products/availman/6552pro_004.html#ap_b
Event:
RESPRS - Resource hash table sparse
Description:
The percentage of occupied entries in the hash table is less than the threshold.
Explanation:
A sparsely populated table wastes memory resources.
Recommended action:
Use the system parameter RESHASHTBL to adjust the total number of entries.
I think this indicates that the percentage of resource hash table entries actually used by your system is less compared to the value that is set for the SYSGEN parameter RESHASHTBL. So, I think this message is indicating that you may reduce the RESHASHTBL value so that memory resources may not be wasted.
Regards,
Shilpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 08:42 AM
тАО07-27-2009 08:42 AM
Re: The resource hash table is sparse ...
Are you short on free physical memory here? If so? toss a few gigabytes into the box and move on to the next problem.
As I posted to the HL web site earlier today, keep your eye on the prize. The rules and the assumptions and the environments change. Memory prices have dropped since the days of VAX, and configurations (with the exception of that fellow with the overloaded AlphaServer 800 box that's been around here recently) are vastly larger and more capable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 10:46 AM
тАО07-27-2009 10:46 AM
Re: The resource hash table is sparse ...
There's lots of memory in these systems - either 4GB or 8GB depending on which one.
Thanks,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 10:53 AM
тАО07-27-2009 10:53 AM
Solution"So it's sort of a reverse warning ... not that it's running out of anything but rather wasting something?"
From the explanation provided for "RESPRS" by the "Availability Manager User's Guide", I think it only indicates that its not utilizing the resource optimally and thus wasting. I think it is more of a informational message than a warning.
Reagrds,
Shilpa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 12:48 PM
тАО07-27-2009 12:48 PM
Re: The resource hash table is sparse ...
The fellow that created this rule obviously thought that a savings of around 16 pages might be significant. It could be, too.
But outside of an aggregate recommendation arising from a memory starvation crisis or cases when the system manager has specifically requested memory optimizations, sixteen pages of memory seems to be noise.
Locally, I'd rather not bother the system manager for a potential savings of sixteen pages. Paralleling what Shilpa mentions around use of resources, the time and thought and consideration of a system manager is itself an important resource.
In my preferred and admittedly skewed view, OVO (or whatever the monitoring and tuning tool might be) would detect and would offer the memory upgrade part number and a URL for the reseller(s) or HP itself for a server memory upgrade, if that's something OVO suspects is warranted. (Or better, a "OVO can contact HP services and schedule an upgrade (for US$whatever) if you want to upgrade your server memory hardware. Is an installation on Thursday at 4pm OK? Enter your PO-number or credit card number into this HP secure web form to confirm." dialog box. Ok, so I can dream.) And as an alternative to the proffered memory upgrade, OVO can suggest RESHASHTBL here when memory was found tight, or as part of a specific "do you want me to find ways to free memory?" offered to the system manager.
As for why I don't find OVO should be reporting this? Even back in the VAX days, "buy more memory" was a common recommendation. These days, tossing 131,072 pages at a problem (or more) is usually a pretty easy solution for what ails your server. My current laptop operates with the equivalent of 524,288 Alpha pages, after all. If sixteen pages is the "low-hanging fruit" here for OVO, there's something wrong.
It'd be interesting to know when the rule was created, and the vintage of the rules engine, but that's fodder for another discussion.
And how much time have we wasted here for maybe sixteen pages?
This reply will probably turn into a blog entry here soon, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2009 01:40 PM
тАО07-27-2009 01:40 PM
Re: The resource hash table is sparse ...
putting in these things in the past was a bit of an art form as a lot of metrics tended to be configurable but not set, these days as with most everything else plug and play is what the customer wants, having paid a small fortune for one of these products another small fortune on tuning it with a small army of specialists is'nt what anybody wants to hear anymore.
so most of these products now come with more and more predefined default values based on 'best practise' and experience.
i think arts experience is typical of this one size fits all attempt at setting values which can range hugely from one site to the next. although now some of the above mentioned products are offering self-learning features in their software where they sample normal usage levels and set thresholds accordingly.
that does'nt leave much room for your system manager to apply their hard gained experience.
fwiw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2009 10:29 AM
тАО07-30-2009 10:29 AM
Re: The resource hash table is sparse ...
VMSSPI_ReshashtblSparse
Condition No.1 - The resource hash table is sparse (The percentage of resources found to the size of the resource hash table is below threshold) (match)
Match
Threshold 30
Reset 30
and
VMSSPI_ReshashtblDense
Condition No.1 - The resource hash table is dense (The percentage of resources found to the size of the resource hash table is above threshold) (match)
Match
Threshold 110
Reset 110
I do have lots of memory on these systems so I will simply increase the threshold for the sparse condition.
The dense threshold seems a bit "dense" (or maybe I just am) but 110% ?!
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2009 10:46 AM
тАО07-30-2009 10:46 AM
Re: The resource hash table is sparse ...
Cheers,
Art