Skip to content

Comments

IGNITE-26157 Enhance the documentation with information about Mainten…#12727

Open
DenisPolo wants to merge 1 commit intoapache:masterfrom
DenisPolo:ignite-26157
Open

IGNITE-26157 Enhance the documentation with information about Mainten…#12727
DenisPolo wants to merge 1 commit intoapache:masterfrom
DenisPolo:ignite-26157

Conversation

@DenisPolo
Copy link
Contributor

…ance Mode

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.


=== Backing Up Damaged Files

Use the `--persistence backup corrupted` option to back up corrupted data files:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where these backup files are stored? What can we do with these files? How to delete backup files after node returns to normal mode if everething is ok? How to use backup files if there is problems with data restoration?
I think backup-files workflow should be described somewhere.


To maintain data consistency, the node marks outdated caches for deletion and enters maintenance mode.

While in maintenance mode, the node automatically deletes outdated caches.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Node was in maintenance mode
  • Cache was deleted in the cluster in this time
  • Node returns to the cluster and need to be returned to maintenance mode again to delete outdated caches?

I'm not sure, but I think outdated caches will be deleted automatically once node exit maintenance mode and join the cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants