Hi,
On Fri, Aug 12, 2016 at 12:26 PM, Kristian Nielsen wrote:
>
>
> From a quick look at the patch, this seems to be because of code removed
> from innobase_kill_query(). Specifically:
>
> > @@ -4799,65 +5511,11 @@ innobase_kill_query(
> >
Hello Kristian,
I am running your opt2 branch with a small sysbench oltp test (1 table,
1000 rows, 8 threads). the good news is that the slave stalls due to lock
timeouts are gone. the bad news is that the slave performance is suspect.
when slave in conservative mode with 2 threads, the tokudb
[Moving the discussion to maria-developers@, hope that is ok/makes sense...]
Ok, so here is a proof-of-concept patch for this, which seems to make TokuDB
work with optimistic parallel replication.
The core of the patch is this line in lock_request.cc
lock_wait_callback(callback_data,
Jan Lindström writes:
> I have reached to situation where I need help fixing remaining test
> failures and mentoring is current status good enough for 10.2 Beta. I need
> help on test failures on parts where I do not follow why test is failing or
> server crashes I do
4 matches
Mail list logo