Re: [Firebird-devel] Roadmap for a Distributed Firebird

2015-03-23 Thread James Starkey
No. The page/lock server is deeply involved with the Firebird on disk structure. On Monday, March 23, 2015, Tony Whyman wrote: > Just out of interest, is OCFS2/DRBD any use as a page/lock server? > > On 23/03/15 13:01, James Starkey wrote: > > The major new piece is a separate component, the pa

Re: [Firebird-devel] Roadmap for a Distributed Firebird

2015-03-23 Thread Tony Whyman
Just out of interest, is OCFS2/DRBD any use as a page/lock server? On 23/03/15 13:01, James Starkey wrote: > The major new piece is a separate component, the page server. By > phase 5, it will be necessary to integrate page change and lock > manager traffic, so perhaps a better name would be p

Re: [Firebird-devel] Roadmap for a Distributed Firebird

2015-03-23 Thread James Starkey
To elaborate somewhat, a very small number of changes would need to be made to the Firebird engine -- the essential architecture is already in place. The changes are mostly to DPM and below. Ironically, the code to generate page change records used to be part of the code base to support long term

[Firebird-devel] Roadmap for a Distributed Firebird

2015-03-22 Thread James Starkey
Goal: Morph Firebird into a high performance, distributed, fully redundant database. Both JRDs (DEC Rdb/ELN and Interbase) were designed as elastic database systems for VAXClusters. They are share-nothing engines, communication exclusively through a distributed lock manage and network attach dis