You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "kishore gopalakrishna (JIRA)" <ji...@apache.org> on 2010/11/08 21:19:09 UTC
[jira] Created: (ZOOKEEPER-924) Recipe: Fault tolerant
communication layer using Zookeeper
Recipe: Fault tolerant communication layer using Zookeeper
----------------------------------------------------------
Key: ZOOKEEPER-924
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-924
Project: Zookeeper
Issue Type: Task
Components: recipes
Environment: Any
Reporter: kishore gopalakrishna
A typical use case in distributed system is " There are T tasks and P processes running but only T processes must be active always [ P > T ] and remaining P-T processes acting as stand by and be ready to take up a Task with one or more active processes fail".
Zookeeper provides an excellent service which can be used to co ordinate among P processes and using the mechanism of locking we can ensure that there is always T processes active. Without a central co-ordinating service generally there will be 2T processes[ i.e atleast one back up for each process]. With Zookeeper we can decide P based on the failure rate.
The assumption here are
1. At any time we have P > T. P can be chosen appropriately based on failure rate.
2. The tasks are stateless. That is any process P_i that takes up a task T_j does not know the state of the process P_k which previously processed T_j. This is not entirely true and there are ways to over come this draw back on a case by case basis.
This was developed for a different project S4 which is also open sourced http://s4.io/. The communication layer and task management layer is completely independent of S4 and can be used in any application.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-924) Recipe: Fault tolerant
communication layer using Zookeeper
Posted by "kishore gopalakrishna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
kishore gopalakrishna updated ZOOKEEPER-924:
--------------------------------------------
Description:
This recipe caters to the following use case
There are S(Active) + s(standby) sender nodes and R(Active) + r(standby) receiver nodes. The objective is following
* If one of the S Active server goes down a standby node should take up the task.
* If one of the R Active server goes down a standby node should take up the task.
* When there is a change in receiver the Sender must get updated and send the message to correct destination
This also uses recipe described in https://issues.apache.org/jira/browse/ZOOKEEPER-923
This was developed for a different project S4 which is also open sourced http://s4.io/. The communication layer and task management layer is completely independent of S4 and can be used in any application.
was:
A typical use case in distributed system is " There are T tasks and P processes running but only T processes must be active always [ P > T ] and remaining P-T processes acting as stand by and be ready to take up a Task with one or more active processes fail".
Zookeeper provides an excellent service which can be used to co ordinate among P processes and using the mechanism of locking we can ensure that there is always T processes active. Without a central co-ordinating service generally there will be 2T processes[ i.e atleast one back up for each process]. With Zookeeper we can decide P based on the failure rate.
The assumption here are
1. At any time we have P > T. P can be chosen appropriately based on failure rate.
2. The tasks are stateless. That is any process P_i that takes up a task T_j does not know the state of the process P_k which previously processed T_j. This is not entirely true and there are ways to over come this draw back on a case by case basis.
This was developed for a different project S4 which is also open sourced http://s4.io/. The communication layer and task management layer is completely independent of S4 and can be used in any application.
> Recipe: Fault tolerant communication layer using Zookeeper
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-924
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-924
> Project: Zookeeper
> Issue Type: Task
> Components: recipes
> Environment: Any
> Reporter: kishore gopalakrishna
>
> This recipe caters to the following use case
> There are S(Active) + s(standby) sender nodes and R(Active) + r(standby) receiver nodes. The objective is following
> * If one of the S Active server goes down a standby node should take up the task.
> * If one of the R Active server goes down a standby node should take up the task.
> * When there is a change in receiver the Sender must get updated and send the message to correct destination
> This also uses recipe described in https://issues.apache.org/jira/browse/ZOOKEEPER-923
> This was developed for a different project S4 which is also open sourced http://s4.io/. The communication layer and task management layer is completely independent of S4 and can be used in any application.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.