-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
OOME & full-gc's in aggregations heavy-load simulator test #9568
Labels
Milestone
Comments
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Jan 4, 2017
The number of thread in the client executor is too big for full-table scan queries. If there's too many of them executed at once the client executor holds to much data and throws OOME eventually.
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Jan 4, 2017
The number of thread in the client executor is too big for full-table scan queries. If there's too many of them executed at once the client executor holds to much data and throws OOME eventually.
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Jan 4, 2017
The number of thread in the client executor is too big for full-table scan queries. If there's too many of them executed at once the client executor holds to much data and throws OOME eventually.
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Jan 5, 2017
The number of thread in the client executor is too big for full-table scan queries. If there's too many of them executed at once the client executor holds to much data and throws OOME eventually.
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Jan 9, 2017
The number of thread in the client executor is too big for full-table scan queries. If there's too many of them executed at once the client executor holds to much data and throws OOME eventually.
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Jan 10, 2017
The number of thread in the client executor is too big for full-table scan queries. If there's too many of them executed at once the client executor holds to much data and throws OOME eventually.
tombujok
added a commit
that referenced
this issue
Jan 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
No description provided.
The text was updated successfully, but these errors were encountered: