Multiple WUQuery requests after visiting #/workunits

Description

Seems to be an issue with multiple batches of requests to WsWorkunits/WUQuery that occur after visiting #/workunits. Even after navigating away to a different route, the requests will continue to poll in a group of 50, by default (page size?).

To reproduce, visit #/workunits, then visit any other route. After about 30 seconds a second batch of requests (50) will be shown on the networking tab of devtools. This will repeat until the browser is refreshed (assuming not you haven't navigated back to #/workunits, in which case the process would begin again)

Conclusion

None

Attachments

Linked work items

relates to

HPCC-25270

WUQuery should return "isComplete" TRUE/FALSE

Activity

Show:

Gordon Smith
September 20, 2021 at 8:59 AM

This is supposed to be handled currently (so I would consider this a regression), FWIW this used to be a pain as it required an additional call to WUInfo (prior to ) but looks like I may not need that additional call now...

Richard Chapman
September 9, 2021 at 3:51 PM

If a workunit action is "compile" then it's not going to move beyond "compiled" and should not be refreshed...

Jeremy Clements
September 9, 2021 at 3:04 PM

I can't edit this issue I guess, but changing the title to something like you had suggested seems appropriate - mentioning the wu status. And you were correct, they were not completed but only compiled and were also roxie queries. This screenshot was when connected to the 160 cluster.

Gordon Smith
September 9, 2021 at 6:38 AM
(edited)

would you happen to have 50 WUs which are not "completed"? Currently ECL Watch will monitor any WU which it sees has not been completed - a screenshot of the network traffic and the workunits home page would be helpful.

Resize issue view side panel

Invalid

Pinned fields

Click on the next to a field label to start pinning.

Details

Components

Assignee

Gordon Smith

Reporter

Jeremy Clements

Priority

Major

Compatibility