ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC
Date Tue, 20 Mar 2018 02:09:54 GMT

What do we understand under "data corruption" here? If a storage is in
corrupted state, does it mean that it needs to be completely removed and
cluster needs to be restarted without data? If so, I'm not sure any mode
that allows corruption makes much sense to me. How am I supposed to use a
database, if virtually any failure can end with complete loss of data?

In any case, this definitely should not be a default behavior. If user ever
switches to corruption-unsafe mode, there should be a clear warning about


On Fri, Mar 16, 2018 at 1:06 AM, Ivan Rakov <ivan.glukos@gmail.com> wrote:

> Ticket to track changes: https://issues.apache.org/jira/browse/IGNITE-7754
> Best Regards,
> Ivan Rakov
> On 16.03.2018 10:58, Dmitriy Setrakyan wrote:
>> On Fri, Mar 16, 2018 at 12:55 AM, Ivan Rakov <ivan.glukos@gmail.com>
>> wrote:
>> Vladimir,
>>> Unlike BACKGROUND, LOG_ONLY provides strict write guarantees unless power
>>> loss has happened.
>>> Seems like we need to measure performance difference to decide whether do
>>> we need separate WAL mode. If it will be invisible, we'll just fix these
>>> bugs without introducing new mode; if it will be perceptible, we'll
>>> continue the discussion about introducing LOG_ONLY_SAFE.
>>> Makes sense?
>>> Yes, this sounds like the right approach.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message