Closed (fixed)
Project:
Varnish
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Feb 2018 at 22:46 UTC
Updated:
3 Aug 2018 at 10:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
phuang07 commentedJust found out I have the variable name described incorrectly in the issue summary above..
I mean to say this:
Recent updated to 7x.1.8, node update seems not longer trigger varnish to purge if it has 'varnish_flush_cron' is disabled.
This seems to related to:
https://www.drupal.org/project/varnish/issues/2920579.
Looking at: https://cgit.drupalcode.org/varnish/tree/varnish.cache.inc?id=c0eb2ec902..., !variable_get('varnish_flush_cron', 0)
if varnish_flush_cron is disabled, nothing will send to varnish even 'varnish_cache_clear' set to 1.
Comment #3
phuang07 commentedComment #4
misc commentedComment #5
punch commented+1
Comment #6
drilauri commentedSame issue as well. When I update a node, it's still serving the cached version. I'm manually restarting varnish on every time-sensitive update to the site.
Comment #7
jozzhart commented+1
Comment #8
misc commentedUpdated patch.
Comment #10
misc commentedCommitted to dev, and will be out in the next release today.