Re: Page Memory behavior with default memory policy

Hello Denis, There is a small piece of documentation in *MemoryConfiguration *class, although I think it should be moved to *MemoryPolicyConfiguration *and detailed a lot. I'm going to write some documentation soon about validation rules that are applied to memory policies configuration (there

[GitHub] ignite pull request #1806: Ignite 4955

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1806 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-4996) Queries: show Node selection modal in case if user execute SCAN on local cache

Pavel Konstantinov created IGNITE-4996: -- Summary: Queries: show Node selection modal in case if user execute SCAN on local cache Key: IGNITE-4996 URL: https://issues.apache.org/jira/browse/IGNITE-4996

[GitHub] ignite pull request #1808: IGNITE-4587: Found bug - CacheVersionIO is change...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1808 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-5001) .NET: Tests cleanup

Pavel Tupitsyn created IGNITE-5001: -- Summary: .NET: Tests cleanup Key: IGNITE-5001 URL: https://issues.apache.org/jira/browse/IGNITE-5001 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5004) GridCacheWriteBegindStore - remove StatefulValue

Alexander Belyak created IGNITE-5004: Summary: GridCacheWriteBegindStore - remove StatefulValue Key: IGNITE-5004 URL: https://issues.apache.org/jira/browse/IGNITE-5004 Project: Ignite

[GitHub] ignite pull request #1590: ignite-4680

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1590 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #1811: Ignite 5000

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/1811 Ignite 5000 Module ignite-math renamed to ignite-ml and examples moved to the separate folder/profile. You can merge this pull request into a Git repository by running: $ git pull

cache query operations

Hi, Igniters! When one fires query like this : ignite().cache(null ).query(...) The query would be executed against the schema. I wonder, how the schema is synchronized with cache, with cache entries? What i mean is , cache.query(...update operation...) must eventually update the cache entry in

[GitHub] ignite pull request #1686: IGNITE-4669 .NET: Sort binary object fields

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1686 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Memory policies examples fails

Denis, It looks like partition exchange mechanism allocates a lot of pages right after the cache is started. I'm trying to figure out what's going on. Thanks, Sergey. On Mon, Apr 17, 2017 at 12:05 AM, Denis Magda wrote: > Igniters, > > I’ve created a simple example to

[GitHub] ignite pull request #1807: ignite-4982

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/1807 ignite-4982 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite master-fix-tests Alternatively you can review and apply

Re: Memory policies examples fails

Denis, I found an issue with the example: each cache introduces some memory overhead (mostly for cache partitions data structures) and it must be counted in MemoryPolicy size. To fix the example just increase size of *10MB_Region_Eviction *to 15 MB and *5MB_Region_Swapping *to 10 MB. I didn't

Re: Adding ML to Ignite, IGNITE-4572

Denis, Yes, this module already in apache master branch. Also I created ticket for module renaming, so we could discuss this renaming in IGNITE-5000 -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-tp13936p16743.html Sent

[jira] [Created] (IGNITE-5006) .NET: SQL does not work with F# record types

Pavel Tupitsyn created IGNITE-5006: -- Summary: .NET: SQL does not work with F# record types Key: IGNITE-5006 URL: https://issues.apache.org/jira/browse/IGNITE-5006 Project: Ignite Issue

[jira] [Created] (IGNITE-5002) fix tests in master

Konstantin Dudkov created IGNITE-5002: - Summary: fix tests in master Key: IGNITE-5002 URL: https://issues.apache.org/jira/browse/IGNITE-5002 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5003) Parallel write same key in CacheWriteBehindStore

Alexander Belyak created IGNITE-5003: Summary: Parallel write same key in CacheWriteBehindStore Key: IGNITE-5003 URL: https://issues.apache.org/jira/browse/IGNITE-5003 Project: Ignite

[jira] [Created] (IGNITE-5005) WriteBehindStore - split flusher's to different classes by writeCoalescing

Alexander Belyak created IGNITE-5005: Summary: WriteBehindStore - split flusher's to different classes by writeCoalescing Key: IGNITE-5005 URL: https://issues.apache.org/jira/browse/IGNITE-5005

[GitHub] ignite pull request #1810: MemoryConfiguration javadoc updated

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1810 MemoryConfiguration javadoc updated You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite memCfg-doc

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

Why do u think so. First of all, the output above is not correct. After 3 iteration key-value API strats to return empty value. Every 5 seconds(iteration sleep time) repository.getAttributes("1").size() is got called. Which makes an entry "touch" and the entry wont be expired for as long as 10

NULL strings in REST-HTTP

