Skip to content
Erlang consumer framework for beanstalkd work queue
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Erlang consumer framework for beanstalkd work queue

Idea behind the project

  • An easy and configurable app that it's starting a pool of consumers which executes jobs from a beanstalkd server.
  • You can tune the concurrency of jobs that are executed in parallel
  • In case the connection between consumer and server goes down minimise the damage (jobs being cached by another consumer and executed again for example).
  • In case the consumer is stopped will wait for all jobs in progress to complete.

What's the lifetime of a job

  • Once a job is reserved before being sent to be processed is buried first.
  • In case the processing was completed fine (no exception triggered) then the job is deleted
  • In case job processing is failing is left in the buried state.
  • In case for some reason the job was not scheduled (processing limits hit or any other reason) the job is scheduled again for being processed (kick-job).
  • All delete/kick operations are taking place on another processes where are queued so in case connection to the server goes down the operations are not lost.

Quick start

Define a module with a function with arity 3 that will process the jobs and one with arity one used for init process for example:

-export([init/1, process/2]).
init(Pid) ->
    [{<<"arg1">>, <<"val1">>}, {<<"arg2">>, <<"val2">>}].
process(Id, Payload, State) ->
    io:format(<<"id:~p job:~p state:~p ~n">>, [Id, Payload, State]).

Use a config similar with:

    {beanstalkd_consumer, [

        {servers, [
            {default_server, [
                {start_at_startup, true},
                {connection_info, [{host, {127,0,0,1}}, {port, 11300}, {timeout, 5000}]},
                {queues_number, 1},
                {consumers, [
                    {consumer_silviu, [
                        {instances, 1},
                        {callbacks, [
                            {<<"tube_name">>, test, init, process}
                        {concurrent_jobs, 100000}


  • start_at_startup - specify if the consuming of messages should start imeediatly when the application is started. In case you have the beanstalkd_consumer as dependency and you need to load more other stuffs into your current app before starting consuming events, you can put this property on false and use beanstalkd_consumer:start_consumers/0 to start the consumers.
  • connection_info - connection details
  • queues_number - number of processes that will handle the deletes and kick operations. Those are queued in case the connection to the server is not up and are sent again once connection is established.

For each consumer:

  • instances - number of consumers
  • callbacks - [{Tube, Module, InitFun/1, ProcessFun/3}]. Each item in list is formed from the tube, module, init function, the function that will handle the jobs for that tube.
  • concurrent_jobs - how many concurrent jobs can run in parallel.
You can’t perform that action at this time.