shoal
  1. shoal
  2. SHOAL-68

HealthMonitor's getMemberState should not make a network roundtrip peer's own health state

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: 1.1
    • Component/s: GMS
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Windows

    • Issuezilla Id:
      68
    • Status Whiteboard:
      Hide

      shoal-shark-na

      Show
      shoal-shark-na

      Description

      When a client component in the same VM calls
      JoinNotificationSignal.getMemberState(), the eventual call results in HM making
      a network call. This is okay for other peers but when the member involved is the
      VM itself, the call should check for that and consult the local health state
      cache and return that state.

      This is critical for Sailfin's CLB

        Activity

        Hide
        sheetalv added a comment -

        will fix for Sailfin 1.5.

        Show
        sheetalv added a comment - will fix for Sailfin 1.5.
        Hide
        sheetalv added a comment -

        needs to be a P2 since it needs to be fixed for Sailfin 1.5

        Show
        sheetalv added a comment - needs to be a P2 since it needs to be fixed for Sailfin 1.5
        Hide
        sheetalv added a comment -

        This issue has been fixed. A check to see if the member is asking for its own state has already been
        checked in.

        Show
        sheetalv added a comment - This issue has been fixed. A check to see if the member is asking for its own state has already been checked in.

          People

          • Assignee:
            sheetalv
            Reporter:
            shreedhar_ganapathy
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: