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

QE verification: [RFE] OVSDB Relay: Support database 'index' for clients

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      ( ) The bug has been reproduced and verified by QE members
      ( ) Test coverage has been added to downstream CI
      ( ) For new feature, failed test plans have bugs added as children to the epic
      ( ) The bug is cloned to any relevant release that we support and/or is needed

      Show
      ( ) The bug has been reproduced and verified by QE members ( ) Test coverage has been added to downstream CI ( ) For new feature, failed test plans have bugs added as children to the epic ( ) The bug is cloned to any relevant release that we support and/or is needed
    • rhel-9
    • None
    • rhel-net-ovs-dpdk

      This ticket is tracking the QE verification effort for the solution to the problem described below.
      Clustered database server reports an 'index' value, which is the
      index of the last database update on this server. This value is
      used by clients to detect and disconnect from servers with stale
      data (i.e. if they were previously connected to a server with higher
      index). OVSDB Relay may proxy this information from the relay source
      to the relay's _Server database, so the clients may detect relays with
      stale data.

      This mechanism has drawbacks though. If the cluster is re-started
      from scratch, clients might loop over all servers and think that
      all of them has stale data. This is a generic problem that should
      be addressed separately (there is another BZ 1972270 for that).

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

                Created:
                Updated: