ReleaseEngineering/Applications/Slavealloc: Difference between revisions

Jump to navigation Jump to search
Line 55: Line 55:
     --no-index --find-links=http://staging-puppet.build.mozilla.org/staging/python-packages/
     --no-index --find-links=http://staging-puppet.build.mozilla.org/staging/python-packages/


Once this was set up, the 'slavealloc dbinit' command was used to initialize the database.
Once this was set up, the 'slavealloc dbinit' command was used to initialize the database.  There is a [http://hg.mozilla.org/build/tools/file/tip/lib/python/slavealloc/contrib/make-slavealloc-virtualenv.sh make-slavealloc-virtualenv.sh] script available in /tools to make this process automatic.


The production and staging tac files are in <tt>/build/slavealloc</tt>.  Staging runs on port 1079, and production runs on 1080.  The files are similar to those [http://hg.mozilla.org/build/tools/file/828895e6a5d3/lib/python/slavealloc/contrib in hg], and include the commented <tt>pool_recycle</tt> line, with timeout 400, to automatically expire connections before the MySQL server itself does.  If this still occurs, we can look to the example of the [https://github.com/djmitche/buildbot/blob/master/master/buildbot/db/enginestrategy.py#L31 Buildbot source] for a better solution.
The production and staging tac files are in <tt>/build/slavealloc</tt>.  Staging runs on port 1079, and production runs on 1080.  The files are similar to those [http://hg.mozilla.org/build/tools/file/828895e6a5d3/lib/python/slavealloc/contrib in hg], and include the commented <tt>pool_recycle</tt> line, with timeout 400, to automatically expire connections before the MySQL server itself does.  If this still occurs, we can look to the example of the [https://github.com/djmitche/buildbot/blob/master/master/buildbot/db/enginestrategy.py#L31 Buildbot source] for a better solution.
canmove, Confirmed users
1,394

edits

Navigation menu