helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kishore gopalakrishna (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HELIX-128) Support multiple communication channels between controller participants and spectators
Date Mon, 10 Jun 2013 04:36:21 GMT
kishore gopalakrishna created HELIX-128:
-------------------------------------------

             Summary: Support multiple communication channels between controller participants
and spectators
                 Key: HELIX-128
                 URL: https://issues.apache.org/jira/browse/HELIX-128
             Project: Apache Helix
          Issue Type: Bug
            Reporter: kishore gopalakrishna


Currently all communications between controller,participant and spectator happens via zookeeper.
This is important for systems where fault tolerance cannot be compromised. But this also increases
the latency of communication quite a bit. 

For some applications, it is important that communication between different components is
fast, its ok to lose the message in some cases or if controller fails after the message is
sent. we can either use tcp or any other pub/sub mechanism to make this as faster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message