Change Job Assignment / Worker Tag on the 2nd node server

[sritatineni]

We have a 2 node architecture with Primary being the controlled and a worker node to balance the load. Currently we are planning to added another worker node to this and use it for long running jobs. To make it easy for users to tag them to appropriate workflows, we want to name the worker nodes differently than just keeping as worker.

Q: Can we change our existing node name from "Worker" highlighted in the screenshot below to something meaningful and don't effect any jobs that are already assigned to worker tag "Worker". We have 100's of workflows that are already tag to it and if changing the name fails the jobs are move it to Primary then, it is going to be a disaster. 

Any knowledge in this matter would be appreciated

Thanks,
Sri

[mbarone]

Sure can.  We do this ourselves now.  We only have 2 servers - the controller and a worker.  Our controller is pretty beefy so we just use the worker for specific jobs, like you were saying.  Our controller server is named, for example, "alteyrxservercontrol".  In the field you have highlighted, we did put that name in there, but also checked it to run unassigned jobs since that's really the "default" server if you will.

But for our worker node, we named it, for example "alteryxworker" and entered "alteryxworker" in your highlighted box and unchecked the "run unassigned jobs" box.  Only trick is that when you upload a workflow/app/add a schedule, you have to specifically pick that value in the "Worker Tag" drop down like this:

Here, for those jobs that only run on the worker, I'd pick that second one in the list.  That way it will only ever run on the worker node.