Hi Vinay,

Thank you for attaching the code. I was able to get to the bottom of the
issue and created a ticket -
https://issues.apache.org/jira/browse/IGNITE-2779
Hope it will be fixed soon.

Vladimir.

On Tue, Mar 1, 2016 at 11:21 PM, vinshar <[email protected]> wrote:

> One observation. Everything works fine if i do not add any QueryIndex to
> QueryEntity. Seems like problem is due to old QueryIndex metadata instance
> being somehow used by client nodes even though all caches on all nodes were
> destroyed and all server nodes restarted.
>
>
> vinshar wrote
> > Hi Vladimir,
> >
> > I am able to reproduce problem and it's not intermittent. Exception
> occurs
> > everytime.
> > I am attaching class with main method which replicates the issue ans also
> > attaching logs.
> > IgniteProblemTest.java
> > <
> http://apache-ignite-users.70518.x6.nabble.com/file/n3307/IgniteProblemTest.java
> >
> >
> > log.txt
> > <http://apache-ignite-users.70518.x6.nabble.com/file/n3307/log.txt>
> >
> > Below is summary of what i am doing in main method
> > 1) create a server node 1 with a replicated cache EMPLOYEE. Wait 10
> > seconds.
> > 2) create a server node 2 with a replicated cache EMPLOYEE. Wait 10
> > seconds.
> > 3) create a client node 1 with a near cache cache EMPLOYEE. Wait 10
> > seconds.
> > 4) create a client node 2 with a near cache cache EMPLOYEE. Wait 10
> > seconds.
> > 5) put 100 entries to both client caches. Only 10 entries remain. Others
> > get evicted.
> > 6) Close both servers and wait for 5 seconds.
> > 7) start servers again with same configs. Wait 10 seconds after start of
> > each server. Some exceptions seen during server close.
> > 8) getOrCreate near caches again on client nodes.
> > 9) Try putting objects again. Exception occurred.
> >
> > Regards,
> > Vinay
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3310.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Reply via email to