Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IMap Near Cache stats seem incorrect when caching null / non-existant values #10806

Closed
vertex-github opened this issue Jun 22, 2017 · 1 comment
Closed

Comments

@vertex-github
Copy link

@vertex-github vertex-github commented Jun 22, 2017

When using a client side NearCache, the cache stats seem incorrect when asking for a key that doesnt exist. As expected, on the first invocation of map.get() I see an increment in the miss count. On a second invocation with the same key for a non-existent mapping, I see the expected increment of hits but I also see an increment in misses

			testMap.put( 1, 42 );
			log.info( "testMap.get( 1 ): {}", testMap.get( 1 ) );
			log.info( "2a - cacheStats: {}", cacheStats ); // 0/1 (Expected Hits/Misses)

			log.info( "testMap.get( 1 ): {}", testMap.get( 1 ) );
			log.info( "2b - cacheStats: {}", cacheStats ); // 1/1

			log.info( "testMap.get( 1 ): {}", testMap.get( 1 ) );
			log.info( "2c - cacheStats: {}", cacheStats ); // 2/1

			log.info( "testMap.get( 2 ): {}", testMap.get( 2 ) );
			log.info( "2d - cacheStats: {}", cacheStats ); // 2/2

			log.info( "testMap.get( 2 ): {}", testMap.get( 2 ) ); //
			log.info( "2e - cacheStats: {}", cacheStats ); // 2/3 <<--- This is reported as 3/3
@ahmetmircik ahmetmircik added this to the 3.8.3 milestone Jun 22, 2017
@ahmetmircik ahmetmircik changed the title NearCache cacheStats seem incorrect when caching null / non-existant values IMap Near Cache stats seem incorrect when caching null / non-existant values Jun 22, 2017
@ahmetmircik
Copy link
Member

@ahmetmircik ahmetmircik commented Jun 23, 2017

fixed by #10807

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants