Morph client always use the first endpoint on creation #304
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#304
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expected Behavior
The valid endpoint from the endpoints list should be used during creation
Current Behavior
cli.client, act, err = cli.newCli(ctx, cli.endpoints.list[0].Address)
When we have priority 1 for localhost and stopped neo-go on current node, always will receive error "could not create RPC client: WS client creation: dial tcp [::1]:40332: connect: connection refused". Endpoints from the list will not used.
Possible Solution
Steps to Reproduce (for bugs)
Stopping neo-go service
systemctl restart to-cm - will fail with error like "panic: neogo is not accessible: could not create RPC client: WS client creation: dial tcp [::1]:40332: connect: connection refused"
Context
Regression
Your Environment
uname -a
):при создании morphclient.New, всегда используется самый приоритетный endpoint, а не доступныйto Morph client always use the first endpoint on creation