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

Retry Policy for Jmx Connection #700 #710

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

SajidRiaz138
Copy link
Contributor

No description provided.

@SajidRiaz138 SajidRiaz138 marked this pull request as ready for review September 5, 2024 17:39
@SajidRiaz138 SajidRiaz138 requested a review from a team as a code owner September 5, 2024 17:39
Copy link
Collaborator

@jwaeab jwaeab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also:

  • Test negatives; no config set, misspelling eetc
  • Add test cases with other values; start delay longer than max, initial longer than fixed etc

- Retry Policy for jmx connection
- Read all nodes statuses from nodes_sync table
- Filter out all node with unavailable status
- Retry to attempt jmx connection for unavailable nodes
- If connection successful add connection and change
status to available in table.
- If connection failed after given retry attempts, change
status to unreachable in table.
- This is schedule service that would execute after given
fix delay. By default it would run after every 24 hour and
scan the table.
@tommystendahl tommystendahl merged commit def5330 into Ericsson:agent/master Sep 10, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants