Bug #70403 | No useful error message when memcached fails to start due to lack of memory | ||
---|---|---|---|
Submitted: | 23 Sep 2013 21:40 | Modified: | 17 Oct 2013 11:11 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Memcached | Severity: | S3 (Non-critical) |
Version: | MySQL Cluster 7.2.12, MySQL Cluster 7.2.13 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[23 Sep 2013 21:40]
Hartmut Holzgraefe
[25 Sep 2013 14:05]
MySQL Verification Team
Hello Hartmut, Thank you for the bug report. Verified as described. Thanks, Umesh
[10 Oct 2013 17:52]
John Duncan
Yes, the "Failed to initialize instance" message comes from engine_loader.c. I think the current state is this: InnoDB memcached and NDB memcached trees have diverged (mostly because InnoDB memcached runs as a plugin daemon inside mysqld rather than as an independent process). Couchbase is separately making changes to their own product based on Memcached 1.6. Mainline memcached people still feel that 1.4 offers better performance. And nobody has recently maintained the "common" 1.6 tree on github. I will try to improve a few of these startup-time error messages on the NDB side. (And hope to make some headway on the other issues, outside of this bug).
[17 Oct 2013 11:11]
Jon Stephens
Documented fix int he NDB 7.2.15 and 7.3.3 changelogs, as follows: When attempting to start memcached with a cache_size larger than that of the available memory and with preallocate=true failed, the error message provided only a numeric code, and did not indicate what the actual source of the error was. Closed.