yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1935888] [NEW] When multiple neutron servers are restarted, the update from neutron MariaDB to ovn North database is triggered, and the neutron server generates contention lock, loses lock and reports an error

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: zhangtongjian <1935888@xxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Jul 2021 02:07:12 -0000
Reply-to: Bug 1935888 <1935888@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

Multiple neutrron server restart, triggering the update of neutron MariaDB to ovn North database. Because acceleration is asynchronous, when a neutron server obtains OVS IDL lock (ovn_ db_ inconsistencies_ After Periodics), but other neutron server can not get the lock, and update it directly without judging whether to acquire the lock, it will cause an error:
  "the transaction failed because the IDL has" will be reported
 "been configured to require a database lock "

 "but didn't get it yet or has already lost it"

neutron ml2 config:
   netron_sync_mode = repair

python ovs version:
   2.13.0
   leader_only' is set to True (default value) the IDL will only
        monitor and transact with the leader of the cluster

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1935888

Title:
  When multiple neutron servers are restarted, the update from neutron
  MariaDB to ovn North database is triggered, and the neutron server
  generates contention lock, loses lock and reports an error

Status in neutron:
  New

Bug description:
  Multiple neutrron server restart, triggering the update of neutron MariaDB to ovn North database. Because acceleration is asynchronous, when a neutron server obtains OVS IDL lock (ovn_ db_ inconsistencies_ After Periodics), but other neutron server can not get the lock, and update it directly without judging whether to acquire the lock, it will cause an error:
    "the transaction failed because the IDL has" will be reported
   "been configured to require a database lock "

   "but didn't get it yet or has already lost it"

  neutron ml2 config:
     netron_sync_mode = repair

  python ovs version:
     2.13.0
     leader_only' is set to True (default value) the IDL will only
          monitor and transact with the leader of the cluster

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1935888/+subscriptions