I have 2 nodes node a and node b (jira cluster enviroment)
and escaltion service job is configured (via Rest API)
this will get all the data and store it in the chacemanager
job will be triggered in any node node a or node.
lets assume job was ran on node a (all the data is cached preperly)
now data replication is done because of data is not yet cached on node be
My problem is : if any end-user open the page in node b, then it is taking long time
because node b is not yet cached
currenlty I am doing manually i have to run to job on node b once it is completed
then only if the user open pages in any node it will be fast
This looks like a classic Jira Data Center caching issue. Since cache isn’t replicated across nodes, users on node B face delays. You may need a shared/distributed cache setup or configure the job to run on all nodes for smoother performance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.