On 04/02/2016 10:41, "Jean-Marc Vanel" <jeanmarc.va...@gmail.com> wrote:
>The journal workspace you mention is on disk , isn't it ? My problem is >not >on disk at all. No The journal is both in-memory and on-disk as it is a Write ahead log for failure recovery purposes, the disk portion preserves the data for failure recovery while the in-memory portion provides data to the live instance. If there is a non-empty journal on disk then there is a corresponding amount of memory within the JVM heap used to store the latest state of the data for subsequent transactions while not overwriting the old state of the data which ongoing transactions may still be accessing Rob
