MonetDB concurrent commits exception
Y.Zhang at cwi.nl
Fri Nov 13 15:01:54 CET 2015
This blog might give you the answers you’re looking for.
In general, it’s no big deal (in MonetDB) if your transactions get aborted due concurrency conflicts. You can just retry the transaction until it succeeded. However, if the level of concurrency is high, you might want to introduce a random break before retrying a transaction.
> On Nov 13, 2015, at 14:45, Vijay Krishna <vijayakrishna55 at gmail.com> wrote:
> I am running a setup on MonetDB where in concurrent transactions take place. Everything works very fine but for a few transactions getting aborted due to SQLExceptions.
> I have set auto commit to false for all these transactions. I am getting frequent SQLExceptions with the message as
> java.sql.SQLException: COMMIT: failed
> But if I retry the same transaction, this works fine. Any idea on what would be the reason for frequent commit fails?
> When I set auto commit to true for the transactions, I get similarly frequent Exceptions but the message becomes
> java.sql.SQLException: COMMIT: transaction is aborted because of concurrency conflicts
> Is it like both the exception thrown be for the same cause?
> Any help much appreciated.
> Thanks in Advance.
> Mobile : (+91) 9500402305.
> users-list mailing list
> users-list at monetdb.org
More information about the developers-list