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] [Created] (HELIX-251) Design participant specification for new language bindings
Date Mon, 23 Sep 2013 23:44:03 GMT
Kanak Biscuitwala created HELIX-251:
---------------------------------------

             Summary: Design participant specification for new language bindings
                 Key: HELIX-251
                 URL: https://issues.apache.org/jira/browse/HELIX-251
             Project: Apache Helix
          Issue Type: Task
            Reporter: Kanak Biscuitwala
            Assignee: Kanak Biscuitwala


There is interest in implementing a Helix participant in Node.js and Python. We should determine
the minimal required implementation required for a functional participant in any language.
Currently, the Helix participant does the following:

- creates an ephemeral node under LIVEINSTANCES when it starts
- listen to MESSAGES for controller messages (e.g. "start serving this replica" and "drop
this replica")
- update the current state with the result of the command

We may need to wrap some of this functionality, or we may not. Either way, we should figure
out exactly what a participant should do, keeping in mind room for potential redesigns and
ensuring that maintenance overhead is not too high.

--
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