magnum-conductor raise db_exc.DBDuplicateEntry when to start multiple processes concurrently
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
New
|
Undecided
|
Wang Bo |
Bug Description
ENV:
[root@node-1 ~]# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 32
On-line CPU(s) list: 0-31
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 2
NUMA node(s): 2
=======
conductor.log:
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
2017-07-09 00:10:13.553 61213 ERROR oslo_service.
we have enable multiple workers of magnum-conductor that result in different processes save same DB entry concurrently.
Changed in magnum: | |
assignee: | nobody → Wang Bo (chestack) |
description: | updated |
description: | updated |
summary: |
- magnum-conductor failed to start multiple processes concurrently + magnum-conductor raise db_exc.DBDuplicateEntry when to start multiple + processes concurrently |
Fix proposed to branch: master /review. openstack. org/494473
Review: https:/