Upgrade google.golang.org/grpc version #1374

Merged
dstepanov-yadro merged 1 commit from dstepanov-yadro/frostfs-node:feat/upgrade_grpc_version into master 2024-10-26 11:30:26 +00:00

For frostfs-cli tree ... and tree syncing it is ok to defer dial to first RPC call.
For tree cache use Healthcheck call to dial.

For `frostfs-cli tree ...` and tree syncing it is ok to defer dial to first RPC call. For tree cache use `Healthcheck` call to dial.
dstepanov-yadro force-pushed feat/upgrade_grpc_version from 22d95e4454 to e100d57662 2024-09-13 09:04:38 +00:00 Compare
fyrchik reviewed 2024-09-13 09:36:09 +00:00
@ -47,3 +40,1 @@
cc, err := grpc.DialContext(ctx, netAddr.URIAddr(), opts...)
cancel()
cc, err := grpc.NewClient(netAddr.URIAddr(), opts...)
Owner

It changes the behaviour if the service is unavailable.
Before we have failed after 2 seconds what is the timeout now?

It changes the behaviour if the service is unavailable. Before we have failed after 2 seconds what is the timeout now?
Author
Member

Fixed: user defined one

Fixed: user defined one
@ -111,0 +120,4 @@
ctx, cancel := context.WithTimeout(ctx, defaultClientConnectTimeout)
defer cancel()
// perform some request to check connection
if _, err := NewTreeServiceClient(cc).Healthcheck(ctx, req); err != nil {
Owner

Can we use only connection methods, like WaitForStateChange?

Can we use only connection methods, like `WaitForStateChange`?
Author
Member

I checked the option with WaitForStateChange, but it requires cc.Connect() call which is experimental. So I decided to perform regualr RPC request.

image

I checked the option with `WaitForStateChange`, but it requires `cc.Connect()` call which is experimental. So I decided to perform regualr RPC request. ![image](/attachments/1d88b92d-ef48-4de9-b9aa-12d20ddf9495)
dstepanov-yadro force-pushed feat/upgrade_grpc_version from e100d57662 to 4287223662 2024-09-13 10:24:18 +00:00 Compare
dstepanov-yadro requested review from storage-core-committers 2024-09-13 12:04:51 +00:00
dstepanov-yadro requested review from storage-core-developers 2024-09-13 12:04:52 +00:00
dstepanov-yadro force-pushed feat/upgrade_grpc_version from 4287223662 to 471b0435d3 2024-09-13 12:27:44 +00:00 Compare
acid-ant approved these changes 2024-09-13 12:31:52 +00:00
fyrchik approved these changes 2024-09-13 12:44:47 +00:00
Dismissed
Owner

The last commit has invalid # number
The last commit has invalid prefix (we use go.mod:)

The last commit has invalid # number The last commit has invalid prefix (we use `go.mod:`)
fyrchik dismissed fyrchik's review 2024-09-13 12:45:30 +00:00
dstepanov-yadro force-pushed feat/upgrade_grpc_version from 471b0435d3 to 89d0435b1d 2024-09-13 12:59:41 +00:00 Compare
Author
Member

The last commit has invalid # number
The last commit has invalid prefix (we use go.mod:)

Fixed

> The last commit has invalid # number > The last commit has invalid prefix (we use `go.mod:`) Fixed
fyrchik approved these changes 2024-09-13 13:00:31 +00:00
dstepanov-yadro merged commit 89d0435b1d into master 2024-09-13 13:09:33 +00:00
dstepanov-yadro deleted branch feat/upgrade_grpc_version 2024-09-13 13:10:03 +00:00
Sign in to join this conversation.
No reviewers
TrueCloudLab/storage-core-developers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#1374
No description provided.