Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Operations: Thor Slave Number reported incorrectly

Environment

From commit a941a83561e8b069d6252254b233209f08e2aca5

Description

My local dev environment is configured with four process-based Thor slaves. The attached screenshot is what I see in the Operations tab when I look at the Thor Cluster Processes. The "Slave Number" values should be ranked 1-4 rather than displaying only "4".

(I hope that the processes don't all think they are ID 4....)

Conclusion

None

Attachments

2

Activity

Show:

Kanghua Wang April 27, 2021 at 6:45 PM

I did reproduce the problem. Looks like the problem happens on the UI side. I just checked the legacy page and it works there. The data comes from the ProcessNumber inside WsTopology.TpMachineQuery response. The legacy page displays it using esp/eclwatch/ws_XSLT/machines.xslt.

To reproduce the problem, you may change the ThorCluster/@slavesPerNode to 4 inside default environment.xml.

Kanghua Wang April 27, 2021 at 2:58 PM

Thanks Dan. I will take a look.

Dan Camper April 27, 2021 at 1:43 PM

attached. I just confirmed that the problem is still showing in the latest 8.0.x build.

Note that this is a one-node cluster.

Kanghua Wang April 27, 2021 at 1:40 PM

 could you please share me your environment settings (environment.xml?) for me to reproduce the problem?

Gordon Smith April 23, 2021 at 8:57 AM

- When the address is IPs it seems to work fine (ECL Watch is just echoing the returned value)?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/14907

Roadmap

Not applicable

Affects versions

Created April 9, 2021 at 1:47 PM
Updated May 13, 2021 at 9:08 AM
Resolved April 30, 2021 at 11:51 AM

Flag notifications