MySQL Bugs: #37784: Passing a 0 timeout value to ndb_logevent_get

Bug #37784	Passing a 0 timeout value to ndb_logevent_get_next will block
Submitted:	1 Jul 2008 23:38	Modified:	14 Aug 2008 9:45
Reporter:	Brian Morin
Status:	Closed
Category:	Server: Docs	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Jon Stephens	Target Version:
Triage:	D4 (Minor)

Description:
http://dev.mysql.com/doc/ndbapi/en/ndb-logevent-get-next.html

Passing 0 as a paramter to timeout will cause this function to block until there is a new
log event.  Please update the documentation.

How to repeat:
n/a

It's not determined that this is intentional behaviour. Until that's done, this is a
development bug, not a docs bug.

Verifier: If this is intentional behaviour, please change category back to Docs, assign
to me, and set Stefan as lead. Otherwise, it needs to be fixed by the Cluster Team.

Thanks.

Looking at how the method is implemented it is expected behavior that a timeout value of
zero requests blocking behavior:

extern "C"
int ndb_logevent_get_next(const NdbLogEventHandle h,
                          struct ndb_logevent *dst,
                          unsigned timeout_in_milliseconds)
{
  if (timeout_in_milliseconds == 0)
  {
    int res;
    while ((res = ndb_logevent_get_next(h, dst, 60000))==0);
    return res;
  }

as requested.

Thank you for your bug report. This issue has been committed to our source repository of
that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available
version, including the bug fix. More information about accessing the source trees is
available at

    http://dev.mysql.com/doc/en/installing-source.html