Make remote exceptions traceable

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The goal is to pin exceptions to their source in presence of multiple levels of RPCs (remote procedure calls). For example, assume node A contacts node B to run an operation against node C. If node C steps down while running this operation and the error is passed through to node A, node A should be able to distinguish this from node B stepping down.

              Assignee:
              Unassigned
              Reporter:
              Amirsaman Memaripour
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: