collective.taskqueue 0.7.0

Advanced configuration

Supported <taskqueue />-settings are:

queue (default=default)

Unique task queue name.

type (default=local)

Task queue type (‘local’ or ‘redis’) or full class path to a custom type.

unix_socket_path

Redis server unix socket path (use instead of host and port).

Other supported Redis-queue options are: host, port, db and password.

Supported <taskqueue-server />-settings are:

name (default=default)

Consumer name, preferably instance name. Consumer is name used by Redis-queues for reserving messages from queue to achieve quaranteed delivery.

queue (default=default)

Queue name for this consumer (consuming server). There must be a <taskqueue/> with matching queue-value registered.

concurrent_limit (default=1)

Maximum concurrent task limit for this consumer. It’s recommend to set this smaller than zserver-thread-count. Leaving this to the default (1) should give the best results in terms of minimal ConflictErrors.

retry_max_count (default=10)

Maximum ZPublisher retry count for requests dispatched by this consumer.

Advanced usage

taskqueue.add accepts the following arguments (with default value):

url (required, no default)

Target path representing the task to be called.

method (optional, default=GET)

HTTP-method for the call. Must be either GET or POST.

params (optional, default=None)

A dictionary of optional task arguments, which are appended as query string after the given url. (When params are provided, url must not already include any querystring).

headers (optional, default=None)

A dictionary of optional HTTP-headers to be appended to (or used to replace) the headers copied from the active request.

payload (optional, default=current)

An optional payload for POST-request. Payload from the active request will be copied by default. Copying the active payload can be prevented with payload=None.

queue (optional, default=alphabetically-first-registered-queue)

An optional queue name, when more than one queue is registered.

How Redis queueing works

1. taskqueue.add prepares a message, which will be pushed (lpush) into key collective.taskqueue.%(queue)s (where %(queue)s` is the name of the queue) at the end of the transaction. If Redis connection is down during the transaction vote, the whole transaction is aborted.

2. <taskqueue-server /> reads each message (rpoplpush) from queue so that they will remain in key collective.taskqueue.%(queue)s.%(name)s (where %(name)s is the name of the <taskqueue-server/>) until each asynchronous processing request has returned a HTTP response.

3. On startup, and when all known messages have been processed, <taskqueue-server/> purges collective.taskqueue.%(queue)s.%(name)s into collective.taskqueue.%(queue)s (with rpoplpush) and those tasks are processed again. (E.g. if Plone was forced to restart in middle of task handling request.)

Redis integration uses PubSub to notify itself about new messages in queue (and get as instant handling as possible in terms of Plone’s asyncore-loop).

0.7.0 (2014-12-29)

• Replace NoRollbackSavepoint with rollback ‘supporting’ DummySavepoint [datakurre]

0.6.2 (2014-12-19)

• Add minimal savepoint-support with NoRollbackSavepoint [datakurre]

0.6.1 (2014-08-05)

• Fix issue where language bindings are not set for task queue requests, because the request is not HTTPRequest, but only inherits it [datakurre]

0.6.0 (2014-05-19)

• Add taskqueue.add to return task id, which later matches request.getHeader(‘X-Task-Id’) [datakurre]

0.5.1 (2014-05-14)

• Fix issue where concurrent task counter mutex was not released due to uncaught exception [datakurre]

• Fix issue where a socket in asyncore.map was closed during asyncore.poll [datakurre]

0.5.0 (2014-04-03)

• Fix threading and execution order related issue where currently active Redis tasks were requeued (and processed more than once) [datakurre]

• Add ‘X-Task-Id’-header to help keeping track of tasks n consuming views [datakurre]

0.4.4 (2013-11-25)

• Fix regression where redis+msgpack where accidentally always required [#7] [datakurre]

• Update docs [Dylan Jay]

• Fix default for ‘unix_socket_path’ [fixes #8] [Dylan Jay]

0.4.3 (2013-11-15)

• Update README [datakurre]

0.4.2 (2013-11-15)

• Updated README [datakurre]

0.4.1 (2013-11-14)

• Updated README [datakurre]

0.4.0 (2013-11-14)

• Refactor configuration by replacing explicit utilities and <product-configuration/> with <taskqueue/>-component [datakurre]

0.3.1 (2013-11-13)

• Enhance acceptance testing support with the first acceptance tests [datakurre]

0.3.0 (2013-11-10)

• Fix TaskQueueServer to re-connect to Redis after Redis restart [datakurre]

• Fix to ping Redis on Zope start only in development mode [datakurre]

• Add optional Task Queue PAS plugin to independently authenticate queued tasks as their creator [datakurre]

0.2.2 (2013-11-09)

• Fix to flush Redis pub-notifications only when queue has been emptied to ensure that all messages will be processed [datakurre]

0.2.1 (2013-11-09)

• Fix taskqueue socket to be not readable by default [datakurre]

0.2.0 (2013-11-09)

• Enhance Redis-integration to connect redis notification pubsub-socket directly to asyncore on instant message handling [datakurre]

• Fix to require redis >= 2.4.10 [fixes #2] [datakurre]

• Fix to not start with clear error when clearly intending to use RedisTaskQueues without redis-dependencies. Also crash when cannot connect to Redis. [fixes #1] [datakurre]

0.1.0 (2013-11-03)

• First release for experimental use.