Hi, I would like to change serialization of null strings in our ignite-rest-http module. Current serialization null -> "" (empty string). Proposed serialization null -> null. This will make things more straightforward. Thoughts? -- Alexey Kuznetsov

Re: NULL strings in REST-HTTP

+1 On Mon, Apr 17, 2017 at 1:42 PM, Sergey Kozlov wrote: > Hi Alexey. > > I vote for your fix. Definitely it's wrong to return the empty string > instead of null. > > On Mon, Apr 17, 2017 at 1:30 PM, Alexey Kuznetsov > wrote: > > > Hi, > > > > I

Re: question: How data are stored in IgniteCache?

>> When you transfer an object over the wire or put it into a persistent store (withKeepBinary property enabled) then only the byte array is used. If we put objects into persistent store and withKeepBinary property is DISABLED, in wich form it will be stored? 2017-04-16 18:29 GMT+03:00 Denis

[GitHub] ignite pull request #1809: Ignite 4998

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1809 Ignite 4998 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4998 Alternatively you can review and apply

[jira] [Created] (IGNITE-4997) Make sure dynamic schema state is re-created properly after client re-connect

Vladimir Ozerov created IGNITE-4997: --- Summary: Make sure dynamic schema state is re-created properly after client re-connect Key: IGNITE-4997 URL: https://issues.apache.org/jira/browse/IGNITE-4997

Re: IGNITE-4052 ready for review

