[jira] [Commented] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created
[
https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819969#comment-16819969
]
Ignite TC Bot commented on IGNITE-9113:
---
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3617987buildTypeId=IgniteTests24Java8_RunAll]
> Allocate memory for a data region when first cache assigned to this region is
> created
> -
>
> Key: IGNITE-9113
> URL: https://issues.apache.org/jira/browse/IGNITE-9113
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.6
>Reporter: Valentin Kulichenko
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently we do not create any regions or allocate any offheap memory on
> client nodes unless it's explicitly configured. This is good behavior,
> however there is a usability issue caused by the fact that many users have
> the same config file for both server and clients. This can lead to unexpected
> excessive memory usage on client side and forces users to maintain two config
> files in most cases.
> Same issue is applied to server nodes that do not store any data (e.g. nodes
> running only services).
> It's better to allocate memory dynamically, when first cache assigned to a
> data region is created.
> More detailed discussion here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-regions-on-client-nodes-td32834.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created
[ https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812413#comment-16812413 ] Nikolay Izhikov commented on IGNITE-9113: - As discussed with [~avinogradov] I will do following changes: # Move `lazyMemoryAllocation` flag to the specifiŅ `DataRegion` # Add check of `CacheConfiguration#nodeFilter` when starting associated `DataRegion`. > Allocate memory for a data region when first cache assigned to this region is > created > - > > Key: IGNITE-9113 > URL: https://issues.apache.org/jira/browse/IGNITE-9113 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.6 >Reporter: Valentin Kulichenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently we do not create any regions or allocate any offheap memory on > client nodes unless it's explicitly configured. This is good behavior, > however there is a usability issue caused by the fact that many users have > the same config file for both server and clients. This can lead to unexpected > excessive memory usage on client side and forces users to maintain two config > files in most cases. > Same issue is applied to server nodes that do not store any data (e.g. nodes > running only services). > It's better to allocate memory dynamically, when first cache assigned to a > data region is created. > More detailed discussion here: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-regions-on-client-nodes-td32834.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created
[
https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812368#comment-16812368
]
Ignite TC Bot commented on IGNITE-9113:
---
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3538537buildTypeId=IgniteTests24Java8_RunAll]
> Allocate memory for a data region when first cache assigned to this region is
> created
> -
>
> Key: IGNITE-9113
> URL: https://issues.apache.org/jira/browse/IGNITE-9113
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.6
>Reporter: Valentin Kulichenko
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently we do not create any regions or allocate any offheap memory on
> client nodes unless it's explicitly configured. This is good behavior,
> however there is a usability issue caused by the fact that many users have
> the same config file for both server and clients. This can lead to unexpected
> excessive memory usage on client side and forces users to maintain two config
> files in most cases.
> Same issue is applied to server nodes that do not store any data (e.g. nodes
> running only services).
> It's better to allocate memory dynamically, when first cache assigned to a
> data region is created.
> More detailed discussion here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-regions-on-client-nodes-td32834.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created
[ https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768268#comment-16768268 ] Pavel Voronkin commented on IGNITE-9113: [~NIzhikov] i also observe that persistent(true) is ignored and region always created non-persistent. Seems like a bug we shouuld either fail on start or support persistent regions. > Allocate memory for a data region when first cache assigned to this region is > created > - > > Key: IGNITE-9113 > URL: https://issues.apache.org/jira/browse/IGNITE-9113 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.6 >Reporter: Valentin Kulichenko >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.8 > > > Currently we do not create any regions or allocate any offheap memory on > client nodes unless it's explicitly configured. This is good behavior, > however there is a usability issue caused by the fact that many users have > the same config file for both server and clients. This can lead to unexpected > excessive memory usage on client side and forces users to maintain two config > files in most cases. > Same issue is applied to server nodes that do not store any data (e.g. nodes > running only services). > It's better to allocate memory dynamically, when first cache assigned to a > data region is created. > More detailed discussion here: > http://apache-ignite-developers.2346864.n4.nabble.com/Data-regions-on-client-nodes-td32834.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
