Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66243

Unwind continuation chains with a loop

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Service Arch

    Description

      Currently continuation chains are being resolved with a call stack based approach. This has a couple consequences:

      • Challenging callback destructor ordering semantics which need to be individually addressed in SERVER-66126
      • Large stacks leading to stack overflows

      Currently, the benefit that we get from the stack based resolution is some extra context in dumps (only with non-executor continuations on non-ready futures). Before committing to this task, it's worth considering whether that benefit is worth preserving, and it's worth looking into improvements that can be made to debugability in all cases.

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            matt.diener@mongodb.com Matt Diener (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: