You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "kishore gopalakrishna (JIRA)" <ji...@apache.org> on 2013/06/10 06:36:21 UTC
[jira] [Updated] (HELIX-128) Support multiple communication
channels between controller participants and spectators
[ https://issues.apache.org/jira/browse/HELIX-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kishore gopalakrishna updated HELIX-128:
----------------------------------------
Issue Type: Improvement (was: Bug)
> 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: Improvement
> 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