summaryrefslogtreecommitdiffstats
path: root/jobs/workers.go
Commit message (Collapse)AuthorAgeFilesLines
* PLT-7705: API to get data retention policy. (#7539)George Goldberg2017-10-021-2/+2
| | | | | | * PLT-7705: API to get data retention policy. * Fix review comments.
* remove jobs.Srv and other jobs-related globals (#7535)Chris2017-09-291-7/+6
|
* PLT-7542 Converting LDAP sync to the job server (#7452)Corey Hulen2017-09-251-4/+25
| | | | | | | | | | | | | | | | | | | | * PLT-7542 Converting LDAP sync to the job server * Fixing minor issues * Fixing build failure * Translate error message * Translate error message * Translate error message * Translate error message * Fixing merge * Fixing bad merge
* PLT-6558: Basic data retention job scheduler/worker implementation. (#7449)George Goldberg2017-09-151-4/+4
| | | | | | * PLT-7639: Batch delete methods for data retention. * PLT-6558: Basic data retention job worker/scheduler implementation.
* Renaming repoChristopher Speller2017-09-061-3/+3
|
* PLT-7302: Aggregate Elasticsearch indexes over a certain age. (#7224)George Goldberg2017-08-171-5/+24
| | | | | | | | | * PLT-7302: Aggregate Elasticsearch indexes over a certain age. This is done by a scheduled daily job, in order to keep the shard count to a sensible level in Elasticsearch. * Use map[string]string instead of StringMap
* PLT-7040: Fix capitalisation of Elasticsearch in Config. (#7020)George Goldberg2017-07-271-4/+4
|
* PLT-6475: Elasticsearch Indexing Worker. (#6879)George Goldberg2017-07-111-7/+24
|
* PLT-6916: Redesign the jobs package and Jobserver. (#6733)George Goldberg2017-07-071-0/+79
This commit redesigns the jobserver to be based around an architecture of "workers", which carry out jobs of a particular type, and "jobs" which are a unit of work carried by a particular worker. It also introduces "schedulers" which are responsible for scheduling jobs of a particular type automatically (jobs can also be scheduled manually when apropriate). Workers may be run many times, either in instances of the platform binary, or the standalone jobserver binary. In any mattermost cluster, only one instance of platform OR jobserver must run the schedulers. At the moment this is controlled by a config variable, but in future will be controlled through the cluster leader election process.