Last modified: 2014-04-15 18:22:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65705, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63705 - Flow: cache versioning cross-wiki and across MediaWiki versions
Flow: cache versioning cross-wiki and across MediaWiki versions
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
master
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-08 21:54 UTC by spage
Modified: 2014-04-15 18:22 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2014-04-08 21:54:36 UTC
Flow has a $wgFlowCacheVersion value. We change it if we change Flow's cache format, and we can bump it to brute-force a cache invalidation.

But I think all WMF wikis share the cache, even though some are running an earlier MediaWiki and thus a different version of the Flow code.
a) If two WMF wikis are using different $wgFlowCacheVersion , they won't see each other's Flow updates.
b) If two WMF wikis are using the same $wgFlowCacheVersion with different code, they may make incompatible cache updates.

So we have to backport incompatible cache code changes to previous releases in production.  We may be able to get away without doing this until we support cross-wiki Flow activity.

Currently a) can't happen because we force all wikis to use the same cache value by also setting $wgFlowCacheVersion in operations/mediawiki-config wmf-config/CommonSettings.php 

To start, someone who really understands Flow caching should add a comment about this to Flow.php.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links