Refresh Identity Task running on UI servers upon selecting Enable Partitioning

*Hi,
we are at IIQ 8.5. We have a refresh task for correlated identities and seeing a weird behavior. We have selected Enable Partitioning flag in the task and no host defined. Upon execution, it picks up a task servers but we see each partition is running on UI Servers.

If we uncheck the flag, it simply runs on task server.

We have properly configured request and task service definition objects.

Could any one help us understand why UI servers are getting picked up?

Below are attached screenshots*

Hi @rabshrestha, welcome back!

At any point were those UI servers ever marked as task servers in the Admin Console?

If so, it could be a caching issue. In that case, restarting the application might clear the cache and resolve the behavior.

Hope it helps.

We did restart but still the same.

Only once we unselect the enable partitioning flag, it executes on task servers.

can you please double check or verify if the details are correct in request and task service definition objects. Can you please take a clean restart of tomcat like below?? and try??

rm -rf /opt/tomcat/work/*
rm -rf /opt/tomcat/temp/*

@rabshrestha
Could you kindly specify the configuration that you altered in order to designate the Task and UI Server?

this is current UI (wb*)* and **task (***ap*) configurations we have for IIQ Servers:

I read somewhere that UI servers are designated as RequestScheduler when we define them in ServiceDefinition: Request object and thus partitioning are carried out by such hosts. Is this true statement?

I just updated the request object with batch servers details. The task with partitioning is now running on batch servers.

Thank you all

1 Like