Hello!
In both cases Ignite will walk through the segments it needs, and adjust
persistence for any data that was updated in already completed operations.
Archive or no archive is a logistical choice, as far as my understanding
goes.
Regards,
--
Ilya Kasnacheev
вт, 12 мая 2020 г. в 07:28,
Hi Alex,
Are you saying if we disable WAL Archiving, will there be any problem?
Let's say if I disable WAL archiving and if 6 out of 10 WAL segments are
filled then what happens during OS crash?
When we restart the server, will all the operations in those 6 segments be
updated on the disc data
Hi,
You need to be careful w/disabling WAL archiving.
It is best to put the WAL on a separate (quicker) disk:
https://apacheignite.readme.io/docs/durable-
memory-tuning#separate-disk-device-for-wal
This section will be of benefit to you when tuning persistence:
Hi Alex, thanks for the reply.
But as our application is write/update intensive, we want a good
performance/high availability application solution along with disk
persistence.
In that case, what configuration would you suggest for the following case,
1. Disk storing functionality can run
Hi,
Throttling is applied to page modifications [percentOfPartTime=0.62,
markDirty=2440 pages/sec, checkpointWrite=1971 pages/sec,
estIdealMarkDirty=0 pages/sec, curDirty=0.00, maxDirty=0.02,
avgParkTime=253807 ns, pages: (total=132474, evicted=0, written=831,
synced=0, cpBufUsed=543,
We are running a write-intensive load test on Apache Ignite. We are also
doing reads. We are getting the following warning messages from sys-stripe
threads quite often after a few hours of testing.
DB Config ->
RAM - 8GB, CPU cores - 64,
Persistence - ON,
Heap - 2GB, Durable memory Off-heap -
