I’m evaluating SciDB for a high-availability application, but there appear to be multiple single-points of failure, and I’m having a hard time distinguishing between SciDB and Paradigm4(P4) functionality.
According to http://www.scidb.org/forum/viewtopic.php?f=6&t=701 if any node’s disk goes away, all data stored on that disk is unavailable unless you have an unnamed P4 extension. Is that interpretation correct? Will the database continue running without that disk? Or will it crash?
According to http://www.scidb.org/forum/viewtopic.php?f=6&t=515 there may be some sort of worker redundancy built in so that k servers can go down without bringing down the whole SciDB database. But P4 extensions are mentioned, so is that native or P4 functionality? If native, how, if no data redundancy is provided as mentioned in the previous link?
What happens if the master node fails? What would a decent failover procedure look like?
When answering please make sure to be clear about what’s provided by native Open Source SciDB, and by Proprietary P4 extensions?