If a site is busy at the time the garbage collector kicks in, it is possible for the system to have a meltdown if nothing finishes the garbage collect fast enough.

Comments

bdragon’s picture

StatusFileSize
new1 KB

Same for HEAD.

gerhard killesreiter’s picture

Status: Needs review » Reviewed & tested by the community

1 line change, good to go, already live on drupal.org.

gerhard killesreiter’s picture

Version: 5.x-dev » 6.x-dev

This should go into D6 first.

gábor hojtsy’s picture

Version: 6.x-dev » 5.x-dev

Great, committed to 6.x. RTBC for 5.x.

hass’s picture

Are you really sure this makes sense?

If a cache is not flushed successfully - the variable shouldn't tell it is flushed successfully. This change sounds very illogical and keeps stale data.

gábor hojtsy’s picture

Hass, the variable_set() never checked the success of the query, so there is no such change as you explained.

drumm’s picture

Status: Reviewed & tested by the community » Fixed

Committed to 5.x.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

etamar’s picture

Priority: Critical » Normal
Status: Closed (fixed) » Active

Hi guys,

I think the "well rounded" / "good" behavior would be adding a global variable to determine "being flushed", and not use the "flushed" variable as it is confusing and erratic as hass correctly mentioned.

This is from a good practices point of view,

To your review,
Etamar

mot’s picture

etamar, doesn't work the fix for you?

mot’s picture

Status: Active » Closed (fixed)

No answer, so a positive is assumed. Closed again.