Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-873

new routes calculated wrongly after connector deletion

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 1.0.0
    • 1.0.0
    • Routing Engine
    • None

    Description

      I have a 3-mesh network with nodes A, B, C.
      B-->A cost is 10
      C-->A cost is 10
      B-->C cost is 100.

      Initial route from B to C is calculated correctly as B,A,C : cost == 20.

      But after I used qdmanage to delete the connector from B to A, I get no further messages delivered from B to C.
      Using qdstat to look at routing table, it looks wrong:

      Both B and C think they can only get to each other by going through A. But there is now no route that way, because B->A has been deleted. They should be using the direct connection B->C. Yet they both calculate the cost correctly as 100.

      ===========================================================
      A
      ===========================================================
      Routers in the Network
      router-id next-hop link ver cost neighbors valid-origins
      A (self) - 1 ['C'] []
      B C - 1 110 ['A', 'C'] []
      C - 1 1 10 ['A', 'B'] ['B']
      ===========================================================
      B
      ===========================================================
      Routers in the Network
      router-id next-hop link ver cost neighbors valid-origins
      B (self) - 1 ['C'] []
      C A - 1 100 [] []
      ===========================================================
      C
      ===========================================================
      Routers in the Network
      router-id next-hop link ver cost neighbors valid-origins
      A - 0 1 10 ['C'] []
      B A - 1 100 ['A', 'C'] ['A']
      C (self) - 1 ['A', 'B'] []

      Attachments

        Activity

          People

            tross Ted Ross
            mgoulish Michael Goulish
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: