[
https://issues.apache.org/jira/browse/UIMA-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-5814:
--------------------------------
Description:
Currently when an agent receives a stop request through its admin channel it
sends SIGTERM to all its running processes and waits 1 minute for them to stop.
Any process still standing after 1 minute is than killed via SIGKILL.
In addition to stop request, an agent should support a quiesce request (through
an admin channel). When such request is received, an agent should send SIGTERM
to all its running processes but should *not* send SIGKILL to allow each
process to finish its tasks and exit when done. An agent should not start a
timer after sending the SIGTERM.
In quiesce mode, an agent will reject new process allocation requests from the
OR. Such process state will be marked as REJECTED and published to the OR. An
agent will keep publishing metrics and inventory.
In an event an agent process does not exit, a sys admin can send a stop request
to force termination.
In addition to changes in an agent, modifications are also needed in the RM,
perhaps OR, CLI and scripts.
was:
Currently when an agent receives a stop request through its admin channel it
sends SIGTERM to all its running processes and waits 1 minute for them to stop.
Any process still standing after 1 minute is than killed via SIGKILL.
In addition to stop request, an agent should support a quiesce request (through
an admin channel). When such request is received, an agent should send SIGTERM
to all its running processes but should *not* send SIGKILL to allow each
process to finish its tasks and exit when done. An agent should not start a
timer after sending the SIGTERM.
In quiesce mode, an agent will reject new process allocation requests from the
OR. Such process state will be marked as REJECTED and published to the OR. An
agent will keep publishing metrics and inventory.
In an event that a process does not exit, a sys admin can send a stop request
to an agent to force termination.
In addition to changes in an agent, modifications are also needed in the RM,
perhaps OR, CLI and scripts.
> UIMA-DUCC: agent should support quiesce request
> -----------------------------------------------
>
> Key: UIMA-5814
> URL: https://issues.apache.org/jira/browse/UIMA-5814
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> Currently when an agent receives a stop request through its admin channel it
> sends SIGTERM to all its running processes and waits 1 minute for them to
> stop. Any process still standing after 1 minute is than killed via SIGKILL.
> In addition to stop request, an agent should support a quiesce request
> (through an admin channel). When such request is received, an agent should
> send SIGTERM to all its running processes but should *not* send SIGKILL to
> allow each process to finish its tasks and exit when done. An agent should
> not start a timer after sending the SIGTERM.
> In quiesce mode, an agent will reject new process allocation requests from
> the OR. Such process state will be marked as REJECTED and published to the
> OR. An agent will keep publishing metrics and inventory.
> In an event an agent process does not exit, a sys admin can send a stop
> request to force termination.
> In addition to changes in an agent, modifications are also needed in the RM,
> perhaps OR, CLI and scripts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
