openresty / openresty/lua-resty-redis
What will occur if not close redis?
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
Hello!
I have long transaction with redis: set some keys with testing ok/not_ok status; get keys and test results; then rpush, test result; then inner calcs; then another set and so on. After every operation I test success/error of this one. If error I return from function. If All OK I finish my transaction, exec() and close() redis. But in case of error and return I never call close()[keep_alive] redis. Is it correct? This redis connection is still open and allocate extra resource? Is there some appropriate technics for centralized closing redis in case of errors? something like: try {} catch {close_redis(); ....} ?
Thanks
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 file, test, or entry point. Read the Redis connection and keepalive behavior exposed by lua-resty-redis, then verify what happens when a transaction returns early after an error. Done means providing a documented, project-specific answer about connection cleanup and any supported centralized pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, redis
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100