Hi Mahesh, Your problem is described here: https://issues.apache.org/jira/browse/IGNITE-12255 The section starts with "This solution showed the existing race between client node join and concurrent cache destroy." According to your logs, I see concurrent client node join and stop caches "SQL_PUBLIC_INCOME_DATASET_MALLIKARJUNA" and "income_dataset_Mallikarjuna". I think some of them are configured on the client node explicitly.
This problem is already fixed in an open-source fork of Ignite and will be donated to Ignite soon. As a workaround, I can suggest to not explicitly declare caches in the client configuration. During joining to cluster process client node will receive all configured caches from server nodes. ср, 2 окт. 2019 г. в 12:17, Mahesh Renduchintala < mahesh.renduchint...@aline-consulting.com>: > This seems to be a new bug, and unrelated to IGNITE-10010. > Both the nodes were fully operational when the null pointer exception > happened. > The logs show that and both the nodes crashed > > Can you give some insights into this, possible scenarios this could have > led this? > Is there any potential workaround? > >
