4 ms·

Sounds a lot like the HyPra / ClustRa system. http://books.google.com/books?id=KH_kfSsMu80C&dq=HypRa+ClustRa+parallel+Database&source=gbs_navlinks_s http://boo

• phliar 16y ago
  You mean the Clustra that was acquired by Sun and renamed HADB? I used it, and as far as I can remember, the HADB fault-tolerant story was that each node has a mirror that takes over if the first fails; and it's basically all in-memory. The Clustrix redundancy granularity is much finer, and everything is on disk.
  • bayareaguy 16y ago
    I never worked with one, but I believe the HyPra system included disks (as shown on page 148. http://books.google.com/books?id=KH_kfSsMu80C&pg=PA148 http://books.google.com/books?id=KH_kfSsMu80C&pg=PA148 ). I recall it was one of the earlier systems to achieve high transaction rates by logging updates to memories of multiple replicas (described on page 181: http://books.google.com/books?id=KH_kfSsMu80C&pg=PA181 http://books.google.com/books?id=KH_kfSsMu80C&pg=PA181 ).
    • phliar 16y ago
      Clustra/HADB did use disks (can't have all your data disappear if you turn off the cluster!) but a running system was in-mem in operation -- if your database was much bigger than the RAM available it was unusable. (I never used Hypra.)
• phliar 16y ago
  For anyone else interested in Clustra: Sun used to have decent HADB docs and whitepapers on bigadmin, but I can't find them any more in the new Oracle world. The two Sun projects that used HADB were Glassfish (clustered fault-tolerant app server, used HADB for session persistence data) and Honeycomb (clustered fault-tolerant archival storage, used HADB for metadata). Examples of how these systems used Clustra are on the web; in both cases the database size was small.