Subject | Re: [firebird-support] Multiple DBMS Access to single GDB files |
---|---|
Author | Ann Harrison |
Post date | 2003-12-11T21:10:32Z |
Tim Ledgerwood wrote:
work fine. The problem with clusters is to prevent the different
servers from stepping on each others' changes. On a single system, in
Classic mode, the various client processes use the lock manager to
indicate that they need exclusive control of a page before writing it
out. The trick in a cluster is to have some similar process that
manages locks between all servers in the cluster. VMS has one. There
are other clusters with lock managers, and with a certain amount of
pain, our lock semantics could be grafted onto theirs. The question is
whether the lock manager would be such a bottleneck that the whole thing
would be slower than a single processor...
Regards,
Ann
>He would like to install the DBMS software on several machines.If we had a current VMS port, and if he had a VAXCluster, then it would
>
>Each DBMS engine looks at the same database (in IB/FB terms, the GDB file)
>file over the network.
>
work fine. The problem with clusters is to prevent the different
servers from stepping on each others' changes. On a single system, in
Classic mode, the various client processes use the lock manager to
indicate that they need exclusive control of a page before writing it
out. The trick in a cluster is to have some similar process that
manages locks between all servers in the cluster. VMS has one. There
are other clusters with lock managers, and with a certain amount of
pain, our lock semantics could be grafted onto theirs. The question is
whether the lock manager would be such a bottleneck that the whole thing
would be slower than a single processor...
Regards,
Ann