Issue 6203 - Problem & solution for back-ndb issue connecting to Cluster data nodes
Summary: Problem & solution for back-ndb issue connecting to Cluster data nodes
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.16
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-09 13:51 UTC by andrew.morgan@sun.com
Modified: 2014-08-01 21:04 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description andrew.morgan@sun.com 2009-07-09 13:51:17 UTC
Full_Name: Andrew Morgan
Version: 2.4.16
OS: Ubuntu
URL: 
Submission from: (NULL) (90.193.196.76)


I am running MySQL Cluster with data nodes all running on the same host.

I configured, built and installed OpenLDAP with back-ndb but when I run "slapd
-d 5", it failed with "ndb_db_open: ni_cluster[0]->wait failed (1)".

Looking at the code in "back-ndb/init.cpp" this implies that it was able to
connect to the Cluster management node but only the first of the data nodes. The
cause of this is line 133:  "ni->ni_cluster[i]->wait_until_ready( 30, 0 );" -
the 30,0 means wait up to 30 seconds for first data node but then no time at all
for the others; the fact that the method returned 1 means that the first node
was found to be live. The second parameter should be set to a non-zero value to
give the other data nodes chance to show as being live. I changed the 0 to 30,
recompiled/installed and slapd came up correctly.
Comment 1 andrew.morgan@sun.com 2009-07-09 14:18:29 UTC
wait_until_ready is documented here:
http://dev.mysql.com/doc/ndbapi/en/class-ndb-cluster-connection-methods.html
#class-ndb-cluster-connection-wait-until-ready 

-----Original Message-----
From: openldap-its@OpenLDAP.org [mailto:openldap-its@OpenLDAP.org] 
Sent: 09 July 2009 14:51
To: Andrew.Morgan@Sun.COM
Subject: Re: (ITS#6203) Problem & solution for back-ndb issue connecting to
Cluster data nodes


*** THIS IS AN AUTOMATICALLY GENERATED REPLY ***

Thanks for your report to the OpenLDAP Issue Tracking System.  Your
report has been assigned the tracking number ITS#6203.

One of our support engineers will look at your report in due course.
Note that this may take some time because our support engineers
are volunteers.  They only work on OpenLDAP when they have spare
time.

If you need to provide additional information in regards to your
issue report, you may do so by replying to this message.  Note that
any mail sent to openldap-its@openldap.org with (ITS#6203)
in the subject will automatically be attached to the issue report.

	mailto:openldap-its@openldap.org?subject=(ITS#6203)

You may follow the progress of this report by loading the following
URL in a web browser:
    http://www.OpenLDAP.org/its/index.cgi?findid=6203

Please remember to retain your issue tracking number (ITS#6203)
on any further messages you send to us regarding this report.  If
you don't then you'll just waste our time and yours because we
won't be able to properly track the report.

Please note that the Issue Tracking System is not intended to
be used to seek help in the proper use of OpenLDAP Software.
Such requests will be closed.

OpenLDAP Software is user supported.
	http://www.OpenLDAP.org/support/

--------------
Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.


Comment 2 Howard Chu 2009-07-13 11:24:26 UTC
changed notes
changed state Open to Test
moved from Incoming to Software Bugs
Comment 3 Quanah Gibson-Mount 2009-07-22 19:51:24 UTC
changed notes
changed state Test to Release
Comment 4 Quanah Gibson-Mount 2009-09-08 16:43:29 UTC
changed notes
changed state Release to Closed
Comment 5 OpenLDAP project 2014-08-01 21:04:23 UTC
fixed in HEAD
fixed in RE24