Skip to content

IGNITE-28243 Keep service descriptor even if no deployments#12910

Merged
nizhikov merged 10 commits intoapache:masterfrom
nizhikov:IGNITE-28243
Mar 19, 2026
Merged

IGNITE-28243 Keep service descriptor even if no deployments#12910
nizhikov merged 10 commits intoapache:masterfrom
nizhikov:IGNITE-28243

Conversation

@nizhikov
Copy link
Contributor

@nizhikov nizhikov commented Mar 18, 2026

Some users implements the following scenario:

  1. Starts sever node (configuration node), first, with the service configuration. NodeFilter like n -> n.isClient().
  2. Starts client nodes that hosts service. Count of the clients depends on the expected workload.

This case was broken in the 66a4a2d
This PR fix regression.

* Tests check the following case:
* 1. Node "A" starts with the service configuration. But, NodeFilter filter out node "A".
* 2. Node "B" starts and NodeFilter conforms it.
* 3. Expect that service will be deployed on node "B".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 3. Expect that service will be deployed on node "B".
* 3. It is expected that service will be deployed on node "B".

@sonarqubecloud
Copy link

@nizhikov nizhikov merged commit ef685f5 into apache:master Mar 19, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants