Mulgara Project: Issueshttps://code.mulgara.org/https://code.mulgara.org/favicon.ico?15861924492008-10-23T13:56:58ZMulgara Project
Redmine Mulgara - Feature #163 (New): Improve performance of distributed resolverhttps://code.mulgara.org/issues/1632008-10-23T13:56:58Zronald -ronald@foo.bar
<p>Right now the distributed resolver seems somewhat overly slow. The<br />queries take quite some time, as well as there being a long (100ms on<br />my machine) unexplained pause between prepare and commit.</p> Mulgara - Bug #162 (New): Transactions involving transactional resolvers do not have snapshot iso...https://code.mulgara.org/issues/1622008-10-23T13:40:30Zronald -ronald@foo.bar
<p>See <a class="external" href="http://www.topazproject.org/trac/ticket/1036">http://www.topazproject.org/trac/ticket/1036</a> for the scenario. Because<br />resolvers are enlisted lazily, mulgara suffers from the same problem. But<br />attempting to always enlist all resolvers at the beginning of every transaction<br />may be quite expensive, and is also in the case of the distributed resolver<br />nearly impossible.</p>
<p>We may want to add a flag so users can choose whether they want this or not.</p> Mulgara - Feature #161 (New): Support recovery in distributed resolver's MultiXAResourcehttps://code.mulgara.org/issues/1612008-10-23T13:35:25Zronald -ronald@foo.bar
<p>Transactions are currently not remembered across restarts. We could possibly<br />store transactions and their states locally in a graph.</p> Mulgara - Bug #83 (Feedback): Mulgara fails to start after abrupt terminationhttps://code.mulgara.org/issues/832008-03-07T06:07:03Zronald -ronald@foo.bar
<p>I killed mulgara abruptly, and subsequently it failed to start.<br />According to Andrae's initial analysis, the problem is that mulgara<br />assumes during recovery that certain deleted structures are internally<br />valid when in this case they aren't.</p>
<p>Attached is the db from after the crash. The failure to recover seems to<br />be reproducable only on 32-bit jvm's, and even then not consistently<br />(due to the timing between certain operations).</p>