How would this fit with our deployment synchronizer?

Paul

On 8 November 2011 17:55, Hiranya Jayathilaka <[email protected]> wrote:

>
>
> On Tue, Nov 8, 2011 at 7:38 PM, Anjana Fernando <[email protected]> wrote:
>
>> Hi,
>>
>> I've created a new Carbon component called "Coordination" to be used for
>> distributed coordination requirements. This is based on Apache ZooKeeper,
>> and both client and the server components are available. The core
>> constructs include the following: Barriers/Double Barriers, Queues /
>> Priority Queues, Locks (can be used to create critical sections), Groups
>> (for leader election, message broadcasting). I've also written some tests
>> as well to test the above, the test are run by running the server component
>> and making calls to it from the tests.
>>
>> I haven't included the component to any product or existing component,
>> the first task is to add the coordination functionalities for the scheduled
>> tasks. This is required when scheduled tasks are run in a cluster
>> environment, where some leader election functionality should be there to
>> select the server which will execute the tasks, and fallback to another
>> option, when that server goes down. Another similar situation would be to
>> register Carbon data sources in JNDI/In-Memory data repository when a data
>> source is added from different server in a cluster (at the moment, this
>> only goes into the registry, and other nodes aren't aware of this). So for
>> requirements such as those, we can use this component.
>>
>
> Can we also use this to manage how artifacts are deployed in a cluster? I
> know that ZooKeeper supports that. Just checking whether we can leverage
> that support in Carbon?
>
> Thanks,
> Hiranya
>
>
>>
>> Cheers,
>> Anjana.
>> --
>> *Anjana Fernando*
>> Senior Software Engineer
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: [email protected];  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
[email protected]

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to