Re: [Katta-developer] Lifetime of DeployClient?

[Murali K. P <mur...@ya...>]

Thanks Johannes,
    Restarting the client fixes it. I haven't tried with reinit of client 
objects. Once restarting the katta nodes also fixed. (by fix, I mean further 
deployments succeed, that particular index needs to be redeployed) So, I am not 
clear what exactly the problem. I am able to search the index. Katta version we 
are using is 0.6.2. 

    Since it takes around 40 hours to happen again, it is getting difficult to 
investigate systematicaly. When it happens again, I will send you the 
zk-filesystem structure. Also I will keep the system without any restart so that 
we can debug this together. Thanks for the support.

 Thanks,
Murali Krishna




________________________________
From: Johannes Zillmann <jzi...@go...>
To: kat...@li...
Sent: Fri, 21 January, 2011 12:48:17 AM
Subject: Re: [Katta-developer] Lifetime of DeployClient?

Hi Murali,

hmm thats strange.. looking at the code i've no clue how this can happen. 
If somethings not correct with the zkclient i would expect an exception but not 
wrong data...
Does it help if you reinitialize all the time ?
Can you search the index ? (Maybe the client is right but there is somehow the 
master is stuck... - which katta version do you use ?)

If this is happening, could you print the structure of the zk-filesystem 
(bin/katta showStructure -d) and send the output together with the index name 
you are trying to deploy over ?

Johannes

On Jan 19, 2011, at 6:21 PM, Murali Krishna. P wrote:

> Hi,
> I have a question on zkclient and deployclient's lifetime. Can we use the same 
>deployClient through out the process without recreating the interaction protocol 
>or deployclient at the client side? Can this still work even if Zookeeper 
>processes or katta nodes gets restarted in between? 
>
> 
>     In our cluster, we keep deploying indices every 10 minutes with the same 
>deplpy client and we are seeing a problem where after a day or so, the deploy 
>operation gets stuck. Essentially, the IIndexDeployFuture.getState() always 
>returns IndexState.DEPLOYING. I am just thinking whether this is related to some 
>problem with Deployclient and we should reinitialize zkclient, 
>interactionprotocol and deployclient every time ?
> 
> My code snippet is as below to
>  keep the deployClient in memory.
> 
>         ZkConfiguration zkConf = new ZkConfiguration();
>         ZkClient zkClient = new ZkClient(zkConf.getZKServers());
>         InteractionProtocol protocol = new InteractionProtocol(zkClient, 
>zkConf);
>         deployClient = new DeployClient(protocol);
>  
> Thanks,
> Murali Krishna
> 
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
>http://p.sf.net/sfu/oracle-sfdevnl_______________________________________________
>_
> Katta-developer mailing list
> Kat...@li...
> https://lists.sourceforge.net/lists/listinfo/katta-developer


------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Katta-developer mailing list
Kat...@li...
https://lists.sourceforge.net/lists/listinfo/katta-developer