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 increase checkpointPageBufferSize 6) restarted IGNITE processes 7) continued loading for 2 days 8) deactivated cluster 9) changed the config xml, but /only/ thread pool sizes 10) restarted IGNITE processes
And we found on after step 10 that caches A,B,C,D were *empty*, and only X had data. We did not look at the cache sizes after step 6. Is this expected behavior? It is not what we would have expected from reading the documents. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
