[
https://issues.apache.org/jira/browse/IGNITE-28978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104296#comment-18104296
]
Ignite TC Bot commented on IGNITE-28978:
----------------------------------------
{panel:title=Branch: [pull/13471/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13471/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9278963&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9278963
rerunBuildIds=9280132,9280134,9280136{color}
> Make MDC-aware discovery ring mode testable in a single JVM
> -----------------------------------------------------------
>
> Key: IGNITE-28978
> URL: https://issues.apache.org/jira/browse/IGNITE-28978
> Project: Ignite
> Issue Type: Task
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Minor
> Fix For: 2.19
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{TcpDiscoveryNodesRing}} caches the {{MDC_AWARE_RING}} system property in a
> static final field, so its value is fixed when the class is initialized. This
> prevents JUnit tests from verifying both MDC-aware and legacy ring ordering
> in the same JVM. Store the flag per ring instance while preserving the
> current default and keeping it immutable for the ring lifetime.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
