Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 645
    • Issues 645
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Merge requests
  • !732

Job Queue

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged minibikini requested to merge minibikini/pleroma:feature/jobs into develop Jan 28, 2019
  • Overview 5
  • Commits 13
  • Pipelines 12
  • Changes 16

What it does

  • Moves job queue logic from Pleroma.Web.Federator to Pleroma.Jobs module.
  • Allows adding new queues for different kinds of tasks (not only federation). The MR includes :federator_incoming and :federator_outgoing queues.
  • Every queue has own max_jobs setting

API

@spec enqueue(atom(), atom(), [any()], integer()) :: :ok
Pleroma.Jobs.enqueue(queue_name, mod, args, priority \\ 1)

Arguments

  • queue_name - a queue name (must be specified in the config).
  • mod - a worker module (must have perform function).
  • args - a list of arguments for the perform function of the worker module.
  • priority - a job priority (0 by default).

Examples

Enqueue Module.perform/0 with priority=1:

Pleroma.Jobs.enqueue(:example_queue, Module, [])

Enqueue Module.perform(:job_name) with priority=5:

Pleroma.Jobs.enqueue(:example_queue, Module, [:job_name], 5)

Enqueue Module.perform(:another_job, data) with priority=1:

data = "foobar"
Pleroma.Jobs.enqueue(:example_queue, Module, [:another_job, data])

Enqueue Module.perform(:foobar_job, :foo, :bar, 42) with priority=1:

Pleroma.Jobs.enqueue(:example_queue, Module, [:foobar_job, :foo, :bar, 42])

Questions

  • Should I Pleroma.Web.Federator.RetryQueue -> Pleroma.Jobs.RetryQueue? ATM RetryQueue is used by Federator only and has some federation logic.
Edited Jan 31, 2019 by minibikini
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/jobs