Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M margo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sds
  • margo
  • Issues
  • #36

Closed
Open
Created Jan 04, 2018 by Shane Snyder@ssnyderOwner

add functionality for pushing shutdown callbacks into margo

Since margo is essentially the glue that will bind many composable microservices together, it should offer a mechanism to allow composed services to shutdown coherently. Currently, it offers a margo_finalize() call that is used to tear down the margo RTE, and a margo_wait_for_finalize() call that blocks until the former call has been invoked. The issue is that services overlying margo may have other shutdown routines that need to be executed, some of which may require a margo instance as input -- these routines can not be invoked if margo has already been shutdown.

To address this, we should add an API to allow other services to push shutdown callbacks into margo, with these callbacks popped off this stack in order to make sure all services are shut down cleanly.

Assignee
Assign to
Time tracking