openresty / openresty/lua-resty-redis
how to fast fail if redis server is not available
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
redis is used to cache data, if redis service is unavailable, how could app fast pass redis connect wait, and continue to query data from other system.
only set timeout contains connect time and execute time, cannot recognize connection time faliure.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by reviewing the connection and timeout handling exposed by lua-resty-redis and the ngx_lua cosocket API. Determine how connection failures are distinguished from command failures, then verify that the requested behavior lets the application stop waiting and continue with its other data source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, redis
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100