>Problem is: 'clientPort', 'dataDir' and 'tickTime'
of zooKeeper can't be
>set via system property, so this is not possible with config admin.
>shared dataDir causes many problems with multiple instances on one
>machine (see other post).
zooDiscovery does check for zooKeeper specific configurational
properties (e.g, DataDir,initLimit,syncLimit,serverPort,..) and overwrite
the defaults with. But I don't think you'll need going that far changing
some specific ones which are/not OK in discovery context. Anyway, if you
intend to do that, please consult those properties documentation at Apache
ZooKeeper page. Could you please post some more details about your scenario/case/needs?
Martin Petzold <mpetzold@xxxxxxx>
Re: [ecf-dev] ZooDiscovery without starting
ANY ZooKeeper instance
Am 07.02.2011 16:46, schrieb Markus Alexander Kuppe:
> On 02/07/2011 03:37 PM, Martin Petzold wrote:
>> What do you think about some improvements about the API?
>> I think i would like to file a Bug for this...
> Hi Martin,
> feel free to file an enhancement bug. But what is it, you wanna
> If you intent to add API to ECF discovery to configure Zookeeper,
> inclined to veto any such API change. ECF discovery has been designed
> provider agnostic. Additionally in OSGi land, bundle configuration
> easily be done with config admin without the need to add programming
I agree with you to have this provider agnostic.
Problem is: 'clientPort', 'dataDir' and 'tickTime' of zooKeeper can't be
set via system property, so this is not possible with config admin. Also
shared dataDir causes many problems with multiple instances on one
machine (see other post).
ecf-dev mailing list