Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-2722

Test Plan: [RFE] Active/Passive replication should be done with update2 and not update

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • ovs-dpdk
    • False
    • False
    • Hide

      ( ) The new test plan is aligned with the epic's acceptance criteria

      Given an OVS/OVN deployment using active/passive replication with many database objects,

      When replication occurs due to changes in the database,

      Then ovsdb-server uses update2 instead of update so that the network traffic and CPU load associated with replication is reduced.

      ( ) The test plan/test case pass successfully on all non blocking functions of the feature

      Show
      ( ) The new test plan is aligned with the epic's acceptance criteria Given an OVS/OVN deployment using active/passive replication with many database objects, When replication occurs due to changes in the database, Then ovsdb-server uses update2 instead of update so that the network traffic and CPU load associated with replication is reduced. ( ) The test plan/test case pass successfully on all non blocking functions of the feature
    • rhel-9
    • None

      This task is tracking the test case writing activities to cover the feature request described below.

      Description of problem:

      When using active/passive replication, ovsdb/replication.c uses "update" notifications, which means that the full change is sent across the wire instead of just the diffs. This is especially noticeable in the case of the "drop" port group (RFE for feature to allow removal here https://bugzilla.redhat.com/show_bug.cgi?id=1947807) and with Logical_Switches that have a lot of ports. In the former case, I've see 17000 entries in that port group that are sent during every single port create.

      Given the load we see on ovsdb-server, it seems like not having to iterate all of those objects to create/process those notifications would be helpful.

      Version-Release number of selected component (if applicable):
      FDP 21.C

      How reproducible:
      100%

      Steps to Reproduce:
      1. Set up active passive replication
      2. Watch the update notifications between servers
      3.

      Actual results:
      "update" notifications are sent

      Expected results:
      "update2" notifications are sent

      Additional info:

              ovsdpdk-triage ovsdpdk triage
              nstbot NST Bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: