[
https://issues.apache.org/jira/browse/IGNITE-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636669#comment-17636669
]
Ignite TC Bot commented on IGNITE-18195:
----------------------------------------
{panel:title=Branch: [pull/10386/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10386/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6918230&buildTypeId=IgniteTests24Java8_RunAll]
> Improve message for restart after WAL disabled
> ----------------------------------------------
>
> Key: IGNITE-18195
> URL: https://issues.apache.org/jira/browse/IGNITE-18195
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we have this message
> {noformat}
> Cache groups with potentially corrupted partition files found. To cleanup
> them maintenance is needed, node will enter maintenance mode on next restart.
> Cleanup cache group folders manually or trigger maintenance action to do that
> and restart the node. Corrupted files are located in subdirectories
> {noformat}
> The message is not very informative and doesn't provide detailed instructions
> of how to deal with the situation.
> The better message could be:
> {noformat}
> Ignite node with disabled WAL was stopped in the middle of a checkpoint, data
> files may be corrupted. Node will stop and enter the Maintenance Mode on next
> start.
> In the Maintenance Mode, use the Control Utility *persistence* command to
> clean and optionally back up corrupted files. When cleaning is done, restart
> the node manually.
> Possible corruption affects the following cache groups: <list of cache groups>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
