[
https://issues.apache.org/jira/browse/IGNITE-17195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562374#comment-17562374
]
Ignite TC Bot commented on IGNITE-17195:
----------------------------------------
{panel:title=Branch: [pull/10131/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10131/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=6664357&buildTypeId=IgniteTests24Java8_RunAll]
> Failure handler need to trigger if h2 database instance is down for some
> reasons.
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-17195
> URL: https://issues.apache.org/jira/browse/IGNITE-17195
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.13
> Reporter: Evgeny Stanilovsky
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> H2 database can be closed by numerous reasons (internal OOM, some not
> recovered problems and so on..), in such a case we need to call failure
> handler machinery.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
