Only one silo comes up
- Dominant language
- C#
- Stars
- 10.9k
- Forks
- 2.1k
- Avg merge
- 14h 42m
- Merged PRs (30d)
- 354
Description
We have 2 silos using ADO.NET clustering, but only one of them is coming up, the first one of the cluster whether it's silo1 or silo2. Logs in the failing silo (second silo) suggest that the target silo (first silo) is not active but it is up and the membership table is also saying the same. The failing silo gets stuck in "Joining" status. Please help!
Membership table:
Error logs from failing silo:
Contributor guide
Research direction
Start by reproducing the two-silo setup with ADO.NET clustering and compare the failing silo's logs with the membership table shown in the issue. Trace why the second silo remains in "Joining" while the first is considered active; done means both silos start successfully and membership reports them as active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100