Dirk JulichandClaude Opus 4.6
918ba2ef36
* AAP-95887 Use SKIP LOCKED to prevent lock convoy on parent JT update When allow_simultaneous is enabled and many jobs complete concurrently, _update_parent_instance() serializes all sessions on the same JT row lock. In an example customer incident, single-row UPDATEs averaged 11-25 minutes with 635+ sessions queued. Use select_for_update(skip_locked=True) for the on_commit callback path so concurrent updaters that cannot acquire the row lock return immediately instead of queuing. This is safe because all fields on the JT (current_job, status, last_job, last_job_failed) are "latest wins" — at least one session always acquires the lock and writes the current state. Non-allow_simultaneous jobs are unchanged (synchronous, no skip). * Skip lock contention test on SQLite select_for_update(skip_locked=True) is silently a no-op on SQLite. Mark the lock contention test to skip when running against SQLite (the default test database). The test runs when tests are executed against PostgreSQL. * Use mock for lock contention test instead of threading The test suite uses SQLite where select_for_update is a no-op. Follow codebase convention (e.g. sqlite_copy fixture) of mocking PostgreSQL-specific behavior: mock select_for_update to return an empty queryset, simulating a locked row. Removes the separate test class and threading/psycopg dependencies. --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Caution
The last release of this repository was released on Jul 2, 2024. Releases of this project are now paused during a large scale refactoring. For more information, follow the Forum and - more specifically - see the various communications on the matter:
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
To install AWX, please view the Install guide.
To learn more about using AWX, view the AWX docs site.
The AWX Project Frequently Asked Questions can be found here.
The AWX logos and branding assets are covered by our trademark guidelines.
Contributing
- Refer to the Contributing guide to get started developing, testing, and building AWX.
- All code submissions are made through pull requests against the
develbranch. - All contributors must use
git commit --signofffor any commit to be merged and agree that usage of--signoffconstitutes agreement with the terms of DCO 1.1 - Take care to make sure no merge commits are in the submission, and use
git rebasevs.git mergefor this reason. - If submitting a large code change, it's a good idea to join discuss via the Ansible Forum. This helps everyone know what's going on, and it also helps save time and effort if the community decides some changes are needed.
Reporting Issues
If you're experiencing a problem that you feel is a bug in AWX or have ideas for improving AWX, we encourage you to open an issue and share your feedback. But before opening a new issue, we ask that you please take a look at our Issues guide.
Code of Conduct
We require all of our community members and contributors to adhere to the Ansible code of conduct. If you have questions or need assistance, please reach out to our community team at codeofconduct@ansible.com
Get Involved
We welcome your feedback and ideas via the Ansible Forum.
For a full list of all the ways to talk with the Ansible Community, see the AWX Communication guide.