You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Aleksandar Vidakovic (Jira)" <ji...@apache.org> on 2022/11/07 13:44:00 UTC
[jira] [Resolved] (FINERACT-1795) Improve resilience of command processing service
[ https://issues.apache.org/jira/browse/FINERACT-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandar Vidakovic resolved FINERACT-1795.
--------------------------------------------
Resolution: Fixed
Includes also cleanups (removed injected, but unused services and components; fixed "manual" dependency injections in a few places... we shouldn't really do this).
> Improve resilience of command processing service
> ------------------------------------------------
>
> Key: FINERACT-1795
> URL: https://issues.apache.org/jira/browse/FINERACT-1795
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Aleksandar Vidakovic
> Assignee: Aleksandar Vidakovic
> Priority: Major
> Fix For: 1.9.0
>
>
> Improve the resilience of the command processing service and make retry (and other parameters) configurable (provide reasonable defaults).
> The current retry mechanics in place are causing various congestion issues in high traffic deployments. Besides that, we always have to lookup the tenant to retrieve the retry configuration; Spring Boot's application.properties are the proper place for that.
> Retries are used currently with 4 service function calls and the code used to implement retries is very repetitive and not very adjustable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)