Re: Issues if -Djava.net.preferIPv4Stack=true is not set

[Dmitriy Setrakyan]

On Wed, Sep 27, 2017 at 5:08 AM, Yakov Zhdanov  wrote:

> hmm.. Dmitry, your suggestion may work if Ignite is started before any of
> network layer class is loaded/called. E.g. this will not work if Ignite is
> started inside application or web server.
>

Sure, let's do it anyway. In addition, can we make sure that we provide
users with this suggestion in case of the common network errors? If yes,
can we file the ticket for 2.3?


>
> --Yakov
>

Re: Persistence per memory policy configuration

[Denis Magda]

Vote for 1.

—
Denis

> On Sep 26, 2017, at 11:23 PM, Vladimir Ozerov  wrote:
> 
> Folks,
> 
> Let me summarize current naming ideas one more time:
> 
> 1) [StorageConfiguration - StorageRegionConfiguration]
> 2) [DurableMemoryConfiguration - DataRegionConfiguration]
> 3) [DurableMemoryConfiguration - DurableMemoryRegionConfiguration] - out of
> question, as "durable memory region" is too misleading.
> 
> My vote for p.1. Short, simple and intuitive.
> 
> Vladimir.
> 
> On Tue, Sep 26, 2017 at 10:16 PM, Dmitriy Setrakyan 
> wrote:
> 
>> On Tue, Sep 26, 2017 at 7:33 AM, Dmitry Pavlov 
>> wrote:
>> 
>>> Hi Dmitriy, thank you for reply. Do you agree Memory Policy already
>> became
>>> Ignite's term? We call this configuration now
>> MemoryPolicy(Configuration),
>>> can we call new configuration elments by their existings name? We can
>> avoid
>>> introduction of second Ignite's term in that case.
>>> 
>> 
>> The refactoring is about merging memory and persistence configuration under
>> the same umbrella. The term "MemoryPolicy" does not make sense anymore,
>> given that it now also includes persistent configuration as well.
>> 
>> 
>>> 
>>> вт, 26 сент. 2017 г. в 17:27, Dmitriy Setrakyan :
>>> 
 Dmitriy, we are not renaming classes, we are refactoring them. Prior to
 this design, it was impossible to set persistence configuration on
 per-cache basis. With this new design, users will be able to configure
>>> some
 caches to be in-memory only and others to be on disk.
 
 Given that we are already refactoring, it only makes sense to pick
>>> better,
 more appropriate names.
 
 D.
 
 On Tue, Sep 26, 2017 at 7:20 AM, Dmitry Pavlov 
 wrote:
 
> Vladimir, it is not clear for me, why we need to rename existing
> configuration classes. Could you explain? And if we can't get
>> consensus
> now, should we pospond solution?
> 
> My idea is that user needs this feature more than elegant names in
> configuration.
> 
> Moreover once MemoryPolicyConfiguration was introduced as Ignite term
>>> it
 is
> simpler to keep it as is, than create new terms.
> 
> Sincerely,
> Dmitriy Pavlov
> 
> вт, 26 сент. 2017 г. в 16:59, Vladimir Ozerov >> :
> 
>> I do not understand why we should delay with renames. Yes, it will
 cause
>> questions, so we will have to put additional efforts to docs and
> JavaDocs.
>> But the earlier we do that, the better.
>> 
>> On Tue, Sep 26, 2017 at 4:50 PM, Dmitry Pavlov <
>>> dpavlov@gmail.com>
>> wrote:
>> 
>>> Hi Igniters, sorry for late response. I didn't catch idea of
 renaming.
>>> PersistentStoreConfiguration is intuitive, and
> MemoryPolicyConfiguration
>> is
>>> intuitive also.
>>> 
>>> If we rename these classes now, it will bring more questions to
>>> user
>> list.
>>> Users may be confused by old and new names and by trying to match
>>> it.
>> More
>>> issues can came from XML configs that users already have.
>>> 
>>> Can we postpone the renaming? I suggest to finish 'persistence
>> per
> memory
>>> policy' task without renaming, and create separate JIRA issue for
>> creating
>>> future decision?
>>> 
>>> вт, 26 сент. 2017 г. в 15:25, Alexey Goncharuk <
>> alexey.goncha...@gmail.com
 :
>>> 
 I do not like DurableMemoryConfiguration, because it's quite
> confusing
>> -
>>> we
 configure in-memory caches using DurableMemory class, which
> immediately
 suggests that everything will be persisted. I am not sure if
>> this
 is
> a
 right wording choice for the documentation either. I would go
>>> with
 DataStoreConfiguration and DataRegionConfiguration.
 
 --AG
 
 2017-09-26 2:22 GMT+03:00 Dmitriy Setrakyan <
>>> dsetrak...@apache.org
> :
 
> Given that we already have a notion of CacheStore which comes
 from
>>> JCache
> spec, I think having other stores may get confusing. I like
> DurableMemoryConfiguration.
> 
> Other opinions?
> 
> D.
> 
> On Mon, Sep 25, 2017 at 12:24 PM, Vladimir Ozerov <
>>> voze...@gridgain.com>
> wrote:
> 
>> Dima, let's finalize the design first.
>> 
>> As I understand, we are happy with idea to merge
>> MemoryConfiguration
>> and PersistentStoreConfiguration
>> into something what I called DataConfiguration, and to
>> rename
>> MemoryPolicyConfiguration to DataRegionConfiguration.
>> 
>> The only outstanding qurestion is whether DataConfiguration
>>> is
 a
>> good
> name.
>> I am not very happy 

[jira] [Created] (IGNITE-6518) Smarter analysis of INSERT and MERGE statements at parsing stage

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-6518:
---

 Summary: Smarter analysis of INSERT and MERGE statements at 
parsing stage
 Key: IGNITE-6518
 URL: https://issues.apache.org/jira/browse/IGNITE-6518
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Reporter: Alexander Paschenko
 Fix For: 2.3


We could analyze INSERT and MERGE statements to detect that they don't specify 
data for key and/or value to notify users early that their query can't be 
executed within Ignite - prior to building plans and attempting to actually do 
anything.
(Note how we check that CREATE TABLE doesn't declare columns for key - logic 
here would be similar.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6517) .NET: DataStreamer DefaultPerNodeBufferSize, DefaultParallelOpsMultiplier

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6517:
--

 Summary: .NET: DataStreamer DefaultPerNodeBufferSize, 
DefaultParallelOpsMultiplier
 Key: IGNITE-6517
 URL: https://issues.apache.org/jira/browse/IGNITE-6517
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.3


Add default constants {{DefaultPerNodeBufferSize}} and 
{{DefaultParallelOpsMultiplier}} somewhere (interface does not allow them).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6516) .NET: PersistentStoreConfiguration.WriteThrottlingEnabled

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6516:
--

 Summary: .NET: PersistentStoreConfiguration.WriteThrottlingEnabled
 Key: IGNITE-6516
 URL: https://issues.apache.org/jira/browse/IGNITE-6516
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.3
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.3


Add {{PersistentStoreConfiguration.WriteThrottlingEnabled}} to .NET.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6515) .NET: Enable persistence on per-cache basis

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6515:
--

 Summary: .NET: Enable persistence on per-cache basis
 Key: IGNITE-6515
 URL: https://issues.apache.org/jira/browse/IGNITE-6515
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.3
Reporter: Pavel Tupitsyn
 Fix For: 2.3


Propagate new configuration to .NET: IGNITE-6030



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2754: IGNITE-5615 .NET: IgniteConfiguration.LocalEventL...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2754


---

[GitHub] ignite pull request #2765: GG-12821 IGNITE-4642: Added "enforceJoinOrder" an...

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/2765

GG-12821 IGNITE-4642: Added "enforceJoinOrder" and "lazy" flags to thick 
JDBC driver.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12821

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2765.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2765


commit 26daa57ca82254d68ac04a7b33223c6eb5ade0e4
Author: sboikov 
Date:   2016-11-10T08:17:29Z

Fixed javadoc.

commit 8b59f4e76138e08e80aa219c1a9cf0c3df6fdb4b
Author: Andrey V. Mashenkov 
Date:   2016-11-10T11:43:00Z

Backport commit of the following:

commit 612eb3daffe608995aac28eed019b3e6ef9d66d3
Author: Aleksei Scherbakov 
Date:   Fri Aug 19 13:28:39 2016 +0300

ignite-2795 Support 'copyOnRead' for SQL queries

commit b7499828c928e02e8e554f960f3754e4d08bfbe0
Author: Anton Vinogradov 
Date:   2016-11-10T13:10:21Z

IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails (DataStreamer data 
loss at unstable topology in !allowOverwrite mode fixed)

commit baa752660c6eddf27d15a812252b01b5872385de
Author: iveselovskiy 
Date:   2016-11-10T15:47:09Z

IGNITE-4208: Hadoop: Fixed a bug preventing normal secondary file system 
start. This closes #1228.

commit ef9d6cf9e334c35b03dfa42e4ce0680c85a693a4
Author: iveselovskiy 
Date:   2016-11-10T15:47:09Z

IGNITE-4208: Hadoop: Fixed a bug preventing normal secondary file system 
start. This closes #1228.

commit 884b281218d88c028daab25d35c14ee2b41be36e
Author: Pavel Tupitsyn 
Date:   2016-11-10T17:35:15Z

IGNITE-4186 .NET: Fix "Invalid session release request" exception in 
IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive

This closes #1227

commit eac5f0c05b85b620f979bd73d5043ae521b6f2f4
Author: Igor Sapego 
Date:   2016-11-10T18:13:13Z

IGNITE-4100: Improved README and DEVNOTES for CPP.

commit e159fdee0152a6df1bbf4dafc3d18a284e86a57e
Author: Alexey Kuznetsov 
Date:   2016-11-11T02:39:32Z

Fixed classnames.properties generation for ignite-hadoop module.

commit 5a4ebd5de8751dcf32a26c96bf4f39e43bcbb341
Author: Alexey Kuznetsov 
Date:   2016-11-11T02:49:41Z

Fixed classnames.properties generation for ignite-hadoop module.

commit 73a8fa8b635cce3b9d8dcad364a32d29f12d4398
Author: Alexey Kuznetsov 
Date:   2016-11-11T03:20:32Z

Fixed classnames.properties generation for ignite-hadoop module.

commit 53876d3f1b3e561702fc0cd8c6ddd078d6c7dce6
Author: Alexey Kuznetsov 
Date:   2016-11-11T03:26:09Z

Fixed classnames.properties generation for ignite-hadoop module.

commit f8aa957327312d76f90231b9bfe6d386d1d4ec37
Author: Alexey Kuznetsov 
Date:   2016-11-11T08:56:42Z

Reverted wrong commit.

commit c6921a311f437504a45a4667ddde85b14269ba57
Author: Alexey Kuznetsov 
Date:   2016-11-11T09:01:33Z

Fixed classnames.properties generation for ignite-hadoop module.

commit d69e26dd8d4fd9383a149c93c251911a8dd67528
Author: Pavel Tupitsyn 
Date:   2016-11-11T09:22:55Z

IGNITE-4126 .NET: Add IgniteConfiguration.SwapSpaceSpi

commit a70f0bac3ac2487b8ab58598ad921daa952b485f
Author: Andrey V. Mashenkov 
Date:   2016-11-11T10:03:40Z

IGNITE-4145: Fixes "No query result found for request" exception when 
running multiple queries concurrently. This closes #1218.

commit 8bb8bdda2e846dcc92a2fd449e64d7594b2700ed
Author: tledkov-gridgain 
Date:   2016-11-11T12:01:14Z

IGNITE-4053: Moved task error output from console to logger. This closes 
#1160.

commit 7128a395085b60e86436f807b4bdbca83627d41a
Author: sboikov 
Date:   2016-11-11T12:29:38Z

ignite-4154 Optimize amount of data stored in discovery history
Discovery history optimizations:
- remove discarded message for discovery pending messages
- remove duplicated data from TcpDiscoveryNodeAddedMessage.oldNodesDiscoData
- do not store unnecessary data in discovery EnsuredMessageHistory
- use special property for EnsuredMessageHistory size instead of 
IGNITE_DISCOVERY_HISTORY_SIZE
Affinity history optimizations:
- do not store calculated primary/backup maps in history
- try save the same assignments instance for caches with similar affinity
Exchange messages optimizations:
- do not send duplicated partition state maps for caches with similar 
affinity
- use zip compression for 

[GitHub] ignite pull request #2764: GG-12826 Backport fixes for NPE in GridDhtPartiti...

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/2764

GG-12826 Backport fixes for NPE in GridDhtPartitionDemander.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12826

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2764.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2764


commit 1c1a2f3e86c091bbbd2668db1cc7d72ff13d91ec
Author: dkarachentsev 
Date:   2017-04-19T10:27:49Z

Fix merge ignite-1.8.5-p1

commit ea3e625fe1269383d46d0be55adc85662a216792
Author: Alexander Belyak 
Date:   2017-04-19T10:29:01Z

IGNITE-4927 Use write behind coalescing from CacheConfiguration in 
GridCacheStoreManagerAdapter to configure actual cache store.

Signed-off-by: nikolay_tikhonov 

commit c8155fd8c2b12ca69fd5877fd21327ec746e1225
Author: Dmitriy Govorukhin 
Date:   2017-04-21T13:23:00Z

ignite-1.9.2 backport of ignite-4949

commit 8cae6dfd7ed000d06b37ad53f5d04aa3fd534d66
Author: Alexander Belyak 
Date:   2017-04-21T13:53:05Z

IGNITE-4927 Use write behind coalescing from CacheConfiguration in 
GridCacheStoreManagerAdapter to configure actual cache store.

Signed-off-by: nikolay_tikhonov 

commit 0d4d3cc36b17b9dcda8be02f9931ba01213f007f
Author: Andrey V. Mashenkov 
Date:   2017-04-21T16:40:08Z

Merge branch 'ignite-1.7.10' into ignite-1.9.2

# Conflicts:
#   
modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/datasource/DataSource.java
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/expiry/IgniteCacheExpiryPolicyAbstractTest.java

commit da3a1bd399832a8c012a5bd5ce1f07fe178cb8a6
Author: Andrey V. Mashenkov 
Date:   2017-04-21T16:41:16Z

Merge remote-tracking branch 'origin/ignite-1.9.2' into ignite-1.9.2

commit fde6d4427131f4b74fcdf88f1caae4f57d225a87
Author: Pavel Tupitsyn 
Date:   2017-04-20T16:39:45Z

IGNITE-5043 .NET: CacheConfiguration.WriteBehindCoalescing

(cherry picked from commit 217c6be)

commit 474add7c79eb5c57b2f88ca71ceb58ed3e5cb20b
Author: dkarachentsev 
Date:   2017-04-24T11:52:07Z

IGNITE-5043 .NET: CacheConfiguration.WriteBehindCoalescing

Fix merge.

commit a4c70f12305c15cbf15a6e5eb7c500f883a8b317
Author: agura 
Date:   2017-04-20T17:45:58Z

ignite-5041 NPE in deadlock detection fixed

commit a1fec4b0b3ddcc208154114e0bf8f202eb597fc9
Author: dkarachentsev 
Date:   2017-04-25T06:14:07Z

Fix index initialization.

commit d94172e7bb7ff4ebab422997e5c70f8cd03c0ae4
Author: agura 
Date:   2017-04-26T12:16:46Z

Redundant test removed

commit c64dc2426a70896116dbdffbf90faea5e52b991c
Author: Andrey V. Mashenkov 
Date:   2017-04-27T13:35:25Z

Revert IGNITE-4863 partially. Warn user if default log level was changed. 
As default log level value (DEBUG) can cause performance issues.

commit f9ecacc625b458539775e6550bd9b7613ed38f21
Author: dkarachentsev 
Date:   2017-04-28T08:46:23Z

IGNITE-5077 - Support service security permissions

backport from master
(cherry picked from commit 6236b5f)

commit 91c899b909383c78b78b9bf0c8f233b8c75ef29e
Author: Valentin Kulichenko 
Date:   2017-04-28T12:48:57Z

IGNITE-5081 - Removed redundant duplication of permissions in 
SecurityPermissionSetBuilder

commit b48a26b9b1e97fb8eb52c2a2f36005770922ac3d
Author: Valentin Kulichenko 
Date:   2017-04-28T12:53:33Z

IGNITE-5080 - Fixes in SecurityBasicPermissionSet

commit f66c23cbb9a6f2c923ebf75c58f00afaf1c0b5f3
Author: Evgenii Zhuravlev 
Date:   2017-05-03T14:47:45Z

IGNITE-4939 Receive event before cache initialized fix

commit 45b4d6316145d0b4b46713409f5e8fbe55ff4c41
Author: Evgenii Zhuravlev 
Date:   2017-05-04T09:11:37Z

IGNITE-4939 Receive event before cache initialized fix

commit 075bcfca0ea22633be13cd02647e359ad6fdca16
Author: Andrey V. Mashenkov 
Date:   2017-05-04T09:21:04Z

Fix flacky service deployment tests.

