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

gRPC Unavailable error code MAY be returned for any RPC that the plugin cannot currently process due to a transient condition. #345

Open
jdef opened this issue Jan 16, 2019 · 1 comment
Milestone

Comments

@jdef
Copy link
Member

jdef commented Jan 16, 2019

Some use cases:

  1. plugin is still booting up and CO invoked a non-probe func before Probe returned OK.
  2. plugin is overwhelmed with requests and cannot process further requests until it catches up
  3. plugin is encountering transient network error conditions when communicating w/ the storage backend (e.g. read/write timeouts), and/or storage backend has indicated "too many requests" (so the plugin should try to shed load).

In response to receiving this error code a CO can choose to:

  1. give up
  2. back off and retry later
@saad-ali
Copy link
Member

saad-ali commented Mar 6, 2019

Seems reasonable considering we don't define behavior for this (so no backwards compat worries).

@saad-ali saad-ali added this to the v1.2 milestone Mar 6, 2019
@jdef jdef modified the milestones: v1.2, v1.3 Feb 24, 2020
@saad-ali saad-ali modified the milestones: v1.3, v1.4 Jun 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants