We have set the maximum queued forked executions per node as 6. From where can i find the rest of the queued processes if any.
The number of "Queued" executions can be determined by monitoring JMX on your local runtime:
Specifically, refer to the section regarding "Execution Properties Status"
Hey Richard Patterson,
BTW having a deep dive into the executions folder of atom directory will I get the above information?
I suppose execution ID will be generated once the atom pickup the request, and for queued it doesn't create one unless its picked up.
Correct me here if any deviation in understandings.
Thats what I thought too.
Dell - Internal Use - Confidential
It may, but because, in the general case, processes are constantly being started and finishing, I would not recommend this approach. It would depend so much upon point-in-time and on the NFS directory. Instead, I would rely on the Java engine to provide this data
Absolutely +1 you should rely on JMX, not digging around in the file system. I'm going to modify this thread's correct answer accordingly.
Yes I too accept to rely on JMX, that was just my finding.
Thanks for sharing, I was just sharing the details. Its proper to go with JMX correct.
JMX will be giving the total number of queued executions right. And I think there is no way to find out which processes are in queue.
Correct: no way to view the specific processes in queue.
Retrieving data ...