commit 25c06b50d46937cb39534cdf4147b862217289a2
Author: rfqu 
Date:   2017-05-02T16:46:44Z

ignite-4220 Support statements for JDBC and Cassandra store

commit 7d8d672295e6554a82f63a16b73c330ca6050618
Author: Andrey V. Mashenkov 
Date:   2017-05-05T11:29:59Z

IGNITE-4992: Fix 

[jira] [Created] (IGNITE-6514) Hide QueryEntity.notNullFields from public API

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6514:


 Summary: Hide QueryEntity.notNullFields from public API
 Key: IGNITE-6514
 URL: https://issues.apache.org/jira/browse/IGNITE-6514
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.3


The QueryEntity class already became too overloaded, so we need to hide this 
from public API for now until a better approach is developed



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6513) Add ability manage version for WAL serializer via system properties

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-6513:
--

 Summary: Add ability manage version for WAL serializer via system 
properties
 Key: IGNITE-6513
 URL: https://issues.apache.org/jira/browse/IGNITE-6513
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.1, 2.0, 2.2, 2.3
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin
 Fix For: 2.4






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Per-entry overhead - some questions

[Alexey Goncharuk]

Yes, Basically, it is a pair of backing arrays of key and value as
BinaryObjects, associated GridCacheVersion and expireTime (I may have
forgotten something, but this something should not be too large). You can
take a closer look at WriteRowHandler class which runs the row store to a
data page to dig into the key-value row layout.

2017-09-27 17:45 GMT+03:00 endianignite :

> Thanks Alexey, understood.
>
> What is the format of the object that is stored off-heap, is it a
> BinaryObjectOffheapImpl (or a parent class/interface) or something else?
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Per-entry overhead - some questions

[endianignite]

Thanks Alexey, understood.

What is the format of the object that is stored off-heap, is it a
BinaryObjectOffheapImpl (or a parent class/interface) or something else?





--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-6512) Need a possibility to start caches without discarding their 'restarting' state

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-6512:
-

 Summary: Need a possibility to start caches without discarding 
their 'restarting' state
 Key: IGNITE-6512
 URL: https://issues.apache.org/jira/browse/IGNITE-6512
 Project: Ignite
  Issue Type: Improvement
Reporter: Eduard Shangareev


Now we always discard restarting state on cache while it is starting.
But sometimes we need extra steps before making caches available from public 
API.

So, I suggest adding a new method which would be called when we want to make 
caches available for public API clients.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2763: IGNITE-5713

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/2763

IGNITE-5713



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5713

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2763.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2763


commit 34ec1d24d67f7429693477d96fa9293393b8ed97
Author: devozerov 
Date:   2017-09-27T12:41:48Z

IGNITE-5713: Removed dependency in ignite-indexing.




---

[jira] [Created] (IGNITE-6511) ODBC: SQLGetDiagRec doesn't follow specification when buffer size is too small

[Sergey Kalashnikov (JIRA)]

Sergey Kalashnikov created IGNITE-6511:
--

 Summary: ODBC: SQLGetDiagRec doesn't follow specification when 
buffer size is too small
 Key: IGNITE-6511
 URL: https://issues.apache.org/jira/browse/IGNITE-6511
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Reporter: Sergey Kalashnikov


When buffer size provided for error message is not big enough to hold the 
entire error message, the function {noformat}SqlGetDiagRec{noformat} returns 
wrong resulting string length (-4) and wrong result code 
({noformat}SQL_SUCCESS{noformat} instead of 
{noformat}SQL_SUCCESS_WITH_INFO{noformat}).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

[Yakov Zhdanov]

hmm.. Dmitry, your suggestion may work if Ignite is started before any of
network layer class is loaded/called. E.g. this will not work if Ignite is
started inside application or web server.

--Yakov

Re: Per-entry overhead - some questions

[Alexey Goncharuk]

Hello Mike,

With the new Ignite 2.0 architecture, GridCacheMapEntry does not add any
overhead because the data is stored off-heap (unless you have on-heap cache
enabled) and the GridCacheMapEntry is created only temporarily.

Anyways, answering your questions:
1) The reference to GridCacheContext in all entries of the same cache is
the same. Theoretically, it may be possible to pass this reference to every
single method on GridCacheMapEntry, however, there might be tricky places
when the context is not around in local variables, so this task may require
quite a bit of refactoring.
2) GridCacheEntryExtras usage pattern depends on whether this is a
transactional or atomic cache. Back in Ignite 1.x I would say that this
field is null most of the time, but in Ignite 2.x, again, it is very likely
that extras are not null when the entry is used.

