[ 
https://issues.apache.org/jira/browse/IGNITE-29209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139099#comment-18139099
 ] 

Anton Vinogradov commented on IGNITE-29209:
-------------------------------------------

[Ignite PR Checker|https://ignite-pr-checker.is-a.dev/?pr=13751] verdict for PR 
13751 · RunAll build [9473877|https://ci2.ignite.apache.org/build/9473877] · 
tested 
[0d8a872|https://github.com/apache/ignite/pull/13751/commits/0d8a872f3551ce4172320ef218c4c43bdd33d04d]
 · 149 suites ran, 0 reused

(/) *No blockers* — nothing in this run looks caused by this PR. 25 failing 
tests are not blamed on this PR.

_What each label means and what to do: [verdict 
glossary|https://github.com/anton-vinogradov/ignite-pr-checker/blob/main/docs/features.md#verdict-glossary]._

♻️ Settled after 1 auto re-run wave: #1 — 2 suites that failed mid-run.

> Allow SSL context factories to reload their context
> ---------------------------------------------------
>
>                 Key: IGNITE-29209
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29209
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>              Labels: ise
>          Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> A subclass of {{AbstractSslContextFactory}} can call the protected {{init()}} 
> method to pick up updated TLS settings and stores before a node restarts with 
> the same factory instance. If loading succeeds, the base {{create()}} returns 
> the new context. If it fails, the previous context stays cached.
> h3. Compatibility
> {{init()}} is final. If your subclass already declares a no-argument 
> {{init()}} method, rename it and recompile the subclass before upgrading. A 
> subclass built against an earlier release may fail to load.
> [PR #13751|https://github.com/apache/ignite/pull/13751]



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to