Vadim, Thank you for your contribution. I'll look at changes. Can you please post the list improvements to jira ticket? On Mon, Apr 17, 2017 at 3:23 PM, Вадим Опольский wrote: > Hi, Nikolay! > > I've made the following improvements ( https://github.com/apache/ >

[jira] [Created] (IGNITE-4998) Add more dynamic indexing tests for various cache modes

Alexander Paschenko created IGNITE-4998: --- Summary: Add more dynamic indexing tests for various cache modes Key: IGNITE-4998 URL: https://issues.apache.org/jira/browse/IGNITE-4998 Project: Ignite

IGNITE-4799 MetricsUpdate after each job

Now IgniteConfiguration.MetricsUpdate now can be: -1 - disabled 0 - collect after each job >0 - collect after specified amount in ms. If we will use this parameter to send metrics - we should remove this options and leave only >0 values available. Should I remove any 0 and -1 mentions in 4799?

Re: IGNITE-4799 MetricsUpdate after each job

Denis M, Can you please elaborate on this? Currently org.apache.ignite.configuration.IgniteConfiguration#getMetricsUpdateFrequency has special values like 0 and -1 that hardly make sense if we use this parameter in discovery to issue metrics updates. I would agree with Sasha and interpret this

[jira] [Created] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

Yury Babak created IGNITE-5000: -- Summary: Rename Ignite Math module to Ignite ML module Key: IGNITE-5000 URL: https://issues.apache.org/jira/browse/IGNITE-5000 Project: Ignite Issue Type: Task

Re: NULL strings in REST-HTTP

Hi Alexey. I vote for your fix. Definitely it's wrong to return the empty string instead of null. On Mon, Apr 17, 2017 at 1:30 PM, Alexey Kuznetsov wrote: > Hi, > > I would like to change serialization of null strings in our > ignite-rest-http module. > > Current

Re: Page Memory behavior with default memory policy

Agree, I will rename it if there are no objections. 2017-04-17 14:31 GMT+03:00 Vladimir Ozerov : > Guys, > > I see that we throw our own "OutOfMemoryException" in this case. I think we > should rename it to "IgniteOufOfMemoryException" to avoid confusion with > JDK's

IGNITE-4052 ready for review

Hi, Nikolay! I've made the following improvements ( https://github.com/apache/ignite/pull/1783 ): 1) Moved framework builder related code to separate method, so it make code cleaner and framework testable. 2) Call framework builder method from test to test role and user. 3) Added validating

[GitHub] ignite pull request #1808: IGNITE-4587: Found bug - CacheVersionIO is change...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/1808 IGNITE-4587: Found bug - CacheVersionIO is changed, but size isn't You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-4999) Use one thread pool to flush all CacheWriteBehindStore

Alexander Belyak created IGNITE-4999: Summary: Use one thread pool to flush all CacheWriteBehindStore Key: IGNITE-4999 URL: https://issues.apache.org/jira/browse/IGNITE-4999 Project: Ignite

Re: Memory policies examples fails

Wow If it happened to Denis, it will happen to many other users as well. With the exception error message saying "Null", I doubt any user would figure out what to do. Can we fix the error message? D. On Mon, Apr 17, 2017 at 6:03 AM, Sergey Chugunov wrote: >

Re: Adding ML to Ignite, IGNITE-4572

Denis, I prepared preliminary draft doc for readme.io, it reflects proposed rename. You can find it attached to JIRA IGNITE-4964 With regards to merge, per my reading of recent mail from Yury it is done except for module rename which is on its way to master now. regards, Oleg Denis Magda-2

Re: Memory policies examples fails

Dmitriy, I think this issue highlights another lack in our documentation that emerged with introduction of PageMemory. In current documentation we have some recommendations about memory capacity planning. As PageMemory storage data structures introduce their own overhead; this section of

Oleg Ignatenko. Request for contribution permissions.

Hello, My name is Oleg Ignatenko. I am interested in machine learning features that are suggested to Apache Ignite in IGNITE-4572. I would like to contribute to the project. Please grant me the required permissions so I can pick up related tickets (at this time I am specifically interested

Re: Page Memory behavior with default memory policy

Denis, If what you are suggesting is true, then we can always allocate about 80% of available memory by default. By the way, it must also work on Windows, so we should definitely test it. Alexey G, can you comment? D. On Mon, Apr 17, 2017 at 6:17 PM, Denis Magda wrote: >

Re: TouchedExpiryPolicy works incorrect in some cases IGNITE-4401

It doesn’t matter who is right and who is wrong unless someone gets to the bottom of the issue debugging it. I would suggest to create a simple unit test with two caches and trying to reproduce the following without computations and other redundant stuff. Would you like to work on this? —

Re: IGNITE-4799 MetricsUpdate after each job

Yasha, Sergey, As far as I recall discovery SPI exchanges not only compute metrics but cache metrics as well over the cluster ring. Presently, org.apache.ignite.configuration.IgniteConfiguration#getMetricsUpdateFrequency is compute metrics oriented (at least the javadoc says this). After we

Re: Oleg Ignatenko. Request for contribution permissions.

Oleg, Someone has already added you to the contributors list in JIRA. Please check up that you can assign the tickets of interest on yourself. — Denis > On Apr 17, 2017, at 9:13 AM, Oleg Ignatenko wrote: > > Hello, > > My name is Oleg Ignatenko. I am interested in

Re: question: How data are stored in IgniteCache?

It depends on a storage. If it’s a relational database and isStoreKeepBinary is false then an object will be deserialized upon the store invocation and the storage will insert or update a record using “INSERT * ..” or “UPDATE * …” statements. Take a look at the code. — Denis > On Apr 17,

Re: cache query operations

Did you have a chance to take a look this documentation that explains how DML statements are turned into cache operations? https://apacheignite.readme.io/docs/dml#dml-operations — Denis > On Apr 17, 2017, at 7:20 AM, ALEKSEY KUZNETSOV

[GitHub] ignite pull request #1812: testAllocatedMemory fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1812 testAllocatedMemory fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite testAllocatedMemory-fix

[GitHub] ignite pull request #1813: mem.OutOfMemoryException was renamed

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1813 mem.OutOfMemoryException was renamed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite oomexception-rename

Re: Adding ML to Ignite, IGNITE-4572

Thanks Oleg, I’ll review the doc a bit later. Yuri, I’ve reopened IGNITE-5000. Please consider my latest notes and prepare one more pull-request: https://issues.apache.org/jira/browse/IGNITE-5000 — Denis > On Apr 17, 2017, at 8:48 AM,

Re: Null as a name for default memory policy?

+1 to "default". On Tue, Apr 18, 2017 at 8:01 AM, Denis Magda wrote: > Sounds good to me. Other thoughts? > > — > Denis > > > On Apr 17, 2017, at 5:54 PM, Dmitriy Setrakyan > wrote: > > > > How about we name it "default"? > > > > On Mon, Apr 17, 2017

GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

Igniters, GridGain, as one of the most active Apache Ignite contributors, has been developing a unique distributed persistent store specifically for Apache Ignite for more than a year in-house. It’s a fully ACID and ANSI-99 SQL compliant fault-tolerant solution. The store transparently

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

Great news and I am glad that GridGain was finally able to open source such an essential feature to Ignite. Given that I was deeply involved in the development of this feature for the past year, I would add that one of the main advantages here is that Ignite becomes fully operational from disk

Re: Page Memory behavior with default memory policy

Guys, If a memory region is not expandable can we calculate the size of the default one automatically rather than setting it to predefined value like 1 GB, 512 MB, etc. ? For instance, when a node is being started it finds out how much RAM is available and requests 70-80% of it for the

Re: Page Memory behavior with default memory policy

Sorry, misprint Alex G., please confirm that we’re *applying* -> *relying* on this low level guarantees in our page memory impl. > On Apr 17, 2017, at 6:00 PM, Denis Magda wrote: > > Dmitriy, > > All the nodes will request its own continuous memory region that takes

Re: Page Memory behavior with default memory policy

Dmitriy, All the nodes will request its own continuous memory region that takes 70-80% of all RAM from an underlying operation system. However, the operating system will not outfit the nodes with physical pages mapped to RAM immediately allowing every node's process to start successfully. The

Re: Page Memory behavior with default memory policy

On Mon, Apr 17, 2017 at 4:40 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Agree, I will rename it if there are no objections. > +1

Null as a name for default memory policy?

Folks, Are we sure we want to use ‘null’ as a name for the default policy if it’s not configured explicitly? Presently, MemoryConfiguration.getDefaultMemoryPolicyName suggests ‘null’ as a default one. I’m bringing this to your attention only because in AI 2.0 we’re trying to get rid of ‘null’

Re: Page Memory behavior with default memory policy

On Mon, Apr 17, 2017 at 6:00 PM, Denis Magda wrote: > Dmitriy, > > All the nodes will request its own continuous memory region that takes > 70-80% of all RAM from an underlying operation system. However, the > operating system will not outfit the nodes with physical pages

Partition loss policy

Alex G., Dmitriy G., Lucky me, preparing the doc for the page memory I’ve spotted a new feature added to 2.0 which is partition loss policies:

Re: Null as a name for default memory policy?

How about we name it "default"? On Mon, Apr 17, 2017 at 5:53 PM, Denis Magda wrote: > Folks, > > Are we sure we want to use ‘null’ as a name for the default policy if it’s > not configured explicitly? Presently, > MemoryConfiguration.getDefaultMemoryPolicyName > suggests

Re: Memory policies examples fails

Sergey, I tweaked the example following your suggestion. Now it works, thanks. In addition, a javadoc of MemoryConfiguraiton, MemoryPolicyConfiguration and DataPageEvictionMode has been significantly improved. There are some of the parameters like page memory’s concurrency mode and policy’s

[jira] [Created] (IGNITE-5008) Page Memory Throws Meaningless OOM exception if there is an issue in config

Denis Magda created IGNITE-5008: --- Summary: Page Memory Throws Meaningless OOM exception if there is an issue in config Key: IGNITE-5008 URL: https://issues.apache.org/jira/browse/IGNITE-5008 Project:

Re: Null as a name for default memory policy?

Sounds good to me. Other thoughts? — Denis > On Apr 17, 2017, at 5:54 PM, Dmitriy Setrakyan wrote: > > How about we name it "default"? > > On Mon, Apr 17, 2017 at 5:53 PM, Denis Magda wrote: > >> Folks, >> >> Are we sure we want to use ‘null’ as a

Re: Page Memory behavior with default memory policy

Dmitriy, > Denis, it sounds like with this approach, in case of the over-allocation, > the system will just get slower and slower and users will end up blaming > Ignite for it. Am I understanding your suggestion correctly? This will not happen (at least in Unix) unless all the nodes really used

Re: Binary objects and cache store

On Wed, Feb 8, 2017 at 4:57 PM, Denis Magda wrote: > Cross-posting to the dev list. > > Igniters, what if we make “storeKeepBinary” = true by default in Ignite > 2.0? Presently, the user has to tweak the configuration manually. > > Makes sense to me.

Re: Page Memory behavior with default memory policy

On Mon, Apr 17, 2017 at 5:46 PM, Denis Magda wrote: > Guys, > > If a memory region is not expandable can we calculate the size of the > default one automatically rather than setting it to predefined value like 1 > GB, 512 MB, etc. ? > > For instance, when a node is being

Re: Memory policies examples fails

On Mon, Apr 17, 2017 at 9:06 AM, Sergey Chugunov wrote: > Dmitriy, > > I think this issue highlights another lack in our documentation that > emerged with introduction of PageMemory. > > In current documentation we have some recommendations about memory capacity >

[jira] [Created] (IGNITE-5007) Clarify some parameters of MemoryConfiguration and MemoryPolicyConfiguration

Denis Magda created IGNITE-5007: --- Summary: Clarify some parameters of MemoryConfiguration and MemoryPolicyConfiguration Key: IGNITE-5007 URL: https://issues.apache.org/jira/browse/IGNITE-5007 Project: