@dshen ,any one suggest is it real workflow, it seems like we found some gap.
1- GP-LB is receiving the request from client, then as part of load balance we are telling to go to let sey-GP-Node1 in this example.
2- From GP-Node1 to control plane flow(3) is to get the pipeline(meta data) to be execute or what ?
3- If yes then control plane should chose GP-node1 to execute the pipeline since it was asked by GP-LB.
Can any body explain the actual design.
Hi,
Step 2 only happens if the task is not already cached on the node itself.
Step 3, the control plane plays no role in choosing the node for execution in the Ground invoked case.
The communication is outbound from the GP Node to the control plane to fetch the depending assets for execution if they are not cached as stated before.
Thanks @cjhoward18 for the info, correct me this flow if my understanding is correct due to cache and we have two cases.
Case1:
In this case if task is already cached in GP-Node1, it will execute the task and will sent response back to GP-LB and request will not go to control plane at all.
Case2:
in case task is not cached then request will go from GP-Node1 to control plane and control plane will not decide as you mentioned which node is going to be execute the task, it must be the same node (GP-Node1), from where request goes to control plane.
is there anyway we can check task is cached previously or not before execution?
No, there is no way to check before execution.
Is there a use case or problem to be solved that you could shed some light on at a high level?
@cjhoward18 thanks, Load balance flow is working as we discussed, will update the above flow chart. Related to cache, one of the case was like, newly crated account was not working, we had to restart the node, it was different cause and not related to Load balance, it was node property parameter jvm key related. will create a separate page for this.
But coming to our load balance cache case: Lets assume below.
1- Trigger task ran first time, it will keep the asset in node1.
2- Assume we modified the asset and it got saved in control plane.
3 - Trigger task ran 2nd time, will it pick up the updated asset or already cached one.
In this case if updated one, then there is no need to restart the node.
It will help us in automation.
