Last modified: 2013-11-05 20:02:20 UTC
I am not sure this is actually an issue, but nextJobDB.php has debug logs showing it creates two redis connection pool, what ever it can be: 0.5303 10.2M Start command line script nextJobDB.php 0.5557 11.0M CACHES: MemcachedPhpBagOStuff[main] MemcachedPhpBagOStuff[message] MemcachedPhpBagOStuff[parser] 0.6357 14.5M Class LanguageAa not found; skipped loading 0.6416 15.0M LocalisationCache: using store LCStore_CDB 0.6861 17.8M Fully initialised 0.6941 17.8M Creating a new RedisConnectionPool instance with id 627014dc7020485d721532dde4142d5190ba3cc1. 0.7075 18.2M Creating a new RedisConnectionPool instance with id 95797b002a3bb33394c101391fbb456c43b076e3. The stream can be seen on deployment-bastion.pmtpa.wmflabs /data/project/logs/cli.log
ccing Aaron Schulz.
I can't reproduce this unless the JobQueueAggregator and the JobQueueRedis server are different IPs (in which case this is normal).
Make sense, I was confused by the lack of meaningful name.