ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-11749) Implement automatic pages history dump on CorruptedTreeException
Date Tue, 16 Apr 2019 07:03:00 GMT
Alexey Goncharuk created IGNITE-11749:

             Summary: Implement automatic pages history dump on CorruptedTreeException
                 Key: IGNITE-11749
                 URL: https://issues.apache.org/jira/browse/IGNITE-11749
             Project: Ignite
          Issue Type: Improvement
            Reporter: Alexey Goncharuk

Currently, the only way to debug possible bugs in checkpointer/recovery mechanics is to manually
parse WAL files after the corruption happened. This is not practical for several reasons.
First, it requires manual actions which depend on the content of the exception. Second, it
is not always possible to obtain WAL files (it may contain sensitive data).

We need to add a mechanics which will dump all information required for primary analysis of
the corruption to the exception handler. For example, if an exception happened when materializing
a link {{0xabcd}} written on an index page {{0xdcba}}, we need to dump history of both pages
changes, checkpoint records on the analysis interval. Possibly, we should include FreeList
pages to which the aforementioned pages were included to.

This message was sent by Atlassian JIRA

View raw message