[IGNITE-5215] Allow user to configure memory policy with maxSize lesser than default initialSize

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.1
• Component/s: cache
• Assignee: Alexey Goncharuk
• Reporter: Ivan Rakov
• Created: 15/May/17 11:28
• Updated: 23/May/17 11:52
• Resolved: 23/May/17 11:52

Description

Attempt to create memory policy with small maxSize ends with error:

Caused by: class org.apache.ignite.IgniteCheckedException: MemoryPolicy maxSize must not be smaller than initialSize [name=dfltMemPlc, initSize=268,4 MB, maxSize=209,7 MB]
	at org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.checkPolicySize(IgniteCacheDatabaseSharedManager.java:419)
	at org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.validateConfiguration(IgniteCacheDatabaseSharedManager.java:337)
	at org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:112)
	at org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:99)
	at org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:493)
	at org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.start0(GridCacheDatabaseSharedManager.java:436)
	at org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:644)
	at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
	... 29 more

This can be easily fixed by setting initialSize. Though, it would be better to don't oblige user to spend time on fixing it.

Issue Links

• links to: GitHub Pull Request #1938