Skip to content
Orleans cluster communication with Consul membership
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Core
CoreFramework code gen Oct 11, 2017
Grain1 Moved grains and grain interfaces in different projects Sep 30, 2017
Grain2
GrainInterface
GrainInterface1
GrainInterface2
GrainWithState
Library Fixed issue with grain implementation not found because of prefix Oct 6, 2017
OrleansClient
OrleansClient1
OrleansHostApp1.Service more flexibility in initialization Oct 3, 2017
OrleansHostApp2.Service
OrleansHostApp3.SQLMembership.Service Fixed issue with grain implementation not found because of prefix Oct 6, 2017
OrleansHostApp4.ZKMembership.Service Fixed issue with grain implementation not found because of prefix Oct 6, 2017
OrleansSilo Removed test Oct 11, 2017
OrleansSilo1 Added second silo containing other grains to test multi clients for m… Oct 1, 2017
OrleansSilo2
.gitattributes
.gitignore
OrleansClusterConsul.sln Removed test Oct 11, 2017
README.md Update README.md Oct 2, 2017

README.md

Orleans Cluster Consul

Orleans cluster communication with Consul membership.

  • The project contains 2 services, 1 cluster with 1 silo per service.
  • Consul as Membership provider

Cluster and client are contained within the same service. For testing purposes a client is created and a connection is made on each hit of the controller endpoints.

Issue with Consul

The following steps can be taken to reproduce the issue:

  1. Run consul
  2. Run OrleansHostApp1.Service
  3. Notice the silo being registered properly as alive in consul 1
  4. Invoke http://localhost:20007/self
  5. Ctrl+c to close the project
  6. Notice a key being registered in consul using the proxy gateway address with it being marked as dead (status 6), the silo address is still alive (status 3) 2
You can’t perform that action at this time.