Last modified: 2014-03-21 16:05:20 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 T64875, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62875 - Have beta cluster use a similar l10n cache as production
Have beta cluster use a similar l10n cache as production
Status: RESOLVED WORKSFORME
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-20 17:20 UTC by Greg Grossmeier
Modified: 2014-03-21 16:05 UTC (History)
9 users (show)

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


Attachments

Description Greg Grossmeier 2014-03-20 17:20:54 UTC
13:16 <     bd808> Beta doesn't use l10n cache like prod as far as I know. I 
                   think it just has a memcache cache
Comment 1 Antoine "hashar" Musso (WMF) 2014-03-21 09:19:13 UTC
Bryan, Niklas, Sam: I have no idea how the l10n cache works.  The Jenkins job https://integration.wikimedia.org/ci/job/beta-code-update/ does generate the l10n cache using cdb at "/a/common/php-master/cache/l10n/l10n_cache-ab.cdb"

Maybe a configuration setting is missing?
Comment 2 Sam Reed (reedy) 2014-03-21 13:03:26 UTC
Based on CommonSettings.php, the config is unconditional:

$wgLocalisationCacheConf['storeDirectory'] = "$IP/cache/l10n";
$wgLocalisationCacheConf['manualRecache'] = true;



Doesn't seem to be overridden in the labs configs. Which would suggest labs is using it...
Comment 3 Sam Reed (reedy) 2014-03-21 13:06:27 UTC
production:

reedy@tin:~$ mwscript eval.php enwiki
> var_dump( $wgLocalisationCacheConf );
array(5) {
  ["class"]=>
  string(17) "LocalisationCache"
  ["store"]=>
  string(6) "detect"
  ["storeClass"]=>
  bool(false)
  ["storeDirectory"]=>
  string(34) "/a/common/php-1.23wmf18/cache/l10n"
  ["manualRecache"]=>
  bool(true)
}


beta:

reedy@deployment-bastion:~$ mwscript eval.php enwiki
> var_dump( $wgLocalisationCacheConf );
array(5) {
  ["class"]=>
  string(17) "LocalisationCache"
  ["store"]=>
  string(6) "detect"
  ["storeClass"]=>
  bool(false)
  ["storeDirectory"]=>
  string(55) "/data/project/apache/common-local/php-master/cache/l10n"
  ["manualRecache"]=>
  bool(true)
}


Bar path (which is very much to be expected), this would look to be identical
Comment 4 Bryan Davis 2014-03-21 15:38:53 UTC
(In reply to Sam Reed (reedy) from comment #3)
> Bar path (which is very much to be expected), this would look to be identical

Sounds like I was talking out of the wrong side of my head then. That's what I get for not checking before I yammered.
Comment 5 Antoine "hashar" Musso (WMF) 2014-03-21 15:54:39 UTC
For what it is worth, I noticed a few hours ago that the l10n cache directory on beta belonged to the wrong user (we migrated l10nupdate to be in LDAP instead of local to the instance).

I fixed up /data/project/apache/common-local/php-master/cache/l10n by running chown -R l10nupdate:l10nupdate


Bryan > should we just close this bug?
Comment 6 Greg Grossmeier 2014-03-21 16:05:20 UTC
/me does that for him

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


Navigation
Links