Hi Igniters,
I would discourage all Igniters from direct assigning issues to anyone
else. Of cource excepting the case it was directly discussed with asignee.
Any contributor should be able to assign issue to himself.
I left issue unassigned until Alex G would assign it.
Sincerely,
Dmitriy Pavlov
---------- Forwarded message ---------
From: Dmitriy Setrakyan (JIRA) <j...@apache.org>
Date: сб, 28 июл. 2018 г. в 0:42
Subject: [jira] [Assigned] (IGNITE-9113) Allocate memory for a data region
when first cache assigned to this region is created
To: <dpavlov....@gmail.com>
[
https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan reassigned IGNITE-9113:
-----------------------------------------
Assignee: Alexey Goncharuk
> 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: Alexey Goncharuk
> Priority: Major
> Fix For: 2.7
>
>
> 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)
