Bug #24333 | concurrent calls to table object on columns with utf8 charse cause crash | ||
---|---|---|---|
Submitted: | 15 Nov 2006 11:57 | Modified: | 22 Dec 2006 16:03 |
Reporter: | Jim Dowling | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: NDB API | Severity: | S1 (Critical) |
Version: | 5.1.12 | OS: | Linux (Linux) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | cluster, table object, utf8 charset |
[15 Nov 2006 11:57]
Jim Dowling
[22 Nov 2006 15:43]
Jonas Oreland
Hi, Looking at mysys charset code, it should serialize access to init_available_charsets If you have used ndb_init (which calls my_init) and also call my_thread_init as first method as first method in a thread. Do you use both of these calls? Can you also expand a bit on what "* However, we still see it in situations where the cluster_connection has been up, fails, and recovers." means ? /Jonas
[22 Nov 2006 16:03]
Jonas Oreland
ok, update to need feedback
[28 Nov 2006 14:15]
Jonas Oreland
jim, can you updated us on what change you did (as issue now is closed) so we know for future (and mabye even document it :-)
[23 Dec 2006 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".