[
https://issues.apache.org/jira/browse/IGNITE-28657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignite TC Bot updated IGNITE-28657:
-----------------------------------
Release Note: Ignite services can now be assigned a node-local startup
order via ServiceConfiguration.setLocalStartOrder(int). When several services
are configured or deployed together, services with lower localStartOrder values
are initialized first, helping applications with dependent services start
reliably on a node.
> Service start order
> -------------------
>
> Key: IGNITE-28657
> URL: https://issues.apache.org/jira/browse/IGNITE-28657
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Minor
> Labels: ise
> Fix For: 2.19
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Ignite supports service grid scenarios.
> In case of complex services logic there may be dependencies between services:
> One service invoke another.
> Currently, Ignite doesn't guarantee start order so one service can be started
> but dependency one not.
> `startOrder` must be introduced to ensure correct start order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
