Skip to content
This repository was 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

Description

@Phil2812

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions