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

Fixing region fail over issue for direct tcp calls #351

Merged
merged 8 commits into from Aug 31, 2020

Conversation

simplynaveen20
Copy link
Member

Currently for tcp network exception we are doing region failover, which is causing problem for some users where due to some intermittent network issue on BE nodes sdk is sending traffic for next 5 min to other available region.

This PR will limit the region failover only in case of http network failure.

Copy link
Member

@kushagraThapar kushagraThapar left a comment

Choose a reason for hiding this comment

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

Have some questions.

@kushagraThapar
Copy link
Member

Discussed the above comments with @simplynaveen20 offline. Good to go from my side.

Copy link
Contributor

@moderakh moderakh left a comment

Choose a reason for hiding this comment

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

I have more comments. still reviewing in a sev1.

Copy link
Contributor

@moderakh moderakh left a comment

Choose a reason for hiding this comment

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

looks good to me thanks Naveen.

Once scenario we haven't covered is when address resolution request to GW fails.
This will cause a region failover, but instead we should be more lenient toward GW address all and not fail over the region.

@simplynaveen20
Copy link
Member Author

looks good to me thanks Naveen.

Once scenario we haven't covered is when address resolution request to GW fails.
This will cause a region failover, but instead we should be more lenient toward GW address all and not fail over the region.

Yes as discussed , its not only address resolution, we need to think and change region fail over for all GW calls.

@moderakh moderakh merged commit fbca799 into master Aug 31, 2020
@moderakh moderakh deleted the users/nakumars/regionFailoverFix branch August 31, 2020 22:05
@@ -323,6 +323,9 @@

// 404: LSN in session token is higher
public static final int READ_SESSION_NOT_AVAILABLE = 1002;

// Client generated gateway network error substatus
public static final int GATEWAY_ENDPOINT_UNAVAILABLE = 10001;
Copy link
Contributor

Choose a reason for hiding this comment

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

we should use a substatus code which doesn't collide with the service side substatus codes otherwise the client-retry-policy will be confused.

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.

None yet

4 participants