So option 2 is the one we have to go for: populate v2.job.cluster in the configuration yml and use “<%= ENV[‘OOD_CLUSTER_NAME’] -%>” to tell OOD what to use run a job (and set “cluster_id” value accordingly).
This means from any cluster we can decide where to run a job using the ENV variable and from any cluster we will query the right cluster (and get the same jobID) so the session will not disappear anymore! That’s great!!!
One last question, is this working in any OOD version or do we need v1.8?
We are on version 1.6.x and we are going to move to v1.8 anyway but I was wondering if we should apply this configuration (option 2) already now or wait and do it on the next release.
By the way, I guess we are done.
One last comment, I guess it will be better to change the title of the thread adding “in multi-cluster environment” (if possible), this may be more useful in case of anyone else having a similar situation in the future.
Thanks a lot for all your help!