Hi,
It might be an issue with deactivation. Try update to 2.6 or wait 2.7. Right
now just skip cluster deactivation. Once you formed a baseline topology and
finished loading data, just enable WAL log for all caches. When log enabled
successfully, you can safely stop nodes.
On next time when all b
We did the following while loading a lot of data into 2.5
1) Started data loading on 8 node cluster
2) ALTER TABLE name NOLOGGING on tables A,B,C,D but not X
3) continued loading
4) deactivated cluster
5) changed the config xml, to increase maxSize of the data region (from 2G
to 160G) and increas
