As stated above, upon creation, the cluster will choose a node that will be responsible for the data subscription server-side processing.
Once chosen, that node will be the only node to process the subscription. There is an enterprise license level feature
that supports subscription (and any other ongoing task)
failover between nodes, but eventually, as long as the originally assigned node is online, it will be the one to process the data subscription.
Nevertheless, there is an option to manually decide the node that will be responsible for the subscription processing, it's called the
name = await store.Subscriptions.CreateAsync(new SubscriptionCreationOptions<Order>
MentorNode = "D"
The mentor node receives the responsible node tag, as can be seen in the subscription topology.
Setting that node manually can help manually choosing a more fitting server from resources, client proximity, or any other point of view.