[
https://issues.apache.org/jira/browse/IGNITE-28487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-28487:
----------------------------------------
Description: 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. (was:
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 nodes.)
> 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)
