<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">IMHO EJB clustering is not the direction we should take, especially considering our IoC plans (see <a href="http://gerrit.ovirt.org/#/c/5575/">http://gerrit.ovirt.org/#/c/5575/</a>).<div>QuartzScheduler can be easily fixed by using a DB for Quartz configuration. We had such a discussion a few weeks ago.</div><div>mod_jk is probably better for our HA.</div><div>Postgres clustering should probably be a different task, as it's more infra and less code.</div><div><br></div><div>Another thing to consider is locking, currently done using synchronized, and will need to be changed somehow (probably using Infinispan).</div><div><br><div><div>On Aug 22, 2013, at 10:22 AM, Itamar Heim wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 08/21/2013 10:27 PM, plysan wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2013/8/22 Itamar Heim <<a href="mailto:iheim@redhat.com">iheim@redhat.com</a> <<a href="mailto:iheim@redhat.com">mailto:iheim@redhat.com</a>>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> On 08/21/2013 11:08 AM, plysan wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> 2013/8/21 Laszlo Hornyak <<a href="mailto:lhornyak@redhat.com">lhornyak@redhat.com</a><br></blockquote><blockquote type="cite"> <<a href="mailto:lhornyak@redhat.com">mailto:lhornyak@redhat.com</a>> <<a href="mailto:lhornyak@redhat.com">mailto:lhornyak@redhat.com</a><br></blockquote><blockquote type="cite"> <<a href="mailto:lhornyak@redhat.com">mailto:lhornyak@redhat.com</a>>>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Hi,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> ----- Original Message -----<br></blockquote><blockquote type="cite"> > From: "plysan" <<a href="mailto:plysab@gmail.com">plysab@gmail.com</a><br></blockquote><blockquote type="cite"> <<a href="mailto:plysab@gmail.com">mailto:plysab@gmail.com</a>> <<a href="mailto:plysab@gmail.com">mailto:plysab@gmail.com</a><br></blockquote><blockquote type="cite"> <<a href="mailto:plysab@gmail.com">mailto:plysab@gmail.com</a>>>><br></blockquote><blockquote type="cite"> > To: <a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a><br></blockquote><blockquote type="cite"> <<a href="mailto:engine-devel@ovirt.org">mailto:engine-devel@ovirt.org</a>> <<a href="mailto:engine-devel@ovirt.org">mailto:engine-devel@ovirt.org</a><br></blockquote><blockquote type="cite"> <<a href="mailto:engine-devel@ovirt.org">mailto:engine-devel@ovirt.org</a>>__><br></blockquote><blockquote type="cite"> > Sent: Wednesday, August 21, 2013 3:49:31 PM<br></blockquote><blockquote type="cite"> > Subject: [Engine-devel] Ideas about engine clustering?<br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"> > Hello, guys:<br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"> > I'm trying to make a jboss clustering environment for<br></blockquote><blockquote type="cite"> engine. But<br></blockquote><blockquote type="cite"> felt the<br></blockquote><blockquote type="cite"> > difficuty too.<br></blockquote><blockquote type="cite"> > So I want to know if any one is working on this? I<br></blockquote><blockquote type="cite"> googled it and<br></blockquote><blockquote type="cite"> haven't<br></blockquote><blockquote type="cite"> > found anything.<br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"> > I know there will be lots of things to do for engine<br></blockquote><blockquote type="cite"> migrating to<br></blockquote><blockquote type="cite"> clustering<br></blockquote><blockquote type="cite"> > environment. I just want to know what problem need to be<br></blockquote><blockquote type="cite"> solved?<br></blockquote><blockquote type="cite"> > I would like to list the things I think that is needed<br></blockquote><blockquote type="cite"> to do(or<br></blockquote><blockquote type="cite"> solve):<br></blockquote><blockquote type="cite"> > 1. run jboss in standalone-ha mode or domain mode.<br></blockquote><blockquote type="cite"> > 2. add @Clustered annotation to each EJB, I think this<br></blockquote><blockquote type="cite"> will solve the<br></blockquote><blockquote type="cite"> > replication problem in cluster, probably lots of details<br></blockquote><blockquote type="cite"> in it.<br></blockquote><blockquote type="cite"> > 3. QuartzScheduler problem, only one node running a<br></blockquote><blockquote type="cite"> scheduler is<br></blockquote><blockquote type="cite"> enough at a<br></blockquote><blockquote type="cite"> > time instead of each node running one.<br></blockquote><blockquote type="cite"> > 4. use mod_cluster to handle load balancing.<br></blockquote><blockquote type="cite"> > 5. postgresql clustering.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> For failover it sounds like a plan, just wondering if this<br></blockquote><blockquote type="cite"> could<br></blockquote><blockquote type="cite"> solve load balancing problems as well.<br></blockquote><blockquote type="cite"> Ovirt is generating a big load on the DB and I would be really<br></blockquote><blockquote type="cite"> interested if SQL DB clustering could solve the issues.<br></blockquote><blockquote type="cite"> It would be great if it could, big part of the scalablity<br></blockquote><blockquote type="cite"> issue is<br></blockquote><blockquote type="cite"> the evil things we did against that poor database.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> > 6. There should be more, but hope anyone can think about<br></blockquote><blockquote type="cite"> it :D<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> There are tons of data structures that are used in oVirt<br></blockquote><blockquote type="cite"> that store<br></blockquote><blockquote type="cite"> state. You will have to hunt all of these down and replace<br></blockquote><blockquote type="cite"> with a<br></blockquote><blockquote type="cite"> data structure that is shared between the cluster memebers.<br></blockquote><blockquote type="cite"> This may<br></blockquote><blockquote type="cite"> be a big lot of work from many parts of the application.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Indeed, and like Yair Zaslavsky said, we can put the data<br></blockquote><blockquote type="cite"> structure in<br></blockquote><blockquote type="cite"> infinispan cache, but clustered EJB can do the same thing for<br></blockquote><blockquote type="cite"> us, right?<br></blockquote><blockquote type="cite"> If all those state values are inside EJBs. (iirc)**<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"> > Any ideas?<br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"> > Thanks!<br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"> > _________________________________________________<br></blockquote><blockquote type="cite"> > Engine-devel mailing list<br></blockquote><blockquote type="cite"> > <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a> <<a href="mailto:Engine-devel@ovirt.org">mailto:Engine-devel@ovirt.org</a>><br></blockquote><blockquote type="cite"> <<a href="mailto:Engine-devel@ovirt.org">mailto:Engine-devel@ovirt.org</a> <<a href="mailto:Engine-devel@ovirt.org">mailto:Engine-devel@ovirt.org</a>>__><br></blockquote><blockquote type="cite"> > <a href="http://lists.ovirt.org/__mailman/listinfo/engine-devel">http://lists.ovirt.org/__mailman/listinfo/engine-devel</a><br></blockquote><blockquote type="cite"> <<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel">http://lists.ovirt.org/mailman/listinfo/engine-devel</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> ><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> _________________________________________________<br></blockquote><blockquote type="cite"> Engine-devel mailing list<br></blockquote><blockquote type="cite"> <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a> <<a href="mailto:Engine-devel@ovirt.org">mailto:Engine-devel@ovirt.org</a>><br></blockquote><blockquote type="cite"> <a href="http://lists.ovirt.org/__mailman/listinfo/engine-devel">http://lists.ovirt.org/__mailman/listinfo/engine-devel</a><br></blockquote><blockquote type="cite"> <<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel">http://lists.ovirt.org/mailman/listinfo/engine-devel</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> unless you need the load balancing, just for HA, hosted-engine<br></blockquote><blockquote type="cite"> should cover your needs?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I think failover and more scalability is what i am interested here.<br></blockquote><blockquote type="cite">Just thinking about the possibilities :)<br></blockquote><blockquote type="cite">Imagine engine would never get restarted from outside view. Cool isn't it?<br></blockquote><br>active/passive failover you should get from hosted-engine (yes, with some downtime)<br>scalability and active-active would be great. iirc, juan looked at implications of doing this a while back<br>_______________________________________________<br>Engine-devel mailing list<br><a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>http://lists.ovirt.org/mailman/listinfo/engine-devel<br></div></blockquote></div><br></div></body></html>