chore: move retries to separate section and document ResourceExhausted #417
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tstirrat15
force-pushed
the
move-retries-to-resilience-section
branch
from
bcb7bc1 to
3f554c8
Compare
tstirrat15
force-pushed
the
move-retries-to-resilience-section
branch
from
3f554c8 to
d3e1c27
Compare
pages/spicedb/ops/resilience.mdx
Outdated
| * You may want to leave additional headroom to allow a new instance to come into service without exhausting connections, depending on your deployment model | ||
| and how instances roll. | ||
|
|
||
| #### CockroachDB fix |
pages/spicedb/ops/resilience.mdx
Outdated
|
|
||
| #### Postgres Fix | ||
|
|
||
| * Ensure that Postgres has enough available connections. |
There was a problem hiding this comment.
Would these bullets read better as h5s instead of bullet/subbullet? Eg:
##### Available Connections
Ensure that Postgres has enough available connections.
....
##### Connection Pooling
##### Connection Flags
Same also with Cockroach, below
There was a problem hiding this comment.
I might actually wanna use steps? https://nextra.site/docs/built-ins/steps
| @@ -6,52 +6,6 @@ import { Callout } from 'nextra/components' | |||
| This page will provide some practical recommendations for writing relationships to SpiceDB. | |||
| If you are interested in relationships as a concept, check out this [page](/spicedb/concepts/relationships). | |||
|
|
|||
There was a problem hiding this comment.
I think this is a good split!
Should there be a small reference to the resilience page here ? Something like: "If you want to focus on more reliable operations with your app, go here (with link to the resilience page)"
|
additional feedback:
|
tstirrat15
force-pushed
the
move-retries-to-resilience-section
branch
from
d3e1c27 to
00ba6ea
Compare
tstirrat15
force-pushed
the
move-retries-to-resilience-section
branch
from
00ba6ea to
2c8c76e
Compare
| @@ -1,5 +1,6 @@ | |||
| /// <reference types="next" /> | |||
| /// <reference types="next/image-types/global" /> | |||
| /// <reference types="next/navigation-types/compat/navigation" /> | |||
There was a problem hiding this comment.
This was an automatic change on running pnpm run dev; it should be fine.
| "yaml-loader": "^0.8.1" | ||
| }, | ||
| "packageManager": "pnpm@10.17.1" | ||
| "packageManager": "pnpm@10.24.0" |
There was a problem hiding this comment.
pnpm told me about this so I did it.
| ## Retries | ||
|
|
||
| When making requests to SpiceDB, it's important to implement proper retry logic to handle transient failures. | ||
| The [SpiceDB Client Libraries](/spicedb/getting-started/client-libraries) use gRPC[^1], |
There was a problem hiding this comment.
Footnote syntax now works!
tstirrat15
force-pushed
the
move-retries-to-resilience-section
branch
from
2c8c76e to
e559981
Compare
Fixes #414
Description
We got a few questions about what
ResourceExhaustedmeans. This splits out aResiliencepage and elaborates on whatResourceExhaustedmeans and what might cause it.Changes
See above.
Testing
Review.