Reconnecting RemoteImporter with RemoteExporter after RemoteExporter fails
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 574
- Forks
- 104
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
I'm been trying to see if remoting would help with a problem I'm facing.
I found when the application with RemoteImporter fails and the application restarts, it automatically reconnects with the exporting application.
However, I was unable to do the opposite. As far as I can tell, after the application with RemoteExporter fails and restart, the application with RemoteImporter never reconnects. Is there a setting I'm missing or it does not have that capability?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the RemoteImporter and RemoteExporter implementations and reproduce the failure-and-restart sequence described in the issue. Trace the reconnection behavior in both directions and check whether an existing setting controls it. Done means the importer reconnects after the exporter restarts, or the supported limitation and configuration are clearly documented.
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
- Needs clarification
- Newbie friendliness
- 25/100