Page MenuHomeSoftware Heritage

Reduce current log configuration of various services
Closed, MigratedEdits Locked

Description

So that log size becomes more manageable in the medium term

Event Timeline

For me, this sums up to change the line ExecStart in /etc/systemd/system/swh-worker.service in our multiple workers.

ExecStart=/usr/bin/python3 -m celery worker --app=swh.scheduler.celery_backend.config.app --pool=prefork --concurrency=10--maxtasksperchild=5 -Ofair --loglevel=debug

and increase the log level to info.

so:

ExecStart=/usr/bin/python3 -m celery worker --app=swh.scheduler.celery_backend.config.app --pool=prefork --concurrency=10--maxtasksperchild=5 -Ofair --loglevel=info

But i don't find any swh-worker.service.erb template in our puppet code...
Looks like this part is not yet puppetized or i just don't know how to search for it.

Looks like this part is not yet puppetized

Yep, it's deployed from louvre.

Something like:

sudo clush --copy -w @workers /etc/systemd/system/swh-worker.service

It's partially done (worker01, worker02, worker03, worker08).
Some workers are stopped so those one need to be booted first,
I think they were stopped for the ram issue we had on louvre the 4th of July (to restart prado).

I let this open for now until we deploy on the other nodes as well.

ardumont changed the task status from Open to Work in Progress.Jul 14 2016, 12:33 PM