[
https://issues.apache.org/jira/browse/IGNITE-21880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Myskov updated IGNITE-21880:
-----------------------------------
Description:
On Ignite startup, only the default data region is created.
In the provided configuration example, region1 and region2 will be ignored:
{code:java}
aimem {
defaultRegion {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
regions {
region1 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
region2 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
}
pageSize=16384
}
{code}
However, if regions are added after the cluster initialization, regions will be
created. This happens because VolatilePageMemoryStorageEngine.start() creates
default data regions and starts listening for configuration changes but ignores
data regions that already exist.
The following storage engines are affected:
* VolatilePageMemoryStorageEngine
* PersistentPageMemoryStorageEngine
* RocksDbStorageEngine
was:
On Ignite startup, only the default data region is created.
In the provided configuration example, region1 and region2 will be ignored:
{code:java}
aimem {
defaultRegion {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268 435 456
memoryAllocator {
type=unsafe
}
}
regions {
region1 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
region2 {
emptyPagesPoolSize=100
initSize=268435456
maxSize=268435456
memoryAllocator {
type=unsafe
}
}
}
pageSize=16384
}
{code}
However, if regions are added after the cluster initialization, regions will be
created. This happens because VolatilePageMemoryStorageEngine.start() creates
default data regions and starts listening for configuration changes but ignores
data regions that already exist.
The following storage engines are affected:
* VolatilePageMemoryStorageEngine
* PersistentPageMemoryStorageEngine
* RocksDbStorageEngine
> Data region definitions are ignored on Ignite startup
> -----------------------------------------------------
>
> Key: IGNITE-21880
> URL: https://issues.apache.org/jira/browse/IGNITE-21880
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Myskov
> Priority: Major
> Labels: ignite-3
>
> On Ignite startup, only the default data region is created.
> In the provided configuration example, region1 and region2 will be ignored:
> {code:java}
> aimem {
> defaultRegion {
> emptyPagesPoolSize=100
> initSize=268435456
> maxSize=268435456
> memoryAllocator {
> type=unsafe
> }
> }
> regions {
> region1 {
> emptyPagesPoolSize=100
> initSize=268435456
> maxSize=268435456
> memoryAllocator {
> type=unsafe
> }
> }
> region2 {
> emptyPagesPoolSize=100
> initSize=268435456
> maxSize=268435456
> memoryAllocator {
> type=unsafe
> }
> }
> }
> pageSize=16384
> }
> {code}
> However, if regions are added after the cluster initialization, regions will
> be created. This happens because VolatilePageMemoryStorageEngine.start()
> creates default data regions and starts listening for configuration changes
> but ignores data regions that already exist.
> The following storage engines are affected:
> * VolatilePageMemoryStorageEngine
> * PersistentPageMemoryStorageEngine
> * RocksDbStorageEngine
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
