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.

Sign up for GitHub

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

Jump to bottom

Retry Policy for Jmx Connection #700

Closed
VictorCavichioli opened this issue Aug 21, 2024 · 0 comments
Closed

Retry Policy for Jmx Connection #700

VictorCavichioli opened this issue Aug 21, 2024 · 0 comments
Assignees
@SajidRiaz138
Labels
enhancement New feature or request PoC/Agent Tasks related to new generation of ecchronos as an agent

Comments

@VictorCavichioli
Copy link
Contributor

VictorCavichioli commented Aug 21, 2024 •
edited
Loading

Story Description:
We create the Jmx connections on the startup, if we success establish a connection with a node, we include this connection in the list and we mark this node as AVAILABLE on nodes_sync, else, we mark it as UNAVAILABLE, the main goal would be to define a retry policy for each UNAVAILABLE node, after the max retries, the node should be marked as UNREACHABLE.

Acceptance Criteria:

NA

Definition of Done:

Code working as described, test cases done, approved by maintainers.

Notes:

I did a patch for the a RetryPolicy on the sidecar application startup that could be used to do it, check #656

Related to #652
@VictorCavichioli VictorCavichioli added enhancement New feature or request PoC/Agent Tasks related to new generation of ecchronos as an agent labels Aug 21, 2024
@SajidRiaz138 SajidRiaz138 self-assigned this Aug 21, 2024
@VictorCavichioli VictorCavichioli mentioned this issue Aug 29, 2024
Closed
2 tasks
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 3, 2024
Retry Policy for Jmx Connection Ericsson#700
fb5b239
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 3, 2024
Retry Policy for Jmx Connection Ericsson#700
d564424
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 4, 2024
Retry Policy for Jmx Connection Ericsson#700
8122b56
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 5, 2024
Retry Policy for Jmx Connection Ericsson#700
e5073ff 
- Removed unused imports
- Increased checkstyle line length
- Fixed PMD warning
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 5, 2024
Retry Policy for Jmx Connection Ericsson#700
1eacaaa 
- 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.
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 5, 2024
Retry Policy for Jmx Connection Ericsson#700
37b1448 
- 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.
SajidRiaz138 pushed a commit to SajidRiaz138/ecchronos that referenced this issue Sep 10, 2024
Retry Policy for Jmx Connection Ericsson#700
c90ca1f 
- 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 pushed a commit that referenced this issue Sep 10, 2024
@SajidRiaz138
Retry Policy for Jmx Connection #700 (#710)
def5330 
- 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.

Co-authored-by: sajid riaz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SajidRiaz138 SajidRiaz138

Labels
enhancement New feature or request PoC/Agent Tasks related to new generation of ecchronos as an agent
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@VictorCavichioli @SajidRiaz138