Hi Val At the time of this issue i checked topology through visor and all 3 client and 2 server nodes were there. There were no items in any cache. I could see caches created on all 5 nodes (near cache on 3 clients and replicated cache on 2 servers). I also tried cleaning a cache through visor through command "cache -clear -c=PROGRAMS" which caused exception trace as i mentioned previously. I tried multiple times and got same error. I was running visor on one on the hosts of server nodes.
Shouldn't a node be dropped from topology if its not accessible due to any issue? Exception trace with class loader related exceptions, error in uodate when cache is empty on all nodes, all nodes visible in visor topology and getting same exception on repeated tries to clean a cache seems like pointing to problem other than network or node accessibility issue. I restarted ignite server nodes but problem was still there. I had to stop all ignite nodes including clients to resolve problem. Even more interesting thing is that i did not faced any issue on my DEV and QA environment when i did cache changes and restarted just server nodes. I faced this problem on pre-prod where i had to restart all nodes. Regards, Vinay Sharma On Feb 17, 2016 7:05 PM, "vkulichenko [via Apache Ignite Users]" < ml-node+s70518n306...@n6.nabble.com> wrote: > Hi Vinay, > > CachePartialUpdateException is thrown by an update operation (put, putAll, > remove, removeAll, ...) if updates for one or more keys involved in this > operation failed. This exception has failedKeys() method that tells you > which keys failed so that you can retry only them, no need to retry > successful ones. > > Most likely you were getting these exceptions when there were no server > nodes in the topology. Is this the case? > > -Val > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3066.html > To unsubscribe from changed cache configuration and restarted server > nodes. Getting exception., click here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3064&code=dmluc2hhcm1hLnRlY2hAZ21haWwuY29tfDMwNjR8ODIyNDgwNzMy> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3070.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
