You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2021. It is now read-only.
When determining the crashed state of an FRLPc, the aggregator looks at all jobs in the jobTable of the FRLPc host's context [1]. However, it should only take into account the jobs with a jid that includes the FRLPc's hostname and port, not all the jobs running in the host's context.
Also, if multiple jobs with the same jid (same host, same port) exist, for example because the job crashed and remains in the table in Z-state [2], only the more recent job (based on startTime) should be looked at to determine the status.
(consider doing the same for FMMApplication, RU, BU)
The text was updated successfully, but these errors were encountered:
Phil2812
changed the title
When determining a FRLPc's crashed flag, only take into account jobs that are running on the correct port
When determining an FRLPc's crashed flag, only take into account jobs that are running on the correct port
Sep 7, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When determining the crashed state of an FRLPc, the aggregator looks at all jobs in the jobTable of the FRLPc host's context [1]. However, it should only take into account the jobs with a jid that includes the FRLPc's hostname and port, not all the jobs running in the host's context.
Also, if multiple jobs with the same jid (same host, same port) exist, for example because the job crashed and remains in the table in Z-state [2], only the more recent job (based on startTime) should be looked at to determine the status.
(consider doing the same for FMMApplication, RU, BU)
[1]
DAQAggregator/src/main/java/rcms/utilities/daqaggregator/data/FRLPc.java
Line 81 in 06d2fc6
[2]
The text was updated successfully, but these errors were encountered: