Skip to content
This repository was archived by the owner on Dec 7, 2018. It is now read-only.

Commit 7b15834

Browse files
authored
Merge pull request #65 from AxonFramework/spring-cloud-service-naming
Added a chapter about blacklisting for spring cloud.
2 parents fa97b55 + f7bcbb8 commit 7b15834

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

part-iii-infrastructure-components/spring-boot-autoconfiguration.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -276,3 +276,10 @@ axon.distributed.spring-cloud.fallback-url=/message-routing-information
276276

277277
For more fine-grained control, provide a `SpringCloudHttpBackupCommandRouter` or `SpringCloudCommandRouter` bean in your application context.
278278

279+
#### Blacklisting
280+
281+
On each heartbeat the memberships of all the nodes in the cluster are updated. If message routing information of a given service instance is not available on this heartbeat signal, that specific service instance gets blacklisted. That blacklisted service instance will be removed from the blacklist if it is no longer present on thereon following heartbeats.
282+
283+
> **Note**
284+
>
285+
> It is regarded as good practice to assign a random value to every service instance name. In doing so, if a given service instance is restarted, it will receive a different name which will mitigate unnecessary blacklisting of nodes.

0 commit comments

Comments
 (0)