First, some versions of memcached and the memcache extension need an extra parameter on delete() to prevent a noticed like this from appearing:
CLIENT_ERROR bad command line format. Usage: delete [noreply]

Adding the "optional" zero timeout parameter makes it work without error. More info at:
http://stackoverflow.com/questions/4745345/how-do-i-stop-phpmemcachedele...

Second, in similar situations, requesting the "malloc" stats will not only return an empty result, but throw a notice as well.

CommentFileSizeAuthor
#1 remove warnings-and-notices-1101374-2.patch2.56 KBfgm

Comments

fgm’s picture

Suggested patch fixes both issues, and make the stats return easier to debug by refactoring returns.

drewish’s picture

It'd be best if we could avoid the warning rather than suppressing them.

drewish’s picture

This and #1103796: memcache delete fix have some overlap. I'm a fan of #1103796 because it's a simpler patch.

fgm’s picture

Priority: Normal » Minor
Status: Needs review » Needs work

Need to reroll to account for #1103796 now being committed. Reducing priority accordingly, since this was the most important part.

mikeytown2’s picture

Another issue for catching the warning if the memcache connection fails and reporting to watchdog.
#1011000: Catch & report errors thrown by $memcache->connect.

markpavlitski’s picture

Component: Documentation » Code
Status: Needs work » Fixed

Marking as fixed based on #1103796: memcache delete fix, #1103796: memcache delete fix and #1011000: Catch & report errors thrown by $memcache->connect. being committed and no activity in this issue for almost 2 years.

@fgm feel free to re-open if you're still experiencing the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.