Uploaded image for project: 'REEF (Retired)'
  1. REEF (Retired)
  2. REEF-893

Different communication groups should use different threads to handle group comm messages

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.14
    • REEF-IO
    • None

    Description

      In GroupCommDriverImpl, the field groupCommMessageStage is a SingleThreadStage and we handle all group comm messages using this stage. This constraint is too strong; we should use different threads to handle group comm messages sent to different CommunicationGroups.

      If the group comm message handling thread waits (for synchronization) and is never awaken while handling a message of one CommGroup, it will block messages intended for other CommGroups. This harms the independence between different CommGroups.

      Attachments

        Issue Links

          Activity

            People

              Gyeongin Gyeongin Yu
              Gyeongin Gyeongin Yu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: