Ha ah! Turning off all binary logging on both mysqld nodes made my
error/issue go away. No more overloaded NDB kernel.
Will turn binlog back on and try increasing some of the binlog buffers
to see if that helps cause obviously turning binlogs off isn't an
acceptable solution.
-Matthew
> -----Original Message-----
> From: Boehm, Matthew [mailto:mboehm@stripped]
> Sent: Tuesday, November 10, 2009 3:44 PM
> To: Jonas.Oreland@stripped
> Cc: Pekka.Nousiainen@stripped; cluster@stripped
> Subject: RE: Send Buffers overloaded in NDB kernel
>
> Hi Jonas,
> Yep. Well, not used --reload but manually deleted the _config.bin file
> before starting up the manager again. Then once a rolling restart is
> complete, I use ndb_config to make sure it took:
>
> ndb_config -c 15001LDMGR01 --type=ndbd -q
> NodeId,DataMemory,TotalSendBufferMemory
> 1,12884901888,257949696 2,12884901888,257949696
>
> 257949696 = 256M
>
> I have since removed that setting since Pekka said the error I'm
> getting
> actually has nothing to do with TCP/IP buffers. It seems to be related
> to binloging on the mysqld servers.
>
> -Matthew
>
> > -----Original Message-----
> > From: Jonas.Oreland@stripped [mailto:Jonas.Oreland@stripped]
> > Sent: Tuesday, November 10, 2009 3:40 PM
> > To: Boehm, Matthew
> > Cc: Pekka.Nousiainen@stripped; cluster@stripped
> > Subject: Re: Send Buffers overloaded in NDB kernel
> >
> > Hi,
> >
> > just a thought,
> >
> > can it be that your config changes has not taken effect
> > since the 7.0 ndb_mgmd needs to be started with "--reload" to
> actually
> > reload the config.ini
> >
> > /Jonas
> >
> > Boehm, Matthew wrote:
> > > So I altered sysbench and dropped the 100 char update statement
> down
> > to
> > > 9 (UPDATE sbtestndb set c='14435575' where id=624923, with id = PK
> > and c
> > > = non-indexed column) and within 10 seconds of the 64 thread test,
> > hit
> > > the error. Didn't bother with 128 and 256 tests.
> > >
> > > You say this has to do with each ndbd sending statuses/updates to
> > each
> > > mysqld? I've got two connected to the cluster but only running the
> > tests
> > > on 1.
> > >
> > > -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
> > >
> > >
> > > --
> > > MySQL Cluster Mailing List
> > > For list archives: http://lists.mysql.com/cluster
> > > To unsubscribe:
> > http://lists.mysql.com/cluster?unsub=1
> > >
>
>
> --
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe:
> http://lists.mysql.com/cluster?unsub=1
