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

[query-cache] Accessing a query-cache with a reasonable amount of data can result in a NPE #11675

Closed
vertex-github opened this issue Oct 26, 2017 · 4 comments

Comments

@vertex-github
Copy link

@vertex-github vertex-github commented Oct 26, 2017

We have a dataset of 600K rows, around 500 bytes per entry. Start server, start client. Access CQCache on client. Server starts loading the data from the MapStore (loading from Cassandra but I dont believe its Cassandra specific). On the client, the IMap can be retrieved from the HazelcastInstance and then a CQCache can be retrieved (which was configured via XML), but it's null. This seems to be a problem with larger datasets (perhaps some sort of timeout between client-server while the server is loading data, and then streaming the data back to the CQ Cache. Our CQ cache is using TruePredicate.INSTANCE - basically caching everything on the client, with an eviction size of Integer.MAX). If we remove most or all of the data in the Cassandra table and rerun the test, then everything works as expected, and the QueryCache reference obtained on the client is non null, thus no NPEs.

We expect the QueryCache object to be non-null on the client, and the method to obtain the cache should block waiting for the results of the query to execute. The method should wait for the server to load all the data through the MapStore. If that takes a few seconds or minutes it doesnt matter.

HZ 3.8.1

@mmedenjak mmedenjak added this to the 3.10 milestone Oct 27, 2017
@ahmetmircik
Copy link
Member

@ahmetmircik ahmetmircik commented Oct 31, 2017

@vertex-github I tried this by transferring nearly 1G data from cluster to query-cache and it worked fine. Is it possible to add an isolated reproducer here?

@taburet taburet added Team: Core and removed Team: Core labels Jan 22, 2018
@mmedenjak
Copy link
Contributor

@mmedenjak mmedenjak commented Feb 19, 2018

@vertex-github any update on this?

@vertex-github
Copy link
Author

@vertex-github vertex-github commented Feb 19, 2018

@ahmetmircik
Copy link
Member

@ahmetmircik ahmetmircik commented Mar 9, 2018

I didn't managed to reproduce this, closing for now. We can re-open this issue when we have a reproducer.

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
4 participants
You can’t perform that action at this time.