IdP3 Clustering...

[Jim Fox]

>> Currently, the configuration of IdP2 running on production is like that :
>> Load-balancer with Persistence for 60sec,
>> 2 standalone IdP2.3.8 in which has a local mysql db but there is no replication
>> between them.
>> Both are actives on production, Is that configuration correct ?

> No. It's certainly not correct for persistent IDs. It's not good for lots of other things.

We have done persistent id this way since the beginning of time.  As long as each host computes the id the same way all the local DBs stay synchronized. And it's resilient.

It also give you an easy way to change a persistent id or even to provide the same id to a set of SPs.  I agree it's probably not good for much else.

Jim