--AG

2017-09-26 18:19 GMT+03:00 endianignite :

> Hi Igniters,
>
> I have been looking in to the per-entry overhead for Ignite cache entries
> and have a couple of questions.
>
> 1. Does each GridCacheMapEntry require a reference to GridCacheContext ?>
> or could this field be removed/optimized in some way? Is the
> GridCacheContext instance the same for every entry in a particular cache?
>
> 2. Is the GridCacheMapEntry extras field (a reference to
> GridCacheEntryExtras) often/usually null? If so, could we find a clever way
> to remove this field and save a further 8 bytes?
>
> The reason for asking is that I am looking at a use-case where object sizes
> are very small, but the number of objects is very large, and therefore the
> overhead is substantial.  In this particular case, the overhead is 70-75%
> of
> the consumed memory.
>
> I look forward to hearing your thoughts.
>
> Regards
> Mike
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-6510) SQL: document CACHE_NAME, KEY_TYPE and VALUE_TABLE options for CREATE TABLE

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6510:
---

 Summary: SQL: document CACHE_NAME, KEY_TYPE and VALUE_TABLE 
options for CREATE TABLE
 Key: IGNITE-6510
 URL: https://issues.apache.org/jira/browse/IGNITE-6510
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.3






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2740: IGNITE-6242

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2740


---

[jira] [Created] (IGNITE-6509) SQL: Add NOT NULL support to QueryEntity API

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6509:
---

 Summary: SQL: Add NOT NULL support to QueryEntity API
 Key: IGNITE-6509
 URL: https://issues.apache.org/jira/browse/IGNITE-6509
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.1
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.3






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Persistence per memory policy configuration

[Yakov Zhdanov]

I like Vladimir's suggestion - StorageConfiguration -
StorageRegionConfiguration

--Yakov

[GitHub] ignite pull request #2753: ignite-5714 updateExplicitVersion for detached en...

[voipp]

Github user voipp closed the pull request at:

https://github.com/apache/ignite/pull/2753


---

[GitHub] ignite pull request #2526: IGNITE-6184 Add checkClusterState() call to destr...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2526


---

[GitHub] ignite pull request #2739: IGNITE-6360: NPE occurs if object with null index...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2739


---

[GitHub] ignite pull request #2760: IGNITE-6331

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/2760


---

[GitHub] ignite pull request #2755: IGNITE-5730 .NET: Fix ignite.jni.dll temp dir rac...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2755


---

[jira] [Created] (IGNITE-6508) Web console: chart has no labels on X axis in some cases

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-6508:
--

 Summary: Web console: chart has no labels on X axis in some cases
 Key: IGNITE-6508
 URL: https://issues.apache.org/jira/browse/IGNITE-6508
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Minor


I'm noticed that in some cases X-axis has no lables



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2762: gnite-gg-pitr-2.1.5 merge to ignite-PITR (master)

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

https://github.com/apache/ignite/pull/2762

gnite-gg-pitr-2.1.5 merge to ignite-PITR (master)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-PITR

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2762.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2762


commit 0b0556528098f2cb326c4d5c988f4cccd6dbe164
Author: Dmitriy Govorukhin 
Date:   2017-09-26T14:25:31Z

ignite-gg-pitr-2.1.5 merge to PITR (master)

commit fd0e6025c8a744280d7da3256a89f644abd8f48b
Author: EdShangGG 
Date:   2017-09-26T15:31:26Z

ignite-gg-pitr-2.1.5 merge to PITR (master)




---

[GitHub] ignite pull request #2756: ignite-gg-pitr-2.1.5 merge to PITR (master)

[DmitriyGovorukhin]

Github user DmitriyGovorukhin closed the pull request at:

https://github.com/apache/ignite/pull/2756


---

[GitHub] ignite pull request #2761: Ignite 2.2

[taoyuyu]

GitHub user taoyuyu opened a pull request:

https://github.com/apache/ignite/pull/2761

Ignite 2.2



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/ignite ignite-2.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2761.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2761


commit 8ad996802c8a9898fd22fdf74bd1c97120f985ed
Author: Ivan Rakov 
Date:   2017-08-29T10:24:20Z

IGNITE-6204 Backport optimizations of checkpointing algorithm into 2.2

(cherry picked from commit 737874f)

commit f2fec666ac8f19107b65f7317663832d78a078e9
Author: Pavel Tupitsyn 
Date:   2017-08-29T15:35:49Z

IGNITE-6204 Backport optimizations of checkpointing algorithm into 2.2 
(hotfix)

(cherry picked from commit abb675f)

commit 773f31e98d51583420d16892c3ddefe0e39a8974
Author: Igor Seliverstov 
Date:   2017-09-01T09:48:38Z

IGNITE-6182 Change default max memory size from 80% to 20%

(cherry picked from commit d51171f)

commit 792b57d80c08339ad4a92744c8ad3a1b16cbebbf
Author: devozerov 
Date:   2017-09-04T14:41:30Z

IGNITE-6182: Improved message.

(cherry picked from commit 1fb2fe0)

commit 42c33682765e631fbf1d8fc3cf237c3781866e6d
Author: oleg-ostanin 
Date:   2017-09-05T10:50:55Z

IGNITE-5817 deleted deploy-ignite sources profile

(cherry picked from commit 94641a9)

commit 5747ce6b36f10b30d2142b9d90dad8e3049e8f74
Author: Anton Vinogradov 
Date:   2017-09-08T14:24:21Z

Release Notes 2.2

(cherry picked from commit 94709fb)




---

[GitHub] ignite pull request #2733: IGNITE-6468: Added tests. Fixed some issues

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2733


---

[GitHub] ignite pull request #2633: IGNITE-6331

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/2633


---

[GitHub] ignite pull request #2760: IGNITE-6331

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/2760

IGNITE-6331



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6331-more

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2760.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2760


commit ef8dec45d777d3ca6443bf9ca021fa9fa7bfeab2
Author: devozerov 
Date:   2017-09-11T11:02:56Z

IGNITE-6331

commit 99f32209ffebff9adaf9432988e844610755c357
Author: devozerov 
Date:   2017-09-11T11:25:02Z

Cleanup.

commit 136517305225caef3ff65f450e89f23985956da5
Author: devozerov 
Date:   2017-09-11T11:28:07Z

More cleanup.

commit 4441c401ffc488c487df75188a80909ecc853f69
Author: devozerov 
Date:   2017-09-11T11:36:02Z

More cleanup.

commit 59b37cdfcd1355248feee1f0fcc168f7577d0ed5
Author: devozerov 
Date:   2017-09-11T11:37:14Z

Cleanup.

commit 6dc79df430c2c4ff2e4a3319034379ee0da8f6b5
Author: devozerov 
Date:   2017-09-11T11:38:54Z

More cleanup.

commit e6d23c4e0e66329b1fb2a0aa6bb4b34a1ce680f7
Author: devozerov 
Date:   2017-09-11T11:39:59Z

WIP,

commit 52e128f91655596647b9479e7f19badb9c13d6f8
Author: devozerov 
Date:   2017-09-11T11:40:58Z

WIP,

commit 47be497f5aa296c13e48094a5dd4b3ea421e25a5
Author: devozerov 
Date:   2017-09-11T12:26:38Z

Fixing compilation.

commit 33935f1dae4aad37d9026a1cd86569c13bbc395b
Author: devozerov 
Date:   2017-09-11T13:50:02Z

Merge branch 'master' into ignite-6331

commit 8f3806cbf17e8e9ab5dbb8ec50ed965eca1d5458
Author: devozerov 
Date:   2017-09-11T13:51:56Z

Merge branch 'ignite-6331' into ignite-6331-more

commit 8d9ee5c8e4952ec33a721e1e08a3a92974790bbd
Author: devozerov 
Date:   2017-09-27T06:31:00Z

Merge branch 'master' into ignite-6331-more




---

Re: Persistence per memory policy configuration

[Vladimir Ozerov]

Folks,

Let me summarize current naming ideas one more time:

1) [StorageConfiguration - StorageRegionConfiguration]
2) [DurableMemoryConfiguration - DataRegionConfiguration]
3) [DurableMemoryConfiguration - DurableMemoryRegionConfiguration] - out of
question, as "durable memory region" is too misleading.

My vote for p.1. Short, simple and intuitive.

Vladimir.

On Tue, Sep 26, 2017 at 10:16 PM, Dmitriy Setrakyan 
wrote:

> On Tue, Sep 26, 2017 at 7:33 AM, Dmitry Pavlov 
> wrote:
>
> > Hi Dmitriy, thank you for reply. Do you agree Memory Policy already
> became
> > Ignite's term? We call this configuration now
> MemoryPolicy(Configuration),
> > can we call new configuration elments by their existings name? We can
> avoid
> > introduction of second Ignite's term in that case.
> >
>
> The refactoring is about merging memory and persistence configuration under
> the same umbrella. The term "MemoryPolicy" does not make sense anymore,
> given that it now also includes persistent configuration as well.
>
>
> >
> > вт, 26 сент. 2017 г. в 17:27, Dmitriy Setrakyan :
> >
> > > Dmitriy, we are not renaming classes, we are refactoring them. Prior to
> > > this design, it was impossible to set persistence configuration on
> > > per-cache basis. With this new design, users will be able to configure
> > some
> > > caches to be in-memory only and others to be on disk.
> > >
> > > Given that we are already refactoring, it only makes sense to pick
> > better,
> > > more appropriate names.
> > >
> > > D.
> > >
> > > On Tue, Sep 26, 2017 at 7:20 AM, Dmitry Pavlov 
> > > wrote:
> > >
> > > > Vladimir, it is not clear for me, why we need to rename existing
> > > > configuration classes. Could you explain? And if we can't get
> consensus
> > > > now, should we pospond solution?
> > > >
> > > > My idea is that user needs this feature more than elegant names in
> > > > configuration.
> > > >
> > > > Moreover once MemoryPolicyConfiguration was introduced as Ignite term
> > it
> > > is
> > > > simpler to keep it as is, than create new terms.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > вт, 26 сент. 2017 г. в 16:59, Vladimir Ozerov  >:
> > > >
> > > > > I do not understand why we should delay with renames. Yes, it will
> > > cause
> > > > > questions, so we will have to put additional efforts to docs and
> > > > JavaDocs.
> > > > > But the earlier we do that, the better.
> > > > >
> > > > > On Tue, Sep 26, 2017 at 4:50 PM, Dmitry Pavlov <
> > dpavlov@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Igniters, sorry for late response. I didn't catch idea of
> > > renaming.
> > > > > > PersistentStoreConfiguration is intuitive, and
> > > > MemoryPolicyConfiguration
> > > > > is
> > > > > > intuitive also.
> > > > > >
> > > > > > If we rename these classes now, it will bring more questions to
> > user
> > > > > list.
> > > > > > Users may be confused by old and new names and by trying to match
> > it.
> > > > > More
> > > > > > issues can came from XML configs that users already have.
> > > > > >
> > > > > > Can we postpone the renaming? I suggest to finish 'persistence
> per
> > > > memory
> > > > > > policy' task without renaming, and create separate JIRA issue for
> > > > > creating
> > > > > > future decision?
> > > > > >
> > > > > > вт, 26 сент. 2017 г. в 15:25, Alexey Goncharuk <
> > > > > alexey.goncha...@gmail.com
> > > > > > >:
> > > > > >
> > > > > > > I do not like DurableMemoryConfiguration, because it's quite
> > > > confusing
> > > > > -
> > > > > > we
> > > > > > > configure in-memory caches using DurableMemory class, which
> > > > immediately
> > > > > > > suggests that everything will be persisted. I am not sure if
> this
> > > is
> > > > a
> > > > > > > right wording choice for the documentation either. I would go
> > with
> > > > > > > DataStoreConfiguration and DataRegionConfiguration.
> > > > > > >
> > > > > > > --AG
> > > > > > >
> > > > > > > 2017-09-26 2:22 GMT+03:00 Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >:
> > > > > > >
> > > > > > > > Given that we already have a notion of CacheStore which comes
> > > from
> > > > > > JCache
> > > > > > > > spec, I think having other stores may get confusing. I like
> > > > > > > > DurableMemoryConfiguration.
> > > > > > > >
> > > > > > > > Other opinions?
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Sep 25, 2017 at 12:24 PM, Vladimir Ozerov <
> > > > > > voze...@gridgain.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Dima, let's finalize the design first.
> > > > > > > > >
> > > > > > > > > As I understand, we are happy with idea to merge
> > > > > MemoryConfiguration
> > > > > > > > > and PersistentStoreConfiguration
> > > > > > > > > into something what I called DataConfiguration, and to
> rename
> > > > > > > > > MemoryPolicyConfiguration to DataRegionConfiguration.
> > > >