Hi Denis,

This problem has certain randomness, it is difficult to write a code that can reproduce 100%.

This has been the case in our past tests, with the use of COPY commands to import large amounts of data and in transaction scenarios with KV interfaces.


在 2020/3/12 上午7:20, Denis Magda 写道:
Let's see if and how we can get to root cause together. Try to prepare a small reproducer and elaborate on the instructions to follow to get the
exception.

Please also attach complete log files.

-
Denis


On Wed, Mar 11, 2020 at 3:10 AM 18624049226 <18624049...@163.com <mailto:18624049...@163.com>> wrote:

    Hi Denis,

    In ignite's 2.7 series, if data is written after persistence is
    turned on, page data corruption may occur, but the error message
    is a little different from this, but it has the same meaning.

    In the JIRA list, there are records of similar problems, but some
    have been fixed.
    I know Ilya's way of solving this problem. But this problem is
    more distressing, which brings insecurity to users.

    在 2020/3/11 上午5:01, Denis Magda 写道:
    Does this issue arise under special circumstances? Have you
    experienced this before switching to Ignite 2.8?

    -
    Denis


    On Sat, Mar 7, 2020 at 5:21 PM 18624049226 <18624049...@163.com
    <mailto:18624049...@163.com>> wrote:

        hi community,

        What are the reasons for the following problems? How to avoid it?

Reply via email to