This repository has been archived by the owner on Mar 7, 2022. It is now read-only.

Create a DB table for job logging #16

Open

isra00 opened this issue Feb 22, 2013 · 0 comments

Owner

isra00 commented Feb 22, 2013

table log_job (engine=ARCHIVE)

id_job
started
time_download
time_generate
generator_output
generator_status

Advantages:

Optimize DB by making the job table lighter (move the current output, time_download and time_generated fields) and having a log table with the ARCHIVE engine
Separate the job queueing from the logging aspect, which allows a smoother transition to an external queue system (RabbitMQ, etc) and optimizes future log analysis.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.