andrewbrg commented on issue #1686: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-623329495
> However, another scenario is that you are running into this bug: apache/incubator-pagespeed-mod#1145. It took me a while to find that. I haven't fully re-read it, but I think the scenario could be that *neither* of your pagespeed instances is able to fetch anything. And the way it is able to optimize assets is by saving them in the local cache while it serves them from their original URLs via In Place Resource Optimization <https://www.modpagespeed.com/doc/system#ipro>. @jmarantz I don't think this can be the case because I see the shared cache being filled up so something is being saved to it and also the URLs of the assets are being changed to PageSpeed URLs. So far what do we know for a fact: 1. Issue happens when Redis Shared cache is 99.9999% full 2. The Redis Shared Cache was configured with maxmemory -> allkeys-lru 3. Two websites each with two PageSpeed reverse proxies use the same Redis _(although different DB numbers per website)_ 4. Some images which were re-written by PageSpeed have the new PageSpeed URL give a 404 but the original non-optimised image url works 5. All Images are saved in a separate Redis DB and served via PHP 6. The entire setup is using docker 7. extend_cache_images is disabled ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
