Bug #10027 Scan causes single node crash in Dbtup
Submitted: 20 Apr 2005 10:16 Modified: 22 May 2005 8:40
Reporter: Johan Andersson Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:mysql 5.0.4 OS:Linux (RHEL 4)
Assigned to: Assigned Account CPU Architecture:Any

[20 Apr 2005 10:16] Johan Andersson 
Description:
Starting a few threads each doing queries of type
SELECT * FROM TABLE WHERE PK1=a and PK2=b and PK3=c and PK4 in (1, ... , 100)

DBTC (line 8739).

How to repeat:
Will put together more info about this
[20 Apr 2005 11:31] Martin Skold 
Looks like it should be a multi-read-range query
[20 Apr 2005 14:03] Martin Skold 
Need more info, such as table definition
[22 Apr 2005 8:40] Jonas Oreland 
Hi,

I can't reproduce this...can you?

Comment: why do you expect ordered index scan when you have infact specified
  full primary keys?

BTW: the TC crash is already solved...is this something else aswell?
[22 May 2005 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".