[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521513#comment-16521513
]
ASF GitHub Bot commented on FINERACT-429:
-----------------------------------------
GitHub user wkk91193 opened a pull request:
https://github.com/apache/fineract/pull/459
FINERACT-429: Node aware Scheduler
[Fineract-429](https://issues.apache.org/jira/browse/FINERACT-429)
Executing jobs based on node id
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wkk91193/incubator-fineract
fineract-429-node-aware-scheduler
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/fineract/pull/459.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #459
----
commit abed7b5f0df61b816e2dcb64771ad3dc4d1fdeba
Author: unknown <wkk91193@...>
Date: 2018-06-24T14:02:47Z
Commit-1: Execute jobs based on node_id
commit 68f2bdf885cecc57bd67ffc2a641a57964b66ffe
Author: unknown <wkk91193@...>
Date: 2018-06-24T14:44:30Z
Commit-2:Add dirty job scheduler
----
> Node aware Scheduler
> --------------------
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Avik Ganguly
> Assignee: Markus Geiss
> Priority: Major
> Labels: gsoc, p2
>
> I believe multiple instances of the same job can be created by keeping the
> same job identifier but having different job keys. Additional parameter
> nodeId can be saved in the job table defaulting to 1. Default this parameter
> for a single-instance app-server to 1.
> If node.id parameter exists in the application yaml while deploying, set that
> system property to configured node id.
> Front-end can pass the configured node-id of the job instance as a query
> parameter.
> This will allow the organization to configure something like let Node 1 do
> all accruals for North zonal office and Node 2 do all accruals for South
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
> map $query_string $srvr {
> default https://myapp1 // If it doesn't match, send to load
> balancer
> node=1 srv1.example.com;
> node=2 srv2.example.com;
> node=3 srv3.example.com;
> }
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
