helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanak Biscuitwala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HELIX-128) Support multiple communication channels between controllers, participants, and spectators
Date Thu, 13 Feb 2014 07:16:20 GMT

     [ https://issues.apache.org/jira/browse/HELIX-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kanak Biscuitwala updated HELIX-128:
------------------------------------

    Reporter: Kanak Biscuitwala  (was: kishore gopalakrishna)

> Support multiple communication channels between controllers, participants, and spectators
> -----------------------------------------------------------------------------------------
>
>                 Key: HELIX-128
>                 URL: https://issues.apache.org/jira/browse/HELIX-128
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Kanak Biscuitwala
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message