2013/8/22 Itamar Heim <iheim(a)redhat.com <mailto:email@example.com>>
On 08/21/2013 11:08 AM, plysan wrote:
2013/8/21 Laszlo Hornyak <lhornyak(a)redhat.com
----- Original Message -----
> From: "plysan" <plysab(a)gmail.com
> To: engine-devel(a)ovirt.org
> Sent: Wednesday, August 21, 2013 3:49:31 PM
> Subject: [Engine-devel] Ideas about engine clustering?
> Hello, guys:
> I'm trying to make a jboss clustering environment for
> difficuty too.
> So I want to know if any one is working on this? I
googled it and
> found anything.
> I know there will be lots of things to do for engine
> environment. I just want to know what problem need to be
> I would like to list the things I think that is needed
> 1. run jboss in standalone-ha mode or domain mode.
> 2. add @Clustered annotation to each EJB, I think this
will solve the
> replication problem in cluster, probably lots of details
> 3. QuartzScheduler problem, only one node running a
enough at a
> time instead of each node running one.
> 4. use mod_cluster to handle load balancing.
> 5. postgresql clustering.
For failover it sounds like a plan, just wondering if this
solve load balancing problems as well.
Ovirt is generating a big load on the DB and I would be really
interested if SQL DB clustering could solve the issues.
It would be great if it could, big part of the scalablity
the evil things we did against that poor database.
> 6. There should be more, but hope anyone can think about
There are tons of data structures that are used in oVirt
state. You will have to hunt all of these down and replace
data structure that is shared between the cluster memebers.
be a big lot of work from many parts of the application.
Indeed, and like Yair Zaslavsky said, we can put the data
infinispan cache, but clustered EJB can do the same thing for
If all those state values are inside EJBs. (iirc)**
> Any ideas?
> Engine-devel mailing list
> Engine-devel(a)ovirt.org <mailto:Enginefirstname.lastname@example.org>
Engine-devel mailing list
unless you need the load balancing, just for HA, hosted-engine
should cover your needs?
I think failover and more scalability is what i am interested here.
Just thinking about the possibilities :)
Imagine engine would never get restarted from outside view. Cool isn't it?
active/passive failover you should get from hosted-engine (yes, with
scalability and active-active would be great. iirc, juan looked at
implications of doing this a while back