Re: 5.1.6-alpha NDB: Could not get apply status share

[Eric Gonia]

I am getting the same error with 5.1.7-beta. x86_64 version.

When I start mysqld-max I get this in the .err file:
060303 14:11:45 [Note] Starting MySQL Cluster Binlog Thread
060303 14:11:45 InnoDB: Started; log sequence number 0 43655
060303 14:11:45 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.7-beta-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)
060303 14:11:45 [ERROR] NDB: Could not get apply status share


When I attempt to start mysqld-debug I get this in the .err file:
060303 14:16:02 [Note] Starting MySQL Cluster Binlog Thread
060303 14:16:02 InnoDB: Started; log sequence number 0 43655
060303 14:16:02 [Note] /usr/sbin/mysqld-debug: ready for connections.
Version: '5.1.7-beta-debug-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Debug (GPL)
mysqld-debug: sql_base.cc:2432: void assign_new_table_id(TABLE_SHARE*): Assertion `(&share->mutex)->count > 0 && pthread_equal(pthread_self(), (&share->mutex)->thread)' failed.
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=402653184
read_buffer_size=2093056
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1621615 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Here's the last little bit out of the trace file:
T@10746207: | | | | | | | >bitmap_init
T@10746207: | | | | | | | <bitmap_init
T@10746207: | | | | | | <set_up_partition_bitmap
T@10746207: | | | | | | >check_range_capable_PF
T@10746207: | | | | | | <check_range_capable_PF
T@10746207: | | | | | | >set_up_partition_key_maps
T@10746207: | | | | | | | >check_fields_in_PF
T@10746207: | | | | | | | <check_fields_in_PF
T@10746207: | | | | | | <set_up_partition_key_maps
T@10746207: | | | | | | >set_up_partition_func_pointers
T@10746207: | | | | | | <set_up_partition_func_pointers
T@10746207: | | | | | | info: thd->set_query_id: 1
T@10746207: | | | | | <fix_partition_func
T@10746207: | | | | <open_table_from_share
T@10746207: | | | | >assign_new_table_id


Are these issues related?
Should I open a bug report?