Skip to content
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.

No way to manage memory usage #16

Open
cwoodwar6 opened this issue Aug 10, 2017 · 4 comments
Open

No way to manage memory usage #16

cwoodwar6 opened this issue Aug 10, 2017 · 4 comments

Comments

@cwoodwar6
Copy link

This is a follow up to #4 since the solution proposed there isn't ideal for us. Our keys are generally small and the values are big which matches OFFHEAP_VALUES best so OFFHEAP_TIERED isn't ideal for us. We also use a 2 day retention policy.

Our issue in particular is that we exceed our memory capacity and are being killed by the system.

Ideally, we'd like to see a way to set a max memory usage so that we aren't being killed by the system.

@dhaval2025
Copy link
Contributor

apologies for the delay, I was out on vacation. Let me make this change(among other things) this week (mostly by Thursday).

@dhaval2025
Copy link
Contributor

I pushed the change where you can now set the cacheMemoryMode using configs.

@wirehat
Copy link

wirehat commented Aug 28, 2017

@dhaval2025 Thanks. Though, that change does not seem to address the max memory usage issue that @cwoodwar6 is dealing with. Unless I'm missing something... ? offHeapStorageSize does not seem to make a difference.

@dhaval2025
Copy link
Contributor

@wirehat when you use cacheMemoryMode= OFFHEAP_VALUES, according to ignite documentaion offHeapStorageSize will not be respected. You need to change the mode to either
ONHEAP_TIERED or OFFHEAP_TIERED.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants