Closed vadimkorr closed 7 years ago
Several things here.
Using localhost
as IP address (or 127.0.0.1
for that matter) doesn't allow connections from other machines. That may be the immediate problem you are seeing. Need to use a real IP address or host name instead.
The configuration option of using a seed node (aka primary) is inherently unreliable because it requires the seed node to stay up the whole time. Have you considered a reliable configuration option with cluster membership table externalized to storage?
It is possible to use a single config file for all nodes in the cluster. You can use Address=""
to automatically pick up the host name of each silo. Seed node is the one address/host name that still has to be hardcoded. That works for a single silo per server. Otherwise, you can use overrides, but that's a bit more complicated to get right.
We've been promoting programmatic configuration as the preferred way of configuring silos and clients. Going forward it will be even more so. XML configs still work, and will continue to be supported for some time. But beware that that's not the direction we plan to invest in.
Sergey, thank you so much for fast and useful feedback. Specifying the Address="" and using real IP address (disabling Virtual Adapters used by virtual machines from Network Connections) solved the problem. Works like a charm!
Great. I'll close the issue then. Thanks for confirming.
[.NET Framework 4.7, Orleans 1.5, Win10 Enterprise x64]
I'm using the following
OrleansConfiguration.xml
for deploying with the script.In order not to change respective addresses on each node of the cluster I put the IP address to
SeedNode
(assuming thatSeedNode
is constant for each node, butNetworking
,ProxyingGateway
are unique ones)(Or at least how is it possible to use only one
OrleansConfiguration.xml
for the cluster, instead of changing it on each node?)Thank you in advance!
This approach causes an error: