> 25.09.2014 21:58, Leyne, Sean wrote: > > All changes are written to disk first > > Which one in, say, ten nodes cluster?
A cluster share always has an elected/nominated primary node (set per share/resource). The non-primary nodes can service all requests but write requests are re-directed to the primary node. So, you can have many readers, only 1 writer. > > Further, all that is required for a write operation is to send a > > message which invalidates the cache object when the write happens. > > The propogation of the changed data can be done later, if the other > > nodes get a request of the block in the meantime, they can read the > > data from disk, > > Wait a second... Do I understand right that Windows storage cluster must > have a single shared storage? 8-O Yes, it uses shared storage, but that it not a real limitation. It is possible for different sets of nodes [say node 1, 2 and 3] (within a single cluster) to service different resources, based on their visibility: - You could have 2 shared storage device pools, so nodes 1 and 2 could be connected to storage A and nodes 1 & 3 connected to storage B. Or, - You could connect all the nodes to all of the SAS storage devices via SAS switches (overall limit is 4 pools of 80 disks each, per cluster). Sean ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel