On Fri, May 25, 2012 at 5:52 PM, Charith Wickramarachchi
<[email protected]>wrote:

>
>
> On Fri, May 25, 2012 at 5:30 PM, Anjana Fernando <[email protected]> wrote:
>
>> Hi,
>>
>> On Fri, May 25, 2012 at 1:25 PM, Charith Wickramarachchi <
>> [email protected]> wrote:
>>
>>>
>>> clustered scenario, the user can explicitly install the
>>> coordination.server feature.
>>>
>>> Yes even in out case user can point to a external zookeeper cluster.
>>> What we thought was to ship coordination feature with the product by
>>> default So that based on the configuration it will start zookeeper server.
>>>
>>> We do not always start zookeeper inside MB Cluster. As an example
>>> there can be scenarios where in a 5 node MB cluster there can be
>>> 4 Cassandra node cluster and 3 zookeeper node cluster. Since we thought of
>>> shipping coordination feature with product by default we need to have
>>> option to disable the starting of zookeeper by default and start it depend
>>> on the cluster configuration.
>>>
>>
>> I see, in that case, you can put a configuration file to
>> coordination.server to read it when starting up, to check if it should
>> start automatically or not, and also expose an OSGi service to control it.
>>
>> Yaa. I was thinking the same. I did same for Cassandra component to
> achieve the same behavior.
>
>
This is now added to the Trunk.

Now Coordination Server got a OSGI service from which other components can
start/stop server and get configuration details.

By default coordination server component will start the zk with the bundle
activation (This is the previous behavior we had. i made it the
 default behavior for Backward compatibility )

Optionally now there is a parameter in zoo.cfg :
"start_zk_server=true|false" which can be configured so that if its false
coordination server component will not start the zk server.

cheers,
Charith

>
> cheers,
> Charith
>
>
>> Cheers,
>> Anjana.
>>
>>
>>>
>>> --Charith
>>>
>>>
>>>>
>>>> Cheers,
>>>> Anjana.
>>>>
>>>>
>>>>>
>>>>> --Charith
>>>>>
>>>>>
>>>>>
>>>>> In the
>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>> Anjana.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> cheers,
>>>>>>> Charith
>>>>>>>
>>>>>>> --
>>>>>>> Charith Dhanushka Wickramarachchi
>>>>>>> Senior Software Engineer
>>>>>>> WSO2 Inc
>>>>>>> http://wso2.com/
>>>>>>> http://wso2.org/
>>>>>>>
>>>>>>> blog
>>>>>>> http://charithwiki.blogspot.com/
>>>>>>>
>>>>>>> twitter
>>>>>>> http://twitter.com/charithwiki
>>>>>>>
>>>>>>> Mobile : 0776706568
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Anjana Fernando*
>>>>>> Associate Technical Lead
>>>>>> WSO2 Inc. | http://wso2.com
>>>>>> lean . enterprise . middleware
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Charith Dhanushka Wickramarachchi
>>>>> Senior Software Engineer
>>>>> WSO2 Inc
>>>>> http://wso2.com/
>>>>> http://wso2.org/
>>>>>
>>>>> blog
>>>>> http://charithwiki.blogspot.com/
>>>>>
>>>>> twitter
>>>>> http://twitter.com/charithwiki
>>>>>
>>>>> Mobile : 0776706568
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Anjana Fernando*
>>>> Associate Technical Lead
>>>> WSO2 Inc. | http://wso2.com
>>>> lean . enterprise . middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Charith Dhanushka Wickramarachchi
>>> Senior Software Engineer
>>> WSO2 Inc
>>> http://wso2.com/
>>> http://wso2.org/
>>>
>>> blog
>>> http://charithwiki.blogspot.com/
>>>
>>> twitter
>>> http://twitter.com/charithwiki
>>>
>>> Mobile : 0776706568
>>>
>>>
>>>
>>
>>
>> --
>> *Anjana Fernando*
>> Associate Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>
>
> --
> Charith Dhanushka Wickramarachchi
> Senior Software Engineer
> WSO2 Inc
> http://wso2.com/
> http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
> twitter
> http://twitter.com/charithwiki
>
> Mobile : 0776706568
>
>
>


-- 
Charith Dhanushka Wickramarachchi
Senior Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

Mobile : 0776706568
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to