Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-7920

Research local crash recovery speed after stop in the middle of checkpoint

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Information Provided
    • None
    • None
    • persistence
    • None

    Description

      When using Ignite as a database on one node, I observed that the recovery time using the WAL exceeds the time between checkpoints.

      Ignite logs message that it is restored after stopping in the middle of the checkpoint

      I use the frequency of CP - setCheckpointFrequency (60 * 1000), but at server with HDD and heavy IO load. At least 16 minutes required to restore Ignite after stop.

      Server monitoring states that high rate of IOPS ocurred and it is constraint (there is plenty of CPU/RAM)

      Attachments

        Issue Links

          is a parent of

          Task - A task that needs to be done. IGNITE-9720 Initialize partition free lists lazily

          • Major - Major loss of function.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-7943 Node hangs on start after failing during checkpoint.

          • Major - Major loss of function.
          • Closed

          Activity

            People

              dpavlov Dmitry Pavlov
              dpavlov Dmitry Pavlov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: