Qlikview Task not stop after publisher restart

[#1]

Hi All,

We are facing an issue that the task on server does not failed even we had restarted both the publisher and the server.

The task is set to be timeout after 60minutes of reloading, yet it does not stopped until we restart the publisher.

We had checked the document log and it shows just like we restarted the machine on days before.

Had anyone faced the same issue before, and get us some hint for the reason?

Thanks in advance.

Bevan

[ashfaq_haseeb]

Hi,

Did you restart machine itself?

What version of Qlik you are using?

Regards

ASHFAQ

[Peter_Cammaert]

What are the last lines in the Document Log when "...it shows just like we restarted the machine on days before."

Best,

Peter

[#4]

Hi Ashfaq,

We did an manual restart on the machine, specifically the publisher. After the restart of publisher we also restart the server.

We expect that it should get all the services down once we did the restart.

We are using version 11 SR3 at the moment.

Thanks
Bevan

[#5]

Hi Peter,

Here are the last few lines on the document log for those weird running task
"

7/10/2015 7:01:13 AM: 0090    FROM

7/10/2015 7:01:13 AM: 0091    [____________.qvd]

7/10/2015 7:01:13 AM: 0092    (qvd)

7/10/2015 7:01:13 AM: 0093    Where AccountingPeriod <= 2015006 and TXFC_RevaluationRecord = 1 and BridgingRecord = 1

7/10/2015 7:01:13 AM:         29 fields found: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, AA, BB, CC, 32,517,178 lines fetched
"

It looks like it was being killed from reloading while running on the server.

Thanks,
Bevan

[Peter_Cammaert · Accepted solution]

Your issue may be caused by one of two hidden engine operations:

• either your script is performing a big JOIN on those 32 million rows and the server eats all memory and thereby starts paging and slows down to a crawl (paging is to be avoided at all times)
• or these 32 million lines are being included in a very large synthetic key which again slows the engine down to a crawl. Is this LOAD close to the end of the script? If not, then it's probably not this one.

Either one can lock up the QVB process and the distribution service may be unable to kill the process in any normal way...

Peter

[Peter_Cammaert]

BTW did you try to run the reload on the server in QV Desktop instead of under QDS control? How long does it take to finish? If it seems to take "forever", open Task Manager and observe the memory usage view in the Performance tab.

Peter

[Bill_Britt]

Hi,

What are you using to say the task is still running? Is it because the QVB process is still running or is it the task in the QMC is showing that it is still running.  There is a big difference here. There are know issues with the task showing running and they are not in the older SR's.

Bill

[#9]

Hi Peter,

For the task, it normally runs only for 5 minutes. (Even other timing on the server or in QV Desktop)

But when the issue occurs, it takes as long as 2-3 hours without shutting down itself. (until we restart the publisher's distribution service)

We also set the task timeout to be 60 minutes, but looks like in this case, the setup does not work.

Thanks,

Bevan

[#10]

Hi Ben,

Thanks for the reply.

The task is running on QMC only. We checked and it is not reloading using QVB at that moment. (We assumed that while restart of the server, both of them should be stopped)

If that is a known issue, then we should have nothing to do unless an upgrade.

Bevan