Partition replicate problem

Question

Hi All,
Is there any possibility that, forte can bring
up two replicates of a partition, though it's not load
balanced? Sometimes, When, we bring up the
application, there are 2 active partitions, though we
desire only one. Its not happening regularly, but
sometimes. I killed all the non-ftexec processes and
tried as well, no use so far. Any idea, whats going
wrong there?
Thanks,
Babu
Send instant messages & get email alerts with Yahoo! Messenger.

Answer 1

Guys,
As far as I know, it's all very simple. The Autostart feature is used at the
moment an SO is referenced that lives inside a partition that hasn't been
started yet. The first reference to this SO fails, blocks and waits for the
partition to start. All following requests will immediately use this newly
created SO. If a second request is issued while the partition is being
started, then it will block as well and wait for the partition.
However, when the partition is being started by another job, then the
Autostart gets confused. Appearantly, it doesn't know the partition is
already being started and doesn't wait for that to complete, but starts
another instance of the same partition.
So, you start a batchjob that starts partition 1, 2 and 3. But, partition 1
references an SO that lives inside partition 3. Then, the Autostart feature
doesn't know you're busy starting partition 2 and 3 and starts its own
partition 3. Now, you have 2 times partition 3.
So, either
1) Don't use autostart and start everything yourself
2) Rely on autostart and never start anything yourself
3) Start all partitions bottom-up, so all SO-references are only to SO's
that already exist.
4) Individually disable Autostart for partitions that still keep causing
problems.
Pascal Rottier
Origin Nederland (BAS/West End User Computing)
Tel. [phone]
Fax. [phone]
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. [phone]
Fax. [phone]
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Babu Raj [mailto:ibcsmartboyyahoo.com]
Sent: Tuesday, September 26, 2000 4:30 AM
To: Amin, Kamran; 'Steve Barnes'; Forte-userslists.xpedior.com
Subject: RE: (forte-users) Partition replicate problem
Amin,
If i depend on the AutoStart, then only these
keep alive settings comes into play. But, in my case,
i tried manually bringing up the entire server
partitions, even that time, it creates 2 replicates
sometimes. As theory says that, when we initiate start
up command on the application, rather than individual
partition, forte brings up the partitions, in order,
meaning 1 to 10 ascending order, so how come that
time, it starts at the first instance itself.
I can make here 2 assumptions:
1. It starts order 1 partition, then before it comes
into active partition, node manager starts second one,
which inturn refers 1st one, and environment manager
is not finding the actual partition 1, though it
hasn't registered still, which inturn causes issuing
another startup command for partition 1.
2. Nodemanager have some timing issues like sort of
bug in forte.
Anyway, i greatly appreciate your input.
Thanks,
Babu
--- "Amin, Kamran" <kamran.aminlendware.com> wrote:
We had the same problem with was solved by playing
with the keep alive
setting. I would never turn of Failover and
autostart from my production
environment... It takes a little playing around
with the keep alive setting
but will solve the problem when you get it right.
ka
-----Original Message-----
From: Steve Barnes [mailto:DHS9126dhs.state.il.us]
Sent: Monday, September 25, 2000 11:18 AM
To: Forte-userslists.xpedior.com;
ibcsmartboyyahoo.com
Subject: Re: (forte-users) Partition replicate
problem
We had a problem when our Production environment had
"Autostart" turned on.
What would happen is (for whatever reason) a client
would "lose sight" of
the AIX server (in particular the partition that
holds our EventMgrSO). We
had code to detect this RemoteAccessEvent and
de-register the dead events
and re-register on the new SO (at the time we had
this partition setup for
failover, so there would be another SO "waiting in
the wings").
Well, when we stopped setting that SO up for
failover, the code was still in
place. The PC would lose sight of the partition and
try to connect to the
replicate (which wasn't there). Since AutoStart was
on, the environment
happily started up a new EventMgrSO partition. Now
some clients pointed to
#1, and some to #2. Very bad when everyone needs to
hear the same events.
We've cleaned most of this up, but have learned that
Failover and Autostart
DO NOT belong in a production environment. (maybe
our WAN is just to
unstable!).
Steven Barnes
Babu Raj <ibcsmartboyyahoo.com> 09/24/0012:12PM >>>
Hi All,
Is there any possibility that, forte can bring
up two replicates of a partition, though it's not
load
balanced? Sometimes, When, we bring up the
application, there are 2 active partitions, though
we
desire only one. Its not happening regularly, but
sometimes. I killed all the non-ftexec processes and
tried as well, no use so far. Any idea, whats going
wrong there?
Thanks,
Babu
Send instant messages & get email alerts with Yahoo!
Messenger.
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
Send instant messages & get email alerts with Yahoo! Messenger.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com