Bug 105 – Job dependencies broken when job_suffix_alias is used

Bug 105 - Job dependencies broken when job_suffix_alias is used

Summary:

Job dependencies broken when job_suffix_alias is used

Status:	ASSIGNED

Product:	TORQUE
Component:	pbs_server
Version:	2.4.x
Platform:	PC Linux

Importance:	P5 major
Assigned To:	David Beer

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-12-20 02:23 MST by Dennis Stam
Modified:	2011-02-17 05:22 MST (History)
CC List:	3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Dennis Stam 2010-12-20 02:23:11 MST

Hello *,

Currently we see a strange behaviour when a user tries to submit a job with a
dependency. What happens is that the job is held forever when the
job_suffix_alias option is enable ( display_job_server = False ).

I also tested it on a cluster without the job_suffix_alias and the jobs there
will run as predicted.

Comment 1 Dennis Stam 2010-12-20 02:25:15 MST

We are using torque 2.4.11

Comment 2 Dennis Stam 2011-01-17 02:32:03 MST

Has someone looked at this issue?

Comment 3 David Beer 2011-01-24 13:35:51 MST

Dennis,

When you set these parameters, what was the status of your cluster? Setting
these parameters while you have queued jobs can cause TORQUE to not be able to
find jobs, since the older jobs weren't named the same way. TORQUE tries to
recover from this, but there are issues that it can't address. (That's why this
feature isn't documented on our website, we were trying to force people to ask
us questions about it before using it.)

David

Comment 4 Dennis Stam 2011-01-31 01:31:20 MST

David,

(In reply to comment #3)
> Dennis,
> 
> When you set these parameters, what was the status of your cluster? 

We started with a fresh installation of Torque 2.4.11

> Setting
> these parameters while you have queued jobs can cause TORQUE to not be able to
> find jobs, since the older jobs weren't named the same way. TORQUE tries to
> recover from this, but there are issues that it can't address. (That's why this
> feature isn't documented on our website, we were trying to force people to ask
> us questions about it before using it.)

We noticed the behaviour of the job_suffix_alias when we tested it. Perhaps
it's best to document this because it changes the behaviour of Torque when
there are jobs queued.

> 
> David

Regards,

Dennis

Comment 5 Bas van der Vlies 2011-02-17 05:22:14 MST

David. I just read your comment on Thia and i am bit confused. Most of times we
get questions sbout "can you test this feature of pbs_server?". We saw in the
changelog this new feature and it was exactly what i want, eg to switch to a
new server for example. If you want to prevent people from using it do not
mention it in the Changelog. 

So we done some testing and it seems to work the only thing that we did not
test was the dependencies.

Now we encounter a bug in this new feature and we get your comment. That is
inspiring for us and the people reporting problems ;-)

Is the answer dependencies do not work with this parameter and do not use this
parameter for your cluster. Or is this a bug that will be fixed? 


Regards