Reconnecting RemoteImporter with RemoteExporter after RemoteExporter fails

Open
#206 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
distributed-systems

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.

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?

Dominant language
C#
Stars
574
Forks
104
Avg merge
19m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/psi

All issues in microsoft/psi

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.