<div dir="ltr">I&#39;ve added a wiki page on Engine HA. <a href="http://www.ovirt.org/Features/Engine_High_Availability">http://www.ovirt.org/Features/Engine_High_Availability</a><div>Please add your comments, we&#39;ll try to make this an ongoing effort.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 24, 2013 at 3:25 PM, Liran Zelkha <span dir="ltr">&lt;<a href="mailto:liran.zelkha@gmail.com" target="_blank">liran.zelkha@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">IMHO EJB clustering is not the direction we should take, especially considering our IoC plans (see <a href="http://gerrit.ovirt.org/#/c/5575/" target="_blank">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&#39;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><div class="h5"><div><br><div><div>On Aug 22, 2013, at 10:22 AM, Itamar Heim wrote:</div>
<br><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 &lt;<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a> &lt;<a href="mailto:iheim@redhat.com" target="_blank">mailto:iheim@redhat.com</a>&gt;&gt;<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 &lt;<a href="mailto:lhornyak@redhat.com" target="_blank">lhornyak@redhat.com</a><br></blockquote><blockquote type="cite">        &lt;<a href="mailto:lhornyak@redhat.com" target="_blank">mailto:lhornyak@redhat.com</a>&gt; &lt;<a href="mailto:lhornyak@redhat.com" target="_blank">mailto:lhornyak@redhat.com</a><br>
</blockquote><blockquote type="cite">        &lt;<a href="mailto:lhornyak@redhat.com" target="_blank">mailto:lhornyak@redhat.com</a>&gt;&gt;&gt;<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">
              &gt; From: &quot;plysan&quot; &lt;<a href="mailto:plysab@gmail.com" target="_blank">plysab@gmail.com</a><br></blockquote><blockquote type="cite">        &lt;<a href="mailto:plysab@gmail.com" target="_blank">mailto:plysab@gmail.com</a>&gt; &lt;<a href="mailto:plysab@gmail.com" target="_blank">mailto:plysab@gmail.com</a><br>
</blockquote><blockquote type="cite">        &lt;<a href="mailto:plysab@gmail.com" target="_blank">mailto:plysab@gmail.com</a>&gt;&gt;&gt;<br></blockquote><blockquote type="cite">              &gt; To: <a href="mailto:engine-devel@ovirt.org" target="_blank">engine-devel@ovirt.org</a><br>
</blockquote><blockquote type="cite">        &lt;<a href="mailto:engine-devel@ovirt.org" target="_blank">mailto:engine-devel@ovirt.org</a>&gt; &lt;<a href="mailto:engine-devel@ovirt.org" target="_blank">mailto:engine-devel@ovirt.org</a><br>
</blockquote><blockquote type="cite">        &lt;<a href="mailto:engine-devel@ovirt.org" target="_blank">mailto:engine-devel@ovirt.org</a>&gt;__&gt;<br></blockquote><blockquote type="cite">              &gt; Sent: Wednesday, August 21, 2013 3:49:31 PM<br>
</blockquote><blockquote type="cite">              &gt; Subject: [Engine-devel] Ideas about engine clustering?<br></blockquote><blockquote type="cite">              &gt;<br></blockquote><blockquote type="cite">              &gt; Hello, guys:<br>
</blockquote><blockquote type="cite">              &gt;<br></blockquote><blockquote type="cite">              &gt; I&#39;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">              &gt; difficuty too.<br></blockquote><blockquote type="cite">              &gt; 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&#39;t<br></blockquote><blockquote type="cite">              &gt; found anything.<br></blockquote><blockquote type="cite">
              &gt;<br></blockquote><blockquote type="cite">              &gt; 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">              &gt; environment. I just want to know what problem need to be<br></blockquote><blockquote type="cite">        solved?<br></blockquote><blockquote type="cite">
              &gt; 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">
              &gt; 1. run jboss in standalone-ha mode or domain mode.<br></blockquote><blockquote type="cite">              &gt; 2. add @Clustered annotation to each EJB, I think this<br></blockquote><blockquote type="cite">
        will solve the<br></blockquote><blockquote type="cite">              &gt; replication problem in cluster, probably lots of details<br></blockquote><blockquote type="cite">        in it.<br></blockquote><blockquote type="cite">
              &gt; 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">
              &gt; time instead of each node running one.<br></blockquote><blockquote type="cite">              &gt; 4. use mod_cluster to handle load balancing.<br></blockquote><blockquote type="cite">              &gt; 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">              &gt; 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">              &gt;<br></blockquote><blockquote type="cite">              &gt; Any ideas?<br>
</blockquote><blockquote type="cite">              &gt;<br></blockquote><blockquote type="cite">              &gt; Thanks!<br></blockquote><blockquote type="cite">              &gt;<br></blockquote><blockquote type="cite">
              &gt; _________________________________________________<br></blockquote><blockquote type="cite">              &gt; Engine-devel mailing list<br></blockquote><blockquote type="cite">              &gt; <a href="mailto:Engine-devel@ovirt.org" target="_blank">Engine-devel@ovirt.org</a> &lt;<a href="mailto:Engine-devel@ovirt.org" target="_blank">mailto:Engine-devel@ovirt.org</a>&gt;<br>
</blockquote><blockquote type="cite">        &lt;<a href="mailto:Engine-devel@ovirt.org" target="_blank">mailto:Engine-devel@ovirt.org</a> &lt;<a href="mailto:Engine-devel@ovirt.org" target="_blank">mailto:Engine-devel@ovirt.org</a>&gt;__&gt;<br>
</blockquote><blockquote type="cite">              &gt; <a href="http://lists.ovirt.org/__mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/__mailman/listinfo/engine-devel</a><br></blockquote><blockquote type="cite">
        &lt;<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a>&gt;<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">
              &gt;<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" target="_blank">Engine-devel@ovirt.org</a> &lt;<a href="mailto:Engine-devel@ovirt.org" target="_blank">mailto:Engine-devel@ovirt.org</a>&gt;<br>
</blockquote><blockquote type="cite">        <a href="http://lists.ovirt.org/__mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/__mailman/listinfo/engine-devel</a><br></blockquote><blockquote type="cite">
        &lt;<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a>&gt;<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&#39;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" target="_blank">Engine-devel@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
</div></blockquote></div><br></div></div></div></div></blockquote></div><br></div>