You can modify this behavior in MongoDB by changing the "write concern" [1] to ensure that the MongoDB client only returns to the caller when at least one of the replicas has acknowledged the data. The problem is that if you do that the performance drops dramatically. In my opinion, MongoDB is only suitable for storing non-critical data. I would never use it for a failover solution with FreeSWITCH. BTW, moving from a relational database to a NoSQL one is not trivial at all, especially if your application requires any kind of transactionality from the DB. [1] http://docs.mongodb.org/manual/core/write-concern/ On Thu, Aug 1, 2013 at 5:19 PM, Patrick Lists < freeswitch-list@puzzled.xs4all.nl> wrote:
On 08/01/2013 09:45 PM, john@millican.us wrote: [snip]
I have used many SQL db and a few NoSQL and the NoSQL are much faster, easier to scale, and just plain more fun. My opinion and of course YMMV
Doesn't MongoDB acknowledge a write when it still has the data in mem as opposed to written on disk? So when the power fails and both FreeSWITCH server 1 and MongoDB server 1 are down there was data in memory that has not been replicated to MongoDB server 2. How is that going to result in proper failover? How can you fire up FreeSWITCH server 2 with all call data when MongoDB server 2 does not have all the call data? I'm no NoSQL expert so would love to hear how a NoSQL based solution could do the job reliably.
Regards, Patrick
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org