New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to quiesce node #6220

Open
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@krmahadevan
Contributor

krmahadevan commented Jul 29, 2018

Closes #2070

This PR provides the following:

  1. Expose an end-point on the Hub which lets a user
    quiesce a node. [ Quiesce = don’t route any more new
    session requests to a node and let the in-flight
    sessions run to completion ] via the URL

/lifecycle-manager?action=quiescenode&proxyid=<ProxyId>

  1. Add an optional argument to the end-point in (1)
    to also send a recycle signal to the node [ This would
    ensure that the Grid automatically shuts down a
    quiesced node after the in-flight sessions have run
    to completion ] via the URL
    /lifecycle-manager?action=quiescenode&proxyid=<ProxyId>&autoshutdown=true

  2. Updated the default hub console to also indicate
    if a particular node is “quiesced” or not.

  3. If the user just uses (1) to quiesce a node, then
    they need to shutdown the node on their own. So
    exposed a new URL on the node to support this via
    the URL/lifecycle-manager?action=shutdown


This change is Reviewable

Add ability to quiesce node
Closes #2070

This PR provides the following:

1. Expose an end-point on the Hub which lets a user
quiesce a node. [ Quiesce = don’t route any more new
session requests to a node and let the in-flight
sessions run to completion ] via the URL 

/lifecycle-manager?action=quiescenode&proxyid=<ProxyId>

2. Add an optional argument to the end-point in (1)
to also send a recycle signal to the node [ This would
ensure that the Grid automatically shuts down a 
quiesced node after the in-flight sessions have run 
to completion ] via the URL 
/lifecycle-manager?action=quiescenode&proxyid=<ProxyId>&autoshutdown=true

3. Updated the default hub console to also indicate 
if a particular node is “quiesced” or not.

4. If the user just uses (1) to quiesce a node, then 
they need to shutdown the node on their own. So 
exposed a new URL on the node to support this via
the URL /lifecycle-manager?action=shutdown
@krmahadevan

This comment has been minimized.

Show comment
Hide comment
@krmahadevan

krmahadevan Jul 29, 2018

Contributor

ping @barancev @shs96c - Please help take a look when you get some time.

Contributor

krmahadevan commented Jul 29, 2018

ping @barancev @shs96c - Please help take a look when you get some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment