[ 
https://issues.apache.org/jira/browse/FINERACT-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Saghy updated FINERACT-2924:
---------------------------------
    Fix Version/s: 1.16.0

> Add fineract.job.reset-scheduler-on-bootup-enabled to keep a stopped 
> scheduler suspended across restarts
> --------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-2924
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2924
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Arnold Galovics
>            Assignee: Arnold Galovics
>            Priority: Major
>             Fix For: 1.16.0
>
>
> ✅ Acceptance Criteria
> • New property fineract.job.reset-scheduler-on-bootup-enabled (env 
> FINERACT_JOB_RESET_SCHEDULER_ON_BOOTUP_ENABLED), default true, so behaviour 
> is unchanged by default.
> • The default is set in the FineractJobProperties field initializer, so a 
> properties file without the key keeps today's behaviour.
> • When false, boot ignores the reset_scheduler_on_bootup column, so a 
> scheduler stopped with POST /scheduler?command=stop stays suspended after a 
> restart.
> • A unit test of JobSchedulerServiceImpl covers boot with a stopped 
> scheduler, with the property on and off.
> • The property is documented in batch-jobs.adoc.
>  
> 📘 Background
> • POST /scheduler?command=stop leaves reset_scheduler_on_bootup=true, so the 
> next batch-manager boot un-suspends the tenant. There is no REST endpoint for 
> that column, so an operator who wants a REST stop to survive a restart has to 
> update the column in the database.
>  
> 🔧 Technical Notes
> • JobSchedulerServiceImpl boot loop (1.15.0 around line 78): add the property 
> check to the reset_scheduler_on_bootup condition.
> • Wire the field in FineractProperties.FineractJobProperties and 
> application.properties like the other fineract.job.* properties.
> • Small and independent of the missed-runs ticket, but both edit the same 
> lines, so merge this first.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to