Sergey, I tweaked the example following your suggestion. Now it works, thanks.
In addition, a javadoc of MemoryConfiguraiton, MemoryPolicyConfiguration and DataPageEvictionMode has been significantly improved. There are some of the parameters like page memory’s concurrency mode and policy’s "empty page pool size" that are not obvious. Marked all the blur places in those configurations with TODOs and created a ticket [1]. * Alex G *, as an architect of the page memory, please look at [1] and try to close it tomorrow so that I can complete the readme part. Finally, as for the out of memory exception I fully support Dmitriy’s opinion - let’s be as more concrete as possible. "Failed to allocate new page within <MemoryPolicyName> MemoryPolicy” sounds to generic and doesn’t help me anyhow. Let’s add to the message what was a root cause (policy size, name, etc.) so that the user can fix it immediately. Created a ticket [2]. [1] https://issues.apache.org/jira/browse/IGNITE-5007 <https://issues.apache.org/jira/browse/IGNITE-5007> [2] https://issues.apache.org/jira/browse/IGNITE-5008 — Denis > On Apr 17, 2017, at 2:18 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > On Mon, Apr 17, 2017 at 9:06 AM, Sergey Chugunov <sergey.chugu...@gmail.com> > wrote: > >> Dmitriy, >> >> I think this issue highlights another lack in our documentation that >> emerged with introduction of PageMemory. >> >> In current documentation we have some recommendations about memory capacity >> planning. >> As PageMemory storage data structures introduce their own overhead; this >> section of documentation must be updated. >> >> As per "null" in OutOfMemoryException message, I've already addressed it so >> now when PageMemory fails to allocate new page, it throws an >> IgniteOutOfMemoryException with message like "Failed to allocate new page >> within <MemoryPolicyName> MemoryPolicy". >> > > Sergey, the error message should also mention which configuration property > needs to be changed to fix the issue.
