Thanks for all the replies. Guess I just need to keep it simple. Appreciate it.
On Tue, Apr 20, 2010 at 7:28 PM, Brad Bendy <[email protected]>wrote: > Hi, > > Master-master works very well, if you have that much traffic you can > write to both at the same time and then you should be able to load > balance your billing processes between the two, one master would use > even keys one would use odd keys so you never have a overlapping primary > id. > > >From our experience keep your acc table small and all is well, we only > keep 24-48 hours in the acc table and nightly move/delete to a archive > table, if we ever need the original acc entries we still have them and > we have had 0 issues with performance > > Ive got one machine that is a dual core Xeon sequence 3000 that can run > 4,000+ QPS all day long with no issues, that's on cheap SATA hard drives > and it does very well actually. > > -Brad > > On Tue, 2010-04-20 at 22:23 +0100, Stanisław Pitucha wrote: > > Hi, > > You may have different environment at your site, but this is my > experience: > > > > - NDB is hard to setup / maintain - it might seem easy at the start > > (trivial even), but when something fails and a node doesn't want to > > reconnect to the cluster again, you're left on your own with the source. > > Not many people know NDB and since it's not included in the standard > > package anymore, not many will learn. It's also sometimes hard to figure > > out which node has problems - sometimes frontend doesn't connect because > > of manager problems. > > - I don't think you can actually create a monitoring tool which is able > > to report the precise problem for you - many times when I had a node > > which could not connect, the only people who could help me were ones on > > irc after looking though a long debug log from the node starting up. > > - Opensips schema is simple and trivial to replicate with id skipping. > > Whatever you're trying to achieve with NDB, will be very likely possible > > with master-master replication between standard mysql hosts. > > - Unless you're handling all the calls of a small city, one host (with > > enough memory and cpu for handling databases) is enough to support all > > your needs. > > > > After a couple of spectacular failures of the NDB setup, I migrated to a > > master-master replication with one ip failover (so that only one db at a > > time gets the actual mysql traffic). I haven't touched it since then. > > If you have some experience with managing NDB, or handle enough traffic > > to justify it - go for it. But I would recommend scaling down - most > > likely NDB would just add new parts which can fail in new ways. > > > > Stan > > > > PS. I tried this around 2 years ago - things might have changed since > then. > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- -- *--*--*--*--*--* Duane *--*--*--*--*--* --
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
