New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling memcached causes "Waiting for property cache" messages and server spinning #885

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 10 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Apr 6, 2015

What steps will reproduce the problem?
1. enable memcached servers in MPS with prefork MPM
2. (I think) turn on LoadFromFile in configuration
3. run traffic

Too many "waiting for property cache" messages in log.  Eventually, httpd 
processes start spinning and the system performance degrades.

Original issue reported on code.google.com by jmara...@google.com on 3 Feb 2014 at 4:01

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

This issue was closed by revision r3759.

Original comment by jmara...@google.com on 3 Feb 2014 at 4:03

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 3 Feb 2014 at 4:06

  • Added labels: Milestone-v31, release-note
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by hui...@google.com on 5 Mar 2014 at 8:52

  • Changed title: Enabling memcached causes "Waiting for property cache" messages and server spinning
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Wile https://code.google.com/p/modpagespeed/source/detail?r=3759 made this 
problem much much less likely to occur, it didn't solve it completely, per 
recent messages on mod-pagespeed-discuss.

A new change has been started that I hope eliminates the problem completely.

Original comment by jmara...@google.com on 27 Mar 2014 at 2:30

  • Changed state: Started
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

What's the status here?  I remember seeing a recent relevant change.  Is this 
fixed?

Original comment by jmaes...@google.com on 18 Apr 2014 at 7:17

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

This problem should be fixed completely now.  This does *not* mean there will 
be zero memcached-related errors in the logs under any condition, no matter 
what the load.

Bursts of CPU activity can cause memcached to timeout but the system should 
stay stable, and there should be no spinning of CPUs.

Original comment by jmara...@google.com on 18 Apr 2014 at 7:21

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Much appreciated for the hard work. Is the fix released in beta or stable 
channel? :)

Original comment by charlesa...@gmail.com on 21 Apr 2014 at 2:59

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

It is fixed in both.  Both beta and stable are currently pointing to 1.7.30.4, 
which has the fix in it.

Original comment by jmara...@google.com on 21 Apr 2014 at 3:11

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Oh my bad, I've read the release notes on March, but then got confused with the 
status changing, thought there is something new on the horizon. It seemed I 
have run the 1.7.30.4 stable version. Thanks!

Original comment by charlesa...@gmail.com on 21 Apr 2014 at 3:16

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

No; my fault :)

This bug was labeled "Milestone-v31" and it should be "Milestone-v30", which 
led to the confusion and the status change.

But we release-noted it in 
https://developers.google.com/speed/pagespeed/module/release_notes#release_1.7.3
0.4-beta and don't need to release-note it again.

Original comment by jmara...@google.com on 21 Apr 2014 at 3:19

  • Added labels: Milestone-v30
  • Removed labels: Milestone-v31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment