Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the logic for determining agent aliveness #11252

Closed
intr3p1d opened this issue Jul 15, 2024 · 0 comments
Closed

Improve the logic for determining agent aliveness #11252

intr3p1d opened this issue Jul 15, 2024 · 0 comments
Assignees
Milestone

Comments

@intr3p1d
Copy link
Contributor

The aliveness of an agent is now determined by the following logic:

If any of the conditions below are met, it should return true.

Determined from the AgentStatus object:

  • The agent status is RUNNING
  • The agent timestamp is within the Range.from ~ Range.to interval.

Determined from isActiveAgent:

  • There is a status in the Jvm Gc Dao (isActiveAgentByGcStat).
  • There is an Agent Ping (isActiveAgentByPing).

Previously, two conditions were connected with and. This resulted in unnecessary overhead.
Fix this first, and then improve isActiveAgent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant