06-20-2005
It is actually a known Sun Cluster problem where the server that contains the Global File System will use more cpu and therefore more overhead.
We have a problem where we have 2 servers in a sun cluster, 1 uses too much cpu which has the global file system. However it is directly related to the amount of files in the filesystem, and when there are too many it uses too much cpu for searching.
The script is /usr/lib/acct/dodisk
Thanks
8 More Discussions You Might Find Interesting
1. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
2. High Performance Computing
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
3. High Performance Computing
Hi all,
I need ur help plz
how sun cluster work and i need good reference for that.
ur cooperate is appreciated (4 Replies)
Discussion started by: AshAdmin
4 Replies
4. High Performance Computing
Gurus,
I have several questions :
1. Does Solaris 10/OpenSolaris has some kind of web based management tools ?
Currently I am using WebMin. It worked fine, however I am very curious to use
the tools provided by Sun Microsystem.
Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies
5. Solaris
Howdy experts,
I am using two Sun-Fire-T200 which is in Cluster mode (sun cluster 3.1). Also Oracle RAC is running on those.
A daylight saving i need to apply in both servers. I am not using any ntp server.
I just plan to change the date with simple date command. Change date in 1st node.... (3 Replies)
Discussion started by: thepurple
3 Replies
6. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
7. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
8. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
LEARN ABOUT NETBSD
cpuset_zero
CPUSET(3) BSD Library Functions Manual CPUSET(3)
NAME
cpuset_create, cpuset_destroy, cpuset_zero, cpuset_set, cpuset_clr, cpuset_isset, cpuset_size -- dynamic CPU sets
SYNOPSIS
#include <sched.h>
cpuset_t *
cpuset_create(void);
void
cpuset_destroy(cpuset_t *set);
void
cpuset_zero(cpuset_t *set);
int
cpuset_set(cpuid_t cpu, cpuset_t *set);
int
cpuset_clr(cpuid_t cpu, cpuset_t *set);
int
cpuset_isset(cpuid_t cpu, const cpuset_t *set);
size_t
cpuset_size(const cpuset_t *set);
DESCRIPTION
This section describes the functions used to create, set, use and destroy the dynamic CPU sets.
This API can be used with the POSIX threads, see pthread(3) and affinity(3).
The ID of the primary CPU in the system is 0.
FUNCTIONS
cpuset_create()
Allocates and initializes a clean CPU-set. Returns the pointer to the CPU-set, or NULL on failure.
cpuset_destroy(set)
Destroy the CPU-set specified by set.
cpuset_zero(set)
Makes the CPU-set specified by set clean, that is, memory is initialized to zero bytes, and none of the CPUs set.
cpuset_set(cpu, set)
Sets the CPU specified by cpu in set. Returns zero on success, and -1 if cpu is invalid.
cpuset_clr(cpu, set)
Clears the CPU specified by cpu in the CPU-set set. Returns zero on success, and -1 if cpu is invalid.
cpuset_isset(cpu, set)
Checks if CPU specified by cpu is set in the CPU-set set. Returns the positive number if set, zero if not set, and -1 if cpu is
invalid.
cpuset_size(set)
Returns the size in bytes of CPU-set specified by set.
SEE ALSO
affinity(3), pset(3), sched(3), schedctl(8), kcpuset(9)
HISTORY
The dynamic CPU sets appeared in NetBSD 5.0.
BSD
November 2, 2011 BSD