openresty / openresty/lua-resty-lock
Is this lock only for caching to shared memory?
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 323
- Forks
- 81
- Avg merge
- 7h 41m
- Merged PRs (30d)
- 2
Description
For example, I use a worker-based cache. I get the data from redis and save it to the worker-level cache. I don't need a lock.For example, I get data from mysql and save it to the cache of the worker process. I don't need a lock.
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
Read the lua-resty-lock API and the repository description of ngx_lua shared memory dictionaries first. Determine whether the lock applies only to shared-memory caching or also to worker-local caches backed by Redis or MySQL, then document the supported use cases and clarify when no lock is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, mysql, redis
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100