Guys,
I see the NPE is the stack trace which suggest that this is a bug and not a
misconfiguration:
Suppressed: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.getPageMemoryForCacheGroup(GridCacheDatabaseSharedManager.java:1451)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1396)
Dmitriy, could you reproduce the issue? It should be easy to do this
considering the place where NPE happened.
—
Denis
> On Aug 15, 2017, at 2:00 AM, dkarachentsev <[email protected]> wrote:
>
> Hi,
>
> The big slowdown gives writing WAL into disk. You may increase throughput by
> setting lower fail safe requirements: set
> PersistentStoreConfigiration.setWalMode() to LOG_ONLY (data may be lost on
> power off) or BACKGROUND (data may be lost on process crash), or increase
> available memory and set lower checkpoint frequency
> PersistentStoreConfigiration.setCheckpointingFrequency().
>
> Thanks!
> -Dmitry.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-while-starting-service-grid-with-persistent-store-enabled-tp15946p16196.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
