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

OOME & full-gc's in aggregations heavy-load simulator test #9568

Closed
tombujok opened this issue Jan 2, 2017 · 0 comments · Fixed by #9581
Closed

OOME & full-gc's in aggregations heavy-load simulator test #9568

tombujok opened this issue Jan 2, 2017 · 0 comments · Fixed by #9581
Assignees
Labels
Milestone

Comments

@tombujok
Copy link
Contributor

tombujok commented Jan 2, 2017

No description provided.

@tombujok tombujok added this to the 3.8 milestone Jan 2, 2017
@tombujok tombujok self-assigned this Jan 2, 2017
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
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.
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants