You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Gyeongin Yu (JIRA)" <ji...@apache.org> on 2015/10/30 11:36:27 UTC
[jira] [Created] (REEF-893) Different communication groups should
use different threads to handle group comm messages
Gyeongin Yu created REEF-893:
--------------------------------
Summary: Different communication groups should use different threads to handle group comm messages
Key: REEF-893
URL: https://issues.apache.org/jira/browse/REEF-893
Project: REEF
Issue Type: Bug
Components: REEF-IO
Reporter: Gyeongin Yu
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}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)