Infrastructure/ansible
3
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

Dance around fedbadges database deadlocks.

Browse source
This commit is contained in:
Ralph Bean 2015-03-31 19:04:47 +00:00
parent 7b91c6bf43
commit cbd7287a21
1 changed files with 4 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

9
roles/badges/backend/templates/badges-awarder.py
View file

@ -2,11 +2,10 @@ config = {
# We need to tell the fedmsg-hub that it should load our consumer on start.
"fedmsg.consumers.badges.enabled": True,
# This sets up four threads to handle incoming messages. At the time of
# this commit, all of our fedmsg daemons are running in single-threaded
# mode. If we turn it on globally, we should remove this setting.
"moksha.workers_per_consumer": 4,
"moksha.threadpool_size": 12,
# fedbadges only needs 1 thread. It is fast enough as is and the multiple
# threads tend to get themselves into database deadlocks.
"moksha.workers_per_consumer": 1,
"moksha.threadpool_size": 4,
# This tells the consumer where to look for its BadgeRule definitions. It
# may be a relative or an absolute path on the file system.