openresty / openresty/lua-resty-redis
Add keepalive for redis client to make the connections reliable
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
In a case of a sudden connection loss Redis clients are not able detect network problems, and will be listening for Pub/Sub messages on a broken TCP connection for hours, making Pub/Sub unusable.
This is a common issue in redis clients and some redis clients like lettuce are already fixed . https://github.com/lettuce-io/lettuce-core/issues/1428
Refer to this issue for more info: https://github.com/redis/redis/issues/7855
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
Start by reading the Redis client's connection and Pub/Sub handling, then review the linked Lettuce and Redis issues for the expected keepalive behavior. Identify how broken TCP connections are detected and verify that Pub/Sub no longer remains blocked on a lost connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100