Two issues on the evcache
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
- The evcache.EVCacheClientPool.poolSize=2 setting will cause the memcached unstable.
If we set the poolSize as 2, the cache client becomes unstable. After several days/hours running and there are about 1M data in cache server, the get/set/delete operation become more and more slow. They needs more than tens seconds. - In default, the evcache writes so many logs with info level.
After we upgrade to the 4.131. 0, the evcache writes so many data, our log database is easy to be full. And it will slow our servers.
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 reproducing the reported behavior with evcache.EVCacheClientPool.poolSize=2 and inspect the logging behavior introduced after version 4.131.0. The report provides no file or test entry point, so first identify the relevant client-pool and logging code. Done means the cache operations remain responsive under the described load and excessive info-level logging is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, memcached
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100