[Design of JBoss Collaboration Server] - Re: JBMS Alternate Datastore
by csand101
Thanks for the reply sappenin. The latest topology for a MySQL cluster is a synchronous cluster where the mysqld SQL server is sitting on top of a clustered db engine which is spread across many machines. There is no master or backups. They are equal. This means each node can be used rather than just sitting and waiting for another to fail.
So ip takeover is not the answer since wouldn't allow usage of all db nodes.
Loadbalancer would work, yes, but getting too complex for a "simple" email instalation since requires 3 layers of hardware just to store an email.
What makes sense to me, as a simple solution, is that each JBMS server can use a particluar db node. But then there is the issue as posted of what happens to JBMS when it's db node goes down? There is still at least one more db running on another ip. JBMS just needs to start using a different one.
As you mention, if JBMS could manage a pool of connections to different databases in the db farm that would be nice.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959643#3959643
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959643
19 years, 8 months
[Design of Kosmos] - Re: serviceResultUpdaterJob not traversing repository
by sstuart4
One more thing I wanted to post...
| 2006-07-18 12:02:51,574 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
| 2006-07-18 12:02:51,575 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
|
| 2006-07-18 14:02:51,561 DEBUG [org.quartz.core.JobRunShell] Calling execute on job DEFAULT.serviceResultUpdaterJob
| 2006-07-18 14:02:51,562 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
|
| 2006-07-18 16:02:51,562 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
| 2006-07-18 16:02:51,562 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
|
| 2006-07-18 18:02:51,559 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
| 2006-07-18 18:02:51,560 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
|
| 2006-07-18 20:02:51,554 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
| 2006-07-18 20:02:51,554 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
|
| 2006-07-18 22:02:51,562 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
| 2006-07-18 22:02:51,562 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
|
This is over the course of a day when I am positive that changes where submitted to the repository and it was listed as one of the monitored urls in the portlet.xml.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959621#3959621
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959621
19 years, 8 months
[Design of JBoss Collaboration Server] - Re: JBMS Alternate Datastore
by sappenin
I can think of a couple alternatives (although, not sure how good they are).
1.) Put the MySql Master (or all of MySql boxes) in a Linux cluster. Imagine 2 boxes in a cluster. I'm pretty sure you can configure it so that one node is a "master", and if it dies, then the other node takes over the "Master's" IP address. You would probably want to separate your storage from any one server in the cluster. (i.e. using a SAN). Plus, I'm not sure if the server that "becomes the Master" can actually be used while it's in waiting (e.g., It may need to be dormant). However, with 3 boxes, you could have a 2-box Linux Cluster, with 1 backup master. If both masters go down, though, then the cluster would fail. Not sure if you can make all the boxes in a cluster "capable of becoming the master".
2.) I believe there are Linux-based Load Balancers with failover capabilities out there. So, you'd have "x" number of Jboss servers connecting to a single IP on the Linux Load balancer server, which would farm requests out to "y" number of MySql Master/Slave boxes NOT in a cluster (even Windows boxes). It seems like the Load-balancer would just heartbeat the downstream boxes, and if one doesn't answer, then mark it as down?
I would be curious to hear of any JBoss + Database specific technologies that might be able to address this, too. E.g., does JBoss Cluster technology have any ability to farm database requests out to multiple databse servers? I don't know the answer to that one.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959596#3959596
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959596
19 years, 8 months