too large transactions not handled gracefully

[Seppo Jaakola]

Replication provider can have limits for how many queries can be inside a transaction. Galera has 65535 as a limit for queries. However, when this limit is reached, mysqld does not rollback the query, but allows the transaction to commit locally.

The Galera library has also a but in detecting query limit, and currently crashes for too large transactions.

[Seppo Jaakola (seppo-jaakola)]

Query limit check has been added. However, Galera library by default does not append queries in write sets, so this issue does not even manifest by defaulot configuration

[Alex Yurchenko (ayurchen)]

Hi Seppo,

I think it should be a row limit check, since we have limit on rows. And
you probably should not mark it as "Fix committed" unless there really is a
fix. If it is not going to be properly fixed for 0.7.4, then it should be
just rescheduled to 0.7.5

Otherwise we'll have a mess in our books.

On Mon, 24 May 2010 08:03:21 -0000, Seppo Jaakola
<email address hidden> wrote:
> Query limit check has been added. However, Galera library by default
> does not append queries in write sets, so this issue does not even
> manifest by defaulot configuration
>
> ** Changed in: codership-mysql
> Milestone: None => 0.7.4
>
> ** Changed in: codership-mysql
> Assignee: (unassigned) => Seppo Jaakola (seppo-jaakola)
>
> ** Changed in: codership-mysql/0.7
> Status: In Progress => Fix Committed
>
> ** Changed in: codership-mysql
> Status: New => In Progress

--
Alexey Yurchenko,
Codership Oy, www.codership.com
Skype: alexey.yurchenko, Phone: [phone]