Bug #64576 ndb memcache crash when using [caching] policy
Submitted: 7 Mar 2012 6:17 Modified: 10 Apr 2019 5:42
Reporter: aylwinear wei Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: NDB API Severity:S1 (Critical)
Version:NDB 7.2.4; MySQL 5.5.19 OS:Linux (RHEL4 x86_64)
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: Memcache

[7 Mar 2012 6:17] aylwinear wei
Description:
1. ndbmemcache's GET policy is set to "caching",
2. do a GET operation in memcache, if the key presents in db but the cache, memcache crashs.

tried both on bundled memcached , and memcached 1.6beta, all with MYSQL-CLUSTER 7.2.4 bundled ndb_engine.so, all the same. 
is the ndb_engine.so problem ?

============================================
<44 server listening (udp)
<44 server listening (udp)
43 - Running task: (conn_listening)
<45 new auto-negotiating client connection
45 - Running task: (conn_new_cmd)
45: going from conn_new_cmd to conn_waiting
45 - Running task: (conn_waiting)
45: going from conn_waiting to conn_read
45 - Running task: (conn_read)
45: going from conn_read to conn_parse_cmd
45 - Running task: (conn_parse_cmd)
45: Client using the ascii protocol
<45 get hostn:431
worker.0 --> attach_thread()
Pipeline 0 attached to S scheduler.
worker.0 ndb_get(): cache miss
worker.0 ndb_get():creating workitem 0.0
worker.0 schedule():SchedulerWorker / config gen. 1
worker.0 worker_set_ext_flag(): 0.0: F
worker.0 --> do_read()
worker.0 --> setKeyForReading()
worker.0 workitem_allocate_rowbuffer_1(): 389 [cls 9]
worker.0 schedule():0.0 placed on send queue.
cl0.conn0.send run_ndb_send_thread():Sent 0.0
cl0.conn0.poll run_ndb_poll_thread(): ** adding 0.0 to wait group ** 
cl0.conn0.poll run_ndb_poll_thread():Polling 0.0
cl0.conn0.poll callback_main():Success.
cl0.conn0.poll worker_finalize_read():0.0
cl0.conn0.poll --> build_hash_item()
cl0.conn0.poll build_hash_item():nbytes: 20   ncopied: 20
Segmentation fault (core dumped)

How to repeat:
see description
[10 Apr 2019 5:42] MySQL Verification Team
Hi,

Cannot reproduce this with modern 7.6.9 nor 7.5.13

kind regards
Bogdan