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

Implement client side retry #3342

Closed
germa89 opened this issue Aug 8, 2024 · 0 comments · Fixed by #3343
Closed

Implement client side retry #3342

germa89 opened this issue Aug 8, 2024 · 0 comments · Fixed by #3343
Assignees
Labels
enhancement Improve any current implemented feature MAPDL Requires changes in MAPDL

Comments

@germa89
Copy link
Collaborator

germa89 commented Aug 8, 2024

After so much research on the infamous MAPDL gRPC issues #3313 I have seen that there is a pattern in some issues:

They all presents the grpc_status:14 in the debug_error_string. Full error:

debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-06-06T11:36:14.151348247+00:00", grpc_status:14, grpc_message:"Connection reset"}"

After researching about this grpc_status:14, I have found these references:

Hence I'm going to implement a retry mechanism, as close as possible to the gRPC interface. So we try to redo the call when this fail with this error message. I haven't decided the implementation yet.

I also believe this PR should help to fix #2479 because I'm using that model to fix it.

@germa89 germa89 added MAPDL Requires changes in MAPDL enhancement Improve any current implemented feature labels Aug 8, 2024
@germa89 germa89 self-assigned this Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve any current implemented feature MAPDL Requires changes in MAPDL
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant