Skip to content
This repository has been archived by the owner on Jul 2, 2021. It is now read-only.

When determining an FRLPc's crashed flag, only take into account jobs that are running on the correct port #116

Open
Phil2812 opened this issue Sep 5, 2018 · 0 comments

Comments

@Phil2812
Copy link
Collaborator

Phil2812 commented Sep 5, 2018

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]

public void updateFromFlashlist(FlashlistType flashlistType, JsonNode flashlistRow) {

[2] example_duplicate_jid_2018-09-05 18-23-26

@Phil2812 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant