Delayed initial streaming when consuming from more than one silo cluster
- Dominant language
- C#
- Stars
- 10.9k
- Forks
- 2.1k
- Avg merge
- 13h 56m
- Merged PRs (30d)
- 351
Description
Hello,
On our project we wanted push values to blazor ui with memory streaming, blazor acting as outside cluster client.
There is initial delay about 30s when start consuming from stream if cluster has more than one silo.
It degrades user experience greatly so we switched to some other mechanism, we dont use orleans memory streaming anymore because of this.
I created repro repo here [https://github.com/spingee/DelayedStreaming](url).
Run docker compose (it will run single instance of server), you will see that in client console stream consuming starts immidetly.
Stop client and scale server to more than one instance. Start client and you will see (sometime there is just one message) that there is about 30s delay before messages starts arrive.
Tested on Macbook pro and windows destop.
Contributor guide
Research direction
Start with the linked reproduction repository and follow its Docker Compose steps: compare stream consumption with one server instance and with multiple instances. The issue reports an approximately 30-second delay in Orleans memory streaming when a Blazor client consumes across multiple silo clusters; investigate the cause and verify consumption starts promptly in the multi-instance setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100