[
https://issues.apache.org/jira/browse/IGNITE-28487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075336#comment-18075336
]
Ignite TC Bot commented on IGNITE-28487:
----------------------------------------
{panel:title=Branch: [pull/13008/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 14{color} [[tests 0 TIMEOUT , Exit Code , Failure on
metric |https://ci2.ignite.apache.org/viewLog.html?buildId=9022552]]
{panel}
{panel:title=Branch: [pull/13008/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=9022526&buildTypeId=IgniteTests24Java8_RunAll]
> Change default startup config for more cluster operability
> ----------------------------------------------------------
>
> Key: IGNITE-28487
> URL: https://issues.apache.org/jira/browse/IGNITE-28487
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.18
> Reporter: Evgeny Stanilovsky
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Default cluster config (in scope of binary or package deployment) has empty
> "IgniteConfiguration#discoverySpi" thus 2 runs of ./bin/ignite.sh will create
> 2 different clusters, which can confuse especially on initial product
> introduction phase. I suggest to change it in order to one cluster will
> contain two or more nodes during initial startup testing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
