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

Ability to disable WAL (Non recoverable case)

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.4
    • cache, persistence, sql
    • None

    Description

      1) WAL should be disabled by custom discovery message

      • without triggering exchange,
      • without triggering checkpoint (since it's non recoverable case)

      In case someone is trying to disable already disabled WAL he should be notified that WAL already disabled
      Only cachegroups containing one cache can de disabled

      2) WAL should be prepared to be enabled by custom discovery message with

      • triggering exchange,
      • disabling cache proxies,
      • waiting for checkpoints at every node.

      In case someone is trying to enable already enablling WAL he should be notified that enabling in progress.

      3) WAL should be enabled by custom discovery message

      • without triggering exchange
        but
      • with enabling proxies
        once all nodes finished their checkpoints.

      Failover:
      On any failure during loading (while WAL disabled or enabling) we should be able to reactivate cluster without affected caches content.
      Originating node fail should be covered (at WAL disabled and enabling cases)

      API:
      Public API should be located at IgniteCluster

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            vozerov Vladimir Ozerov
            avinogradov Anton Vinogradov (Obsolete, actual is "av")
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment