Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Announcements
QlikWorld, June 24-25, 2020. Free virtual event for DI and DA gurus. Register Today
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Employee
Employee

Re: NPRINTING ENGINE CORES ARE ASSIGNED TO ALREADY ABORTED TASKS

Thanks!



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Highlighted
Partner
Partner

Re: NPRINTING ENGINE CORES ARE ASSIGNED TO ALREADY ABORTED TASKS

Hi,

First of all, thank you all for all the suggestions and good advices on this topic. Everything was very helpfull to improve stability and performance in our reports.

However, unfortunatelly, R&D team has identify 3 issues/bugs affecting us (classified as OP-8457, OP-8394 and OP-8871). Let me paste R&D comments below: 

  1. OP-8457 (resolved on coming NPrinting November 2019)  -> RabbitMQ requests got lost because the engine was unable to send them back to the Scheduler (for some reason RabbitMQ broker closed the channel, hence the error you see in RabbitMQ logs).
  2. OP-8394 (I guess related to previous OP-8457) -> The fact that the 4 lost requests remained there even after an abort is known to me but is part of OP-8394 improvement that has not been planned yet. In any case essentially this does not produce any practical issue for the customer, just a theoretical very small performance degrade, probably difficult to measure, due to sub-optimal scheduler allocations (the scheduler thinks that there are four requests to resolve on that connection and so once in while, depending on starvation mechanisms, allocate one or more resolvers for them).
  3. OP-8871 -> qv.exe gets stuck sometimes. workaround is a script that could start every 20-30 minutes to clean up potentially stuck qv.exe

 

Let me clarify that (after many performance improvements) currently these issues only affect to certain documents.

If you guys have any additonal input on these JIRA issues, please let me know.

 

Regards,

Luis

View solution in original post

Highlighted
Support
Support

Re: NPRINTING ENGINE CORES ARE ASSIGNED TO ALREADY ABORTED TASKS

Hi @luis_pimentel 

Thank you for providing this very helpful update! It is truly appreciated!

Kind regards...

We are just 'like' you & like to be liked when we provide a helpful answer and or when you press the 'Solution Accepted' button if an answer provided resolves your question or issue... Cheers!