In ignite2.13.0, the number of cache hit times and the number of cache miss times are incorrectly calculated.
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 1.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
The number of cache hit times and the number of cache miss times are incorrectly calculated. We are using ignite version 2.13.0.
When I use two non-existent keys (A and B) and call getAll to query the cache, the number of misses for key A increases by 1, but the number of misses for key B does not increase by 1.
I suspect that only the local call misses metric is + 1, but the remote one is not. This doesn't feel reasonable. Can you help?
Here's how to intercept via arthas:
Contributor guide
Research direction
Start by reproducing the reported getAll call with two nonexistent keys on Ignite 2.13.0 and compare local and remote hit/miss metrics, using the Arthas interception shown in the issue. Done means the miss count increases correctly for both keys and the corresponding hit/miss metrics are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100