openresty / openresty/lua-resty-redis
Redis close or keepalive
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
Hi There,
We are using the module for a long time and I think we have a mem leak or something regarding the connections.
I would like to know the following:
- Do we need to close redis connections? What happen if we are not closing the connection?
- When to use close and when to use keepalive? Do we need to use keepalive all the time?
- If we have timeout in connection do we still need to close or use keepalive on the object?
- If we get timeout when making a command, what we need to do? Is there a chance for mem leak?
Basically I want to understand what may cause mem leaks and what action to take under several circumstances.
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, so first review the repository's Redis connection and keepalive documentation and identify the relevant lifecycle APIs. Clarify the expected documentation scope around closing connections, keepalive, timeouts, and possible memory leaks; done means providing authoritative answers for each listed scenario.
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
- 25/100