08-27-2012
If you have results, in some static form, you can dynamically mount NFS connections as needed to acces those directories.
Is your "backbone" 1GB or 10GB? If you can create a subnet for the fast NICs and each UNIX box has a 10GB NIC, this is very acceptable - what we do now. We create a job's data, notify the other box, it NFS mounts the dataset readonly, and away we go.
There is another issue to consider. Even though you may get great throughput, some boxes have issues. Solaris with older Qlogix cards takes a hit on interrupts. Because the cpu does a lot of work for the NIC.
All of this is a case of limiting factors, something you see in Science a lot. When you raise the bar on one limit (cpu) then some other resource becomes limiting (I/O in this case or interrupt stack). Since it is not economically feasible to build highways to completely handle rush hour traffic, so it is with computers. As long as it does not hurt production, and you get more processing power, you are okay. You did pay for the hadware, so use it.
9 More Discussions You Might Find Interesting
1. High Performance Computing
hello all...first off let me say hi and im really glad to be apart of this community....tried to join awhile back but i couldnt for some reason
im a highschool student and im eager to learn and what im trying to learn now is clusters
i have 3 computers in my room all connected on a simple hub
... (1 Reply)
Discussion started by: hexadecimal0011
1 Replies
2. Virtualization and Cloud Computing
Tim Bass
Thu, 15 Nov 2007 23:55:07 +0000
*I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. Solaris
How to get the list of zones which are bound to a pool say appPool. Rather then logging in each zone and then check from pool stat command. (3 Replies)
Discussion started by: fugitive
3 Replies
4. Programming
I was trying to test dump data on bedework jxi console however I got the error below.I'm using debian as my OS and installed quickstart bedework on it. Pls advise what am I missing. thanks
Caused by: javax.naming.NameNotFoundException: env not bound
at... (1 Reply)
Discussion started by: lhareigh890
1 Replies
5. Solaris
:)Hi,
can someone please explain VCS clustering and where do we need VCS clusters ..?
:o:)Thanks in advance :o:) (1 Reply)
Discussion started by: amitbisht9
1 Replies
6. Linux
Hi all,
Am getting the below error for a job that is run in our system.
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
This job uses a cobol program and as far as I know, the problem is related to this cobol program.
What does this... (1 Reply)
Discussion started by: das.somik
1 Replies
7. Solaris
Hi Guys,
I am studying netstat and I am getting confused a lot. I will be glad if someone will be kind enough to explain to me :
1) bound port
2) unbound port
3) idle
4 listening
I will very much appreciate it. Thanks guys
We have a special forum with special rules for homework (3 Replies)
Discussion started by: cjashu
3 Replies
8. Emergency UNIX and Linux Support
Hi All,
Can you please answer my question.
i see lot of CPU utilization on AIX LPARs. i am able to find the cause of the probelm. But i do not know how to mitigate or fix the problem.
for instance,
i found the process which is consuming most of CPU. i informed the responsible team.
how... (7 Replies)
Discussion started by: System Admin 77
7 Replies
9. Shell Programming and Scripting
Hi all,
I've data as:
22 51018157 51018157 exonic CHKB nonsynonymous SNV
22 51018204 51018204 exonic CHKB nonsynonymous SNV
22 51018428 51018428 exonic CHKB nonsynonymous SNV
22 51018814 51018814 ... (4 Replies)
Discussion started by: genome
4 Replies
LEARN ABOUT SUSE
ocf_heartbeat_filesystem
OCF_HEARTBEAT_FILESY(7) OCF resource agents OCF_HEARTBEAT_FILESY(7)
NAME
ocf_heartbeat_Filesystem - Manages filesystem mounts
SYNOPSIS
Filesystem [start | stop | notify | monitor | validate-all | meta-data]
DESCRIPTION
Resource script for Filesystem. It manages a Filesystem on a shared storage medium. The standard monitor operation of depth 0 (also known
as probe) checks if the filesystem is mounted. If you want deeper tests, set OCF_CHECK_LEVEL to one of the following values: 10: read first
16 blocks of the device (raw read) This doesn't exercise the filesystem at all, but the device on which the filesystem lives. This is noop
for non-block devices such as NFS, SMBFS, or bind mounts. 20: test if a status file can be written and read The status file must be
writable by root. This is not always the case with an NFS mount, as NFS exports usually have the "root_squash" option set. In such a setup,
you must either use read-only monitoring (depth=10), export with "no_root_squash" on your NFS server, or grant world write permissions on
the directory where the status file is to be placed.
SUPPORTED PARAMETERS
device
The name of block device for the filesystem, or -U, -L options for mount, or NFS mount specification. (required, string, no default)
directory
The mount point for the filesystem. (required, string, no default)
fstype
The optional type of filesystem to be mounted. (required, string, no default)
options
Any extra options to be given as -o options to mount. For bind mounts, add "bind" here and set fstype to "none". We will do the right
thing for options such as "bind,ro". (optional, string, no default)
statusfile_prefix
The prefix to be used for a status file for resource monitoring with depth 20. If you don't specify this parameter, all status files
will be created in a separate directory. (optional, string, default .Filesystem_status/)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 60.
stop
Stops the resource. Suggested minimum timeout: 60.
notify
Suggested minimum timeout: 60.
monitor
Performs a detailed status check. Suggested minimum timeout: 40. Suggested interval: 20.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a Filesystem resource using the crm(8) shell:
primitive example_Filesystem ocf:heartbeat:Filesystem
params
device=string
directory=string
fstype=string
op monitor depth="0" timeout="40" interval="20"
SEE ALSO
http://www.linux-ha.org/wiki/Filesystem_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents 1.0.3 07/05/2010 OCF_HEARTBEAT_FILESY(7)