[
https://issues.apache.org/jira/browse/FINERACT-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihaly Dallos closed FINERACT-1942.
-----------------------------------
> Graceful shutdown of Fineract
> -----------------------------
>
> Key: FINERACT-1942
> URL: https://issues.apache.org/jira/browse/FINERACT-1942
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Mihaly Dallos
> Assignee: Mihaly Dallos
> Priority: Minor
> Labels: PepperSoup
> Fix For: 1.9.0
>
>
> h3. API:
> The APIs in Fineract should be able to shut down gracefully, i.e. not
> accepting any more HTTP requests upon receiving the SIGTERM signal but
> finishing all in-flight HTTP requests.
> *Notes:* Spring Boot has built-in support for this. See:
> [!https://docs.spring.io/favicon.ico!Spring Boot Reference
> Documentation|https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#web.graceful-shutdown]
> *APIs not concerned* (OK either way)
> * Asynchronous APIs (only available on batch manager instance)
> * Jobs APIs (only available on batch manager instance)
> * Only batch manager relevant APIs
> h3. Batch workers
> The batch workers should be able to react to a SIGTERM signal by waiting to
> finish all in-flight partitions and not accepting any more work from the JMS
> queue. When everything in-flight is finished, the application can shut
> down.{*}{*}
> {panel}
> *Acceptance criteria*
> * Upon receiving the SIGTERM signal, the application should stop accepting
> new HTTP requests
> * Upon receiving the SIGTERM signal, the application should finish any
> in-flight HTTP request
> * Upon receiving the SIGTERM signal, the application should stop accepting
> new partitions via JMS
> * Upon receiving the SIGTERM signal, the application should finish any
> in-flight partitions{panel}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)