On Thu, 2006-07-06 at 10:28 +0200, Michel Stam wrote:
> Ok, in that case I'll refrain from posting the bugs so as not to
> needlessly bother the mysql developers. I can work around the problem
> easily enough, anyway.
>
> I'll make a couple of additions to the INSTRUCTIONS file with these
> issues, so that people running 4.1 wanting to compile this don't have
> to figure it out for themselves.
Great - this is probably best. It is highly unlikely that anybody is
going to deploy 4.1 Cluster at this stage (5.0 at least). However, some
may want to add this on... but I would say most people these days are
going with 5.0 or plan to upgrade soon.
> Another thing that came to mind yesterdaynight;
> I know that its possible to get events from the NDB cluster. However,
> as far as I know this is only in the form of a character string. Is it
> possible to read these events out in more detail (perhaps a structure
> with information pertaining to the node(s) involved)?
>
> Given that, it might be an idea to send out SNMP traps for these too?
> That way you can see when for instance a disk node dies, or perhaps
> when a backup is started / completed.
Have a look at the (recently uploaded) NDB API docs in the MGM API.
http://dev.mysql.com/doc/ndbapi/en/struct-ndb-logevent.html
Each event has different information, but most have all that you would
need.
>
>
>
--
Stewart Smith, Software Engineer
MySQL AB, www.mysql.com
Office: +14082136540 Ext: 6616
VoIP: 6616@stripped
Mobile: +61 4 3 8844 332
Jumpstart your cluster:
http://www.mysql.com/consulting/packaged/cluster.html
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
