Ok. Interesting results. So I have 2 mysqld (MYS01 and MYS02) and 2 NDB.
1 of the mysqld (MYS01) is the one running the sysbench tests and had
all the binlog stuff turned off. But I left all of that turned on on
MYS02. Running the tests, I get the errors.
But then I shutdown MYS02 and now everything works! I repeated the test
twice to make sure. Then started MYS02 back up, ran the test again and
immediately hit the error.
Going to turn off all the bin-log stuff on MYS02 and see if that affects
anything.
-Matthew
> -----Original Message-----
> From: Pekka.Nousiainen@stripped [mailto:Pekka.Nousiainen@stripped]
> Sent: Tuesday, November 10, 2009 1:37 PM
> To: cluster@stripped
> Subject: Re: Send Buffers overloaded in NDB kernel
>
> On 091110, Boehm, Matthew wrote:
> > Interestingly, if I run the "update_index" bench (ie: UPDATE table
> SET
> > indexedColum=indexedColumn+1 WHERE PKcolumn=<rand>), that one runs
> just
> > fine all the way up to 256 threads.
> >
> > But if I try the update_nonindex, (ie: UPDATE table SET
> > nonIdxColum='<random 100 char string>' WHERE PKcolumn=<rand>), that
> is
> > the one that fails right away on the 64/128/256 thread bench.
>
> Updating indexed column takes lots of time (relatively speaking).
> So maybe that's what keeps the traffic low enough to not hit
> send buffer limit.
>
> If binlogging is off and you're not selecting masses of data
> to API, that leaves the update traffic. Maybe somebody else
> knows if it's possible to hit send buffer limit here.
>
> --
> Pekka Nousiainen, Software Engineer, Sun Microsystems / MySQL
>
> --
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe:
> http://lists.mysql.com/cluster?unsub=1
