Sponsored Content
Full Discussion: process migration
Top Forums UNIX for Dummies Questions & Answers process migration Post 302073808 by jim mcnamara on Wednesday 17th of May 2006 08:47:54 PM
Old 05-17-2006
It is not possible to move a running process. Load balancing in a cluster occurs BEFORE the process starts - by creating the process on the least busy machine.

On a multi-cpu box, the load is shifted among processors. Once the process starts.

One other possibility is to have the same process sleeping everywhere and have it waken to handle a single request on a selected machine.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Migration

Is it possible to migrate a UNIX program and use it in a NetWare or Windows 2000 network? I have a client that must have one of those two operating systems for the new program that they want. However, they've been using an older UNIX program for about 7 years and they want to be able to refer to... (7 Replies)
Discussion started by: refram
7 Replies

2. UNIX for Advanced & Expert Users

migration

hi, is there any tool that i can use to update my scripts (SH scripts) form Unix to linux. please mention any useful websites. thanx in advance (2 Replies)
Discussion started by: omran
2 Replies

3. UNIX for Advanced & Expert Users

Process migration

Using binary translators, would it be possible capture the runtime image (instructions and data) of processes and translate these so that the process can run from where it left on a machine with a different architecture? This will be useful for migrating applications to heterogenous systems for... (3 Replies)
Discussion started by: sumona
3 Replies

4. UNIX for Advanced & Expert Users

Migration

Hi all, Would appreciate advise on my situation. Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies

5. UNIX for Advanced & Expert Users

process migration

how can i migrate a running process in unix to another node? (1 Reply)
Discussion started by: aisalihu
1 Replies

6. Shell Programming and Scripting

Migration unit testing process

Hi, We are doing migration from DB2 to Teradata. There are couple of things involving in the project. Please see below following order Autosys-Jil script Profile script Category1 Teradata script Data stage job script Tera data script Export files script.. Like that we have 10000... (1 Reply)
Discussion started by: onesuri
1 Replies

7. UNIX for Advanced & Expert Users

Migration of users

We are about to get a new server and I need to prepare for migration to the new one. This will be my first migration so I'm sure I will be learning alot. My current server is running CentOS 4.x and I want to move to a sever running Centos 5.x , thought it would make things easier. The old... (1 Reply)
Discussion started by: mcraul
1 Replies

8. Red Hat

Doubt about process migration

Hello experts, My doubt is, shall we move process from one node to another node..? This will be need when the cpu running on max load. Thanks. (1 Reply)
Discussion started by: srigias
1 Replies

9. AIX

Lpar migration

We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2 Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies

10. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
intrbald(1M)															      intrbald(1M)

NAME
intrbald - daemon for balancing interrupts SYNOPSIS
interval | DESCRIPTION
Balancing interrupts is a process which distributes interrupts across the available CPUs in an optimal fashion. This action is performed by (see intctl(1M)). Performing frequent CPU migrations between system partitions may require you to perform periodic balancing of interrupts. This is espe- cially true with systems that use WLM (Workload Manager), iCAP (Instant Capacity), and vPars (Virtual Partitions) products. If the fre- quency of CPU migration is high, then balancing of interrupts should be performed more frequently. The daemon monitors the system for imbalance in interrupt distribution. If an imbalance is detected after the specified interval executes to balance the interrupt distribution. uses the parameters from the configuration file for balancing the interrupts. For more information about the command, see intctl(1M) and the configuration file. The daemon is started from the general purpose sequencer script (see rc(1M)), at run level 2 and is killed at run level 1. By default, the daemon is not enabled. The daemon configuration file must be edited and the parameter set to in order to enable running the daemon. After setting to for the first time, you can start the daemon manually by executing the script Otherwise, the daemon will automatically start the next time the system is restarted. Any actions performed by the daemon are logged in and details of interrupt migrations performed will be logged in the file Options recognizes the following options: Instructs the running daemon to reexamine the configuration file If the parameter has been updated, then the running daemon uses the new value. If the parameter is set to then the running daemon stops executing. The daemon checks if the system requires any balancing of interrupts after interval seconds; the valid range is 5 seconds to seconds (see limits(5)). This value can also be specified persistently in the configuration file by setting the parameter. The default value is 60 seconds. Setting this value too small can cause unnecessary interrupt migrations. Gracefully kills the running daemon. intrbald rc Configuration File is the configuration file. The following parameters can be persistently specified in this configuration file: Specifies if the daemon should be started automatically during the system bootup process by the script. The daemon will only be started automatically if this parameter is set to NOTE: This value is by default. Before using the daemon, needs to be changed to in the file. Then the daemon needs to be started, either manually by running or it will be started automatically at next boot via the script. The daemon checks if the system requires any interrupt balancing after this interval. The interval is specified in seconds; the valid range is 5 seconds to seconds (see lim- its(5)). The default is 60 seconds. Setting this value too small could cause unnecessary interrupt migrations. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. WARNINGS
The command can be executed only by the superuser. This command should be used only by performance analysts for performance tuning pur- poses. If the interrupts are not redistributed properly, a possible decrease in overall system performance can occur. Some processors can become overloaded while other processors will not be optimally utilized. FILES
configuration file. See the section above. script. start symbolic link. kill symbolic link. daemon log file. SEE ALSO
intctl(1M), ioscan(1M), rc(1M), limits(5). intrbald(1M)
All times are GMT -4. The time now is 03:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy