Bug #48753 | Search an ordered index after update sometimes fails | ||
---|---|---|---|
Submitted: | 13 Nov 2009 8:27 | Modified: | 4 Jan 2010 10:50 |
Reporter: | Marco Tusa | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | 7.0.9a, Orderd index, search, UPDATE |
[13 Nov 2009 8:27]
Marco Tusa
[13 Nov 2009 9:03]
Jonas Oreland
just checking: how do you make sure that your 70 client access distinct data. I.e that multiple threads don't use same rows ? /Jonas
[16 Nov 2009 12:14]
Marco Tusa
Jonas, the table is used to temporary store modified values, which are deleted after the update transaction. The value of the attribute RID_PE is unique in respect of the IP_ADDRESS. More the application has only one client accessing the value of RID_PE (which is also unique) in that table a time. So they state that they cannot have more then one client accessing the same information (record) at the same time on this table.
[16 Nov 2009 14:13]
Jørgen Austvik
Marco, do you have a support issue ticket number?
[20 Nov 2009 16:25]
Marco Tusa
No
[5 Jan 2010 0: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".