This repository has been archived by the owner on Dec 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Handle vshard error the same way as lua vshard router #77
Labels
Comments
Merged
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 26, 2024
* RouterCallImpl: retry on BucketResolve error * RouterCallImpl: do not retry on vshard error "TRANSFER_IS_IN_PROGRESS" * RouterCallImpl: remove misleading RetryOnCall
nurzhan-saktaganov
added a commit
that referenced
this issue
Sep 27, 2024
* RouterCallImpl: retry on BucketResolve error * RouterCallImpl: do not retry on vshard error "TRANSFER_IS_IN_PROGRESS" * RouterCallImpl: remove misleading RetryOnCall
nurzhan-saktaganov
added a commit
that referenced
this issue
Oct 1, 2024
* RouterCallImpl: retry on BucketResolve error * RouterCallImpl: do not retry on vshard error "TRANSFER_IS_IN_PROGRESS" * RouterCallImpl: remove misleading RetryOnCall
KaymeKaydex
pushed a commit
that referenced
this issue
Oct 1, 2024
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 7, 2024
* handle vshard error the same way as lua vshard router.
Solution e81ae86 |
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 8, 2024
* handle vshard error the same way as lua vshard router.
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 8, 2024
* handle vshard error the same way as lua vshard router.
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 18, 2024
* handle vshard error the same way as lua vshard router.
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 18, 2024
* handle vshard error the same way as lua vshard router.
Merged
1 task
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 26, 2024
* handle vshard error the same way as lua vshard router.
nurzhan-saktaganov
added a commit
that referenced
this issue
Nov 26, 2024
* handle vshard error the same way as lua vshard router.
KaymeKaydex
pushed a commit
that referenced
this issue
Dec 12, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How we handle now:
go-vshard-router/api.go
Lines 172 to 179 in e4e989d
Reference how we should handle:
https://github.com/tarantool/vshard/blob/b6fdbe950a2e4557f05b83bd8b846b126ec3724e/vshard/router/init.lua#L662
The text was updated successfully, but these errors were encountered: