I mean, for example; we provide max value 500MB for durable memory under
eviction policy, that will make sure Ignite will only use 500MB from the
RAM no matter what. When native persistence comes into the picture, Ignite
store entries in disk. So if we run on production, we want to make sure we
don't run out of disk space for any reason. So something configurable like
X GBs max for persistence.
On Tue, Mar 13, 2018 at 3:30 AM, Dmitry Pavlov <dpavlov....@gmail.com>
> Hi, I'm not sure I understand what high watermark for persistence mean.
> Could you please explain?
> пн, 12 мар. 2018 г. в 19:43, Subash Chaturanga <subash...@gmail.com>:
>> Thank you very much for the responses.
>> Will keep an eye on when it will be released. Any estimated release for
>> the fix ?
>> One more question I asked was, can we provide a high watermark for
>> persistence store ?
>> On Mon, Mar 12, 2018 at 12:24 PM vkulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>> Currently expired entry is removed only from memory. The same will be
>>> supported for persistence layer after this ticket is implemented:
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/