How do I log into a specific node or cancel a job on a node I'm not logged into?

[StephenHey]

We've had to cancel some background jobs that were running longer than anticipated, but those jobs sometimes get put on a node that we're not logged into.   Depending on the severity, we have the whole team log in until they get the node it's running on (by checking all active transactions).

Is there any way to specify a node to log into as an admin or a way to see all jobs across all nodes?

[Slava Savitsky]

Consider using transaction quotas to cancel your background jobs proactively if they take too long to complete.

[StephenHey]

Thanks for the suggestion.   In this specific case, it would not have helped.   We had some bad data that was causing a script to loop.   We could tell pretty quickly the script was going back into a loop (within 5 minutes).   The normal transaction for these things is about 30 min to an hour.   So, transaction cancellations can help us if we don't notice and it runs for >1 hr.   But for when we're testing and watching, transaction quotas don't apply here.

[nairvine · Accepted solution]

Hi,

You can use certain add-on's like "edit cookie" and many more. The cookie contains the sys id if of the node. Hence when you log in for the first time into service now the sys id is stored in the cookie which is used later to log in to the same node again.

Just get the sys id of the node you want to log in and make use of edit cookie to update the cookie with the new sys id.

Log in again and you should be taken to the desired node.

Thanks,

Vineeth

[StephenHey]

Looks like the cookie named "glide_user_route" is the right cookie.   It has a value of glide.<sysID>.   I found the sys_ids of my nodes by going to the "My System Diagnostics" homepage and clicking on each one of the node links.   This brought me to an xml page and the sys_id is under "servlet.node_id"

[nikita_mironov]

Hi

Indeed yes. and sys_cluster_state list   gives a hint about the sys_ids. However, once I edited the cookie with the node I want to log in it still brings me back to the old one even if I logout and login back