delta/openstack/taskflow.git/taskflow/jobs, branch 4.6.2

Add sentinel redis support

2020-08-05T13:03:25+00:00

Redis client has an ability to connect to Redis server
using Sentinel[1] (especially important for Redis clusters),
but this ability was missing here.

Allow to pass 'sentinel' variable to Redis conf, extend
_make_client to use sentinel for that case.

[1] - https://github.com/andymccurdy/redis-py#sentinel-support

Change-Id: Ia8cc98e701435fd0231da3724f5d7108fc4f96f4

Update various links in docs

2018-07-17T18:56:19+00:00

Avoid redirects, s/http/https/.

Change-Id: Id03bd49f250b48109967a0e04b92b75925f08932

Avoid log warning when closing is underway (on purpose)

2017-08-01T11:28:26+00:00

Related-Bug: #1557107

Change-Id: I8b2f327dadbf038cd050f05fbc46a428282a3d82

do not allow redis job reclaim by same owner

2017-05-13T14:55:50+00:00

Running a nonblocking conductor or two conductors on the same host will re-execute the same job multiple times with the current implementation of 'claim' for the redis jobboard backend. This is different from the ZooKeeper jobboard backend, there the same owner of a job is not allowed to reclaim the job again (https://github.com/openstack/taskflow/blob/master/taskflow/jobs/backends/impl_zookeeper.py#L554). If the same owner is allowed to reclaim the job again there can be no concurrent execution on the same owner because all jobs will be re-claimed and re-executed by the same owner every pass as long as it's on the jobboard.

To reproduce this behavior:

- Use the redis jobboard backend
- Create a flow with a task that sleeps 10 seconds in the execute method
- Post that flow as a job
- Run a nonblocking conductor

It will claim and execute the same job multiple times in a loop until the first worker is finished and consumes the job. After this change it will not re-execute the same job multiple times.

Change-Id: I4f6c364211500e510fc496f23b03ce056771417d

python3.0 has deprecated LOG.warn

2017-03-07T09:29:26+00:00

python3.0 has deprecated LOG.warn
https://docs.python.org/3/library/logging.html#logging.warning
Closes-Bug: #1650843

Change-Id: Ib8473cbdb84547f385e619fe08ed723b1ee7bcdb

Some classes not define ne() built-in function

2016-08-31T10:57:50+00:00

Some classes defines __eq__() built-in function, but does
not define __ne__() built-in function, so self.assertEqual works
but self.assertNotEqual does not work at all in this test case in
python2. This patch fixes it.

Change-Id: I3e4f213081268bad44583a63a84795d39094117f
Closes-Bug: #1586268

Merge "Ensure the fetching jobs does not fetch anything when in bad state"

2016-07-25T16:37:39+00:00

Fix some misspellings in the function name and descriptions

2016-06-30T15:44:49+00:00

Change-Id: I7e3451feb94b1f25b00c5e7b197bb6b527548306

Ensure the fetching jobs does not fetch anything when in bad state

2016-06-01T00:58:34+00:00

When the underlying connection is in LOST or SUSPENDED mode do not
allow jobs to be iterated over (and clear the local cache when the
connection has been LOST).

Related-Bug: #1557107

Change-Id: Ic0a2ab2519ff8a7386d80d9092a0e24579883681

Merge "Add rundimentary and/or non-optimized job priorities"

2016-04-28T20:58:49+00:00