[GitHub] ignite pull request #2295: IgniteCacheP2pUnmarshallingRebalanceErrorTest fix

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

Re: Enabling memory and persistence metrics

Denis, Indeed for default MemoryPolicy user has to create a MemoryPolicy explicitly. But I strongly dislike the idea of adding new global setting to MemoryConfiguration section. This section is already overloaded with a lot of non-obvious stuff; and adding one more will make it even worse. The

[jira] [Created] (IGNITE-5717) MemoryPolicy configuration and documentation improvements

Sergey Chugunov created IGNITE-5717: --- Summary: MemoryPolicy configuration and documentation improvements Key: IGNITE-5717 URL: https://issues.apache.org/jira/browse/IGNITE-5717 Project: Ignite

[GitHub] ignite pull request #2252: logging

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2252 logging You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite donnet-hangs-debug Alternatively you can review

[GitHub] ignite pull request #2235: two tests unmuted, one test removed as obsolete (...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2235 two tests unmuted, one test removed as obsolete (IGNITE-5592) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

[jira] [Created] (IGNITE-5594) Ignite test framework intervenes into configuration of Ignite node internal component

Sergey Chugunov created IGNITE-5594: --- Summary: Ignite test framework intervenes into configuration of Ignite node internal component Key: IGNITE-5594 URL: https://issues.apache.org/jira/browse/IGNITE-5594

[GitHub] ignite pull request #2199: Ignite gg 12347 1

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2199 Ignite gg 12347 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12347-1 Alternatively you can

[GitHub] ignite pull request #2173: storing binary metadata on disk

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2173 storing binary metadata on disk You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12347

[GitHub] ignite pull request #2163: new method in MarshallerContext interface to regi...

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/2163 --- 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

[GitHub] ignite pull request #2163: new method in MarshallerContext interface to regi...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2163 new method in MarshallerContext interface to register mappings locally You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[jira] [Created] (IGNITE-5559) New method on MarshallerContextImpl to register mappings locally

Sergey Chugunov created IGNITE-5559: --- Summary: New method on MarshallerContextImpl to register mappings locally Key: IGNITE-5559 URL: https://issues.apache.org/jira/browse/IGNITE-5559 Project

[GitHub] ignite pull request #2145: IGNITE-5519

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2145 IGNITE-5519 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5519 Alternatively you can review

[GitHub] ignite pull request #2137: MemoryMetricsTest fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/2137 --- 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

[GitHub] ignite pull request #2137: MemoryMetricsTest fix

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

[jira] [Created] (IGNITE-5499) Binary metadata is persisted when persistence is enabled

Sergey Chugunov created IGNITE-5499: --- Summary: Binary metadata is persisted when persistence is enabled Key: IGNITE-5499 URL: https://issues.apache.org/jira/browse/IGNITE-5499 Project: Ignite

Re: Apache Ignite 2.1 scope

1. IGNITE-5386 Inactive mode must be forced on starting up grid with persistence is enabled It is important improvement to fix critical bug IGNITE-5363. Working on it, ETA - tomorrow. 2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface improvements A lot of

[jira] [Created] (IGNITE-5386) Inactive mode must be forced on starting up grid with persistence enabled

Sergey Chugunov created IGNITE-5386: --- Summary: Inactive mode must be forced on starting up grid with persistence enabled Key: IGNITE-5386 URL: https://issues.apache.org/jira/browse/IGNITE-5386

Re: Persistent Store Stabilization for release

Hello Denis, There are three suites [1] [2] [3] configured on TeamCity with bunch of tests for PDS functionality. As you can see most of tests are passing now (only 6 tests are failing, for *partitionLoss *tests problem was almost sorted out), it looks like that this functionality is pretty

Re: Persistent Distributed Store Metrics

Guys, I created a ticket [1] summing up results of our discussion. Please review and leave comments if something is still unclear there. Thanks, Sergey [1] https://issues.apache.org/jira/browse/IGNITE-5375 On Wed, May 31, 2017 at 11:56 PM, Dmitriy Setrakyan wrote: >

[jira] [Created] (IGNITE-5375) New PersistentStoreMetrics, MemoryMetrics interface improvements

Sergey Chugunov created IGNITE-5375: --- Summary: New PersistentStoreMetrics, MemoryMetrics interface improvements Key: IGNITE-5375 URL: https://issues.apache.org/jira/browse/IGNITE-5375 Project

[jira] [Created] (IGNITE-5363) Exception in logs after starting cluster in inactive mode and subsequent activation

Sergey Chugunov created IGNITE-5363: --- Summary: Exception in logs after starting cluster in inactive mode and subsequent activation Key: IGNITE-5363 URL: https://issues.apache.org/jira/browse/IGNITE-5363

[GitHub] ignite pull request #2045: MemoryPolicyConfiguration.rateTimeInterval proper...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2045 MemoryPolicyConfiguration.rateTimeInterval property changed its type to long You can merge this pull request into a Git repository by running: $ git pull https://github.com

Re: Persistent Distributed Store Metrics

Hello Denis, I have an idea of how we could clarify proposed above approach to collecting metrics for PDS. I suggest to split all metrics into two major groups (disk-related and memory-related) and group them in the following interfaces: public interface PersistenceMemoryMetrics extends

Re: Persistent Store example fails with NPE

ks like a dirty hack when I need to add an > empty MemoryConfiguration to a client config file. Plus, it requires us to > create different configuration files for servers and clients which has to > be optional by default. > > — > Denis > > > On May 26, 2017, at 9:50 AM, Ser

[GitHub] ignite pull request #2016: persistence configuration should be ignored on cl...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2016 persistence configuration should be ignored on client nodes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

Re: Persistent Store example fails with NPE

and proceed without persistence. Supporting persistence on client nodes definitely requires more thoughtful discussion and may be added in the future. Thanks, Sergey. On Fri, May 26, 2017 at 7:28 PM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Denis, > > I see from example tha

Re: Persistent Store example fails with NPE

; > My point is that we just need to create a MemoryConfiguration implicitly > if it’s not defined (no any warnings or extra messages). It’s a > responsibility of our platform to generate a default configuration if it’s > not set explicitly. > > — > Denis > > > On May 2

Re: Persistent Store example fails with NPE

Hi Denis, What is the expected behavior in that case? Bug doesn't suggest any. >From my point of view it would be better to throw an exception on startup with meaningful message than to silently create a default MemoryConfiguration under the cover. Thanks, Sergey. On Fri, May 26, 2017 at 4:00

[jira] [Created] (IGNITE-5302) Empty LOST partition may be used as OWNING after resetting lost partitions

Sergey Chugunov created IGNITE-5302: --- Summary: Empty LOST partition may be used as OWNING after resetting lost partitions Key: IGNITE-5302 URL: https://issues.apache.org/jira/browse/IGNITE-5302

Re: IGNITE-5124 is ready for review

. > > — > Denis > > > On May 23, 2017, at 1:44 AM, Sergey Chugunov <sergey.chugu...@gmail.com> > wrote: > > > > Hello Igniters, > > > > I implemented UX improvements for MemoryMetrics and added/clarified some > > documentation to public API. > >

[jira] [Created] (IGNITE-5273) MemoryMetrics API improvements to be ported to .NET

Sergey Chugunov created IGNITE-5273: --- Summary: MemoryMetrics API improvements to be ported to .NET Key: IGNITE-5273 URL: https://issues.apache.org/jira/browse/IGNITE-5273 Project: Ignite

IGNITE-5124 is ready for review

Hello Igniters, I implemented UX improvements for MemoryMetrics and added/clarified some documentation to public API. Please find changes under pull request here , for discussions feel free to leave comments in upsource review

[GitHub] ignite pull request #1988: properties to configure memoryMetrics are added, ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1988 properties to configure memoryMetrics are added, documentation improved You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[jira] [Created] (IGNITE-5265) Eviction Rate memory metric to be implemented

Sergey Chugunov created IGNITE-5265: --- Summary: Eviction Rate memory metric to be implemented Key: IGNITE-5265 URL: https://issues.apache.org/jira/browse/IGNITE-5265 Project: Ignite Issue

[GitHub] ignite pull request #1930: logging of memory configuration improvements on n...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1930 logging of memory configuration improvements on node start You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

[jira] [Created] (IGNITE-5115) Investigation of failing tests of coordinator node failure

Sergey Chugunov created IGNITE-5115: --- Summary: Investigation of failing tests of coordinator node failure Key: IGNITE-5115 URL: https://issues.apache.org/jira/browse/IGNITE-5115 Project: Ignite

Re: MemoryMetrics interface inconsistencies

what are use cases. And I still don't have a full picture of > > this. > > Yes, there is a gap in here. We will start improving the situation with > this ticket: > https://issues.apache.org/jira/browse/IGNITE-4963 < > https://issues.apache.org/jira/browse/IGNITE-4963> &g

[GitHub] ignite pull request #1878: changes with expandable memory policy and memory ...

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1878 --- 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

[GitHub] ignite pull request #1878: changes with expandable memory policy and memory ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1878 changes with expandable memory policy and memory metrics improvements You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

Re: MemoryMetrics interface inconsistencies

pit...@apache.org > > > >>>> wrote: > >>>> > >>>>> Sergey, I disagree. > >>>>> > >>>>> 1) As a user, I would expect MemoryMetrics instance to be > >>>>> read-only and serializable, so I can send it so

[GitHub] ignite pull request #1872: MemoryMetrics interface cleanup, MemoryMetricsImp...

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1872 --- 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

[GitHub] ignite pull request #1873: logging was improved

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1873 logging was improved You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5079 Alternatively you can

[jira] [Created] (IGNITE-5079) Improve debug logging for binary metadata exchange

Sergey Chugunov created IGNITE-5079: --- Summary: Improve debug logging for binary metadata exchange Key: IGNITE-5079 URL: https://issues.apache.org/jira/browse/IGNITE-5079 Project: Ignite

[GitHub] ignite pull request #1872: MemoryMetrics interface cleanup, MemoryMetricsImp...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1872 MemoryMetrics interface cleanup, MemoryMetricsImpl split You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1800: Obsolete cache metrics removed, test fixed

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1800 --- 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

[GitHub] ignite pull request #1867: incorrect construction of swap files directory pa...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1867 incorrect construction of swap files directory path fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: MemoryMetrics interface inconsistencies

I guess the main reason to have IgniteCache returning snapshot metrics was to collect metrics about distributed cache across the cluster. At the same time MemoryMetrics were initially designed to be local on each node, there were no requirements about collecting cluster-wide MemoryMetrics.

[jira] [Created] (IGNITE-5067) Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir path

Sergey Chugunov created IGNITE-5067: --- Summary: Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir path Key: IGNITE-5067 URL: https://issues.apache.org/jira/browse/IGNITE-5067

[jira] [Created] (IGNITE-5064) Obsolete EventTypes to be removed

Sergey Chugunov created IGNITE-5064: --- Summary: Obsolete EventTypes to be removed Key: IGNITE-5064 URL: https://issues.apache.org/jira/browse/IGNITE-5064 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1860: null is not used as name of default MemoryPolicy ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1860 null is not used as name of default MemoryPolicy anymore You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Page Memory behavior with default memory policy

; On Wed, Apr 19, 2017 at 2:34 AM, Sergey Chugunov < > sergey.chugu...@gmail.com> > wrote: > > > Guys, > > > > I created a ticket to implement these improvements, please take a look: > > IGNITE-5024 <https://issues.apache.org/jira/browse/IGNITE-5024>

Re: Page Memory behavior with default memory policy

namically expandable memory pools. > > > > > > Sergi > > > > > > 2017-04-19 22:20 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > > > > > > > Sergey, > > > > > > > > I have responded in the ticket. Can you

Re: Null as a name for default memory policy?

Guys, I created a ticket for this as a subtask of IGNITE-3488 ; you can find it IGNITE-5025 Thanks, Sergey. On Tue, Apr 18, 2017 at 5:20 AM, Alexey Kuznetsov wrote:

[jira] [Created] (IGNITE-5025) null name for default MemoryPolicy must be replaced with 'default'

Sergey Chugunov created IGNITE-5025: --- Summary: null name for default MemoryPolicy must be replaced with 'default' Key: IGNITE-5025 URL: https://issues.apache.org/jira/browse/IGNITE-5025 Project

Re: Page Memory behavior with default memory policy

Guys, I created a ticket to implement these improvements, please take a look: IGNITE-5024 Besides employing the idea of allocation 80% of physical memory I'm also suggesting to introduce one more configuration property to specify default

[jira] [Created] (IGNITE-5024) Default MemoryPolicy settings improvements

Sergey Chugunov created IGNITE-5024: --- Summary: Default MemoryPolicy settings improvements Key: IGNITE-5024 URL: https://issues.apache.org/jira/browse/IGNITE-5024 Project: Ignite Issue Type

[GitHub] ignite pull request #1822: IGNITE-5008 message of IgniteOutOfMemoryException...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1822 IGNITE-5008 message of IgniteOutOfMemoryException was detailed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

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

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1810 --- 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

[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

[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

Re: Memory policies examples fails

fix the error message? > > D. > > > On Mon, Apr 17, 2017 at 6:03 AM, Sergey Chugunov < > sergey.chugu...@gmail.com> > wrote: > > > Denis, > > > > I found an issue with the example: each cache introduces some memory > > overhead (mostly for cach

[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: Memory policies examples fails

find any documentation on this, but I think it is part of new PageMemory-based storage so it needs to be documented as part of ignite-2.0 release. Thanks, Sergey. On Mon, Apr 17, 2017 at 2:50 PM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Denis, > > It looks like par

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

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 #1800: Obsolete cache metrics removed, test fixed

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1800 Obsolete cache metrics removed, test fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4536

[GitHub] ignite pull request #1794: swap-related functionality removed in ignite-2.0

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1794 swap-related functionality removed in ignite-2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[GitHub] ignite pull request #1788: IGNITE-4952 swap/unswap functionality was removed

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1788 IGNITE-4952 swap/unswap functionality was removed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[GitHub] ignite pull request #1205: IGNITE-4155 minor fixes to examples

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1205 --- 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

[GitHub] ignite pull request #1744: Ignite 3477 master client offheap fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1744 --- 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

[GitHub] ignite pull request #1754: Ignite 3477 client hash index fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1754 --- 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

[GitHub] ignite pull request #1769: Ignite 3477 master CPP Win32 OOM fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1769 --- 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

[GitHub] ignite pull request #1778: client reconnect fix

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1778 --- 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

[jira] [Created] (IGNITE-4952) Swapping-related Event Types must be deleted

Sergey Chugunov created IGNITE-4952: --- Summary: Swapping-related Event Types must be deleted Key: IGNITE-4952 URL: https://issues.apache.org/jira/browse/IGNITE-4952 Project: Ignite Issue

[GitHub] ignite pull request #1778: client reconnect fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1778 client reconnect fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3477-master-client-reconn-fix

[GitHub] ignite pull request #1769: Ignite 3477 master CPP Win32 OOM fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1769 Ignite 3477 master CPP Win32 OOM fix as usual, DO NOT MERGE You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1754: Ignite 3477 client hash index fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1754 Ignite 3477 client hash index fix DO NOT MERGE PR only to run tests on TC You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #1744: Ignite 3477 master client offheap fix

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1744 Ignite 3477 master client offheap fix DO NOT MERGE. PR only to run tests on TC. You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request #1741: IGNITE-4914 distributing marshaller mappings for ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1741 IGNITE-4914 distributing marshaller mappings for multiple platforms fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com

Re: Question: local cache on client nodes

data locally in hashtable like data structure and talk to it > using Ignite APIs. > > The upshot is that this kind of cache can be started on any node and we > should keep supporting this capability in 2.0. > > -- > Denis > > On Thursday, March 30, 2017, Sergey Chugu

[jira] [Created] (IGNITE-4889) Replacement of Cache Key classes with fields not participating in equals operation

Sergey Chugunov created IGNITE-4889: --- Summary: Replacement of Cache Key classes with fields not participating in equals operation Key: IGNITE-4889 URL: https://issues.apache.org/jira/browse/IGNITE-4889

Question: local cache on client nodes

/IGNITE-3477 Thanks, Sergey Chugunov

[GitHub] ignite pull request #1672: MemoryMetrics to monitor how PageMemories perform...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1672 MemoryMetrics to monitor how PageMemories performing You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1655: IGNITE-4302 BinaryMetadata exchange protocol refa...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1655 IGNITE-4302 BinaryMetadata exchange protocol refactored... ... to use **CustomDiscoveryMessage**s instead of system cache You can merge this pull request into a Git repository

Re: IGNITE-4536 metrics of new offheap storage

at[N] - page_size - 16 to page size free bytes. > Agree; using an array instead of separate methods is better. > > — > Denis > > > On Mar 16, 2017, at 10:22 AM, Sergey Chugunov <sergey.chugu...@gmail.com> > wrote: > > > > Denis, > > > >

Re: IGNITE-4536 metrics of new offheap storage

etOffHeapMisses //I think in new model is the same as getCacheMisses > > getOffHeapMissPercentage //same as above > > getOffHeapPuts //same as above > > getOffHeapRemovals //same as above > > Could you please prepare an updated version of the cache metrics adding >

Re: IGNITE-4536 metrics of new offheap storage

getOffHeapRemovals //same as above Please share your thought if I miss something here. Thanks, Sergey Chugunov. On Wed, Mar 15, 2017 at 4:51 PM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Hello Igniters, > > As part of [1] cache metrics need to be updated as some of

IGNITE-4536 metrics of new offheap storage

fragmented entries in cache: may be useful to adjust page size. Please suggest any other metrics that may be worth tracking. [1] https://issues.apache.org/jira/browse/IGNITE-3477 Thanks, Sergey Chugunov.

Re: IGNITE-4758 - introducing cache memory policies

lower size by default. I think 100 MB would be enough. Surely this setting will be configurable via existing MemoryConfiguration interface. Thanks, Sergey. On Thu, Mar 2, 2017 at 11:12 AM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Yes, they use the same PageMemo

Re: IGNITE-4758 - introducing cache memory policies

Yes, they use the same PageMemory region. On Wed, Mar 1, 2017 at 10:34 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > When 2 caches share the same memory policy, does it mean that they are > using the same Page Memory offheap space? > > On Tue, Feb 28, 2017 at 11:49 P

Re: IGNITE-4758 - introducing cache memory policies

Just to confirm, the same memory policy could be shared between different > caches, right? > > D. > > On Tue, Feb 28, 2017 at 1:28 AM, Sergey Chugunov < > sergey.chugu...@gmail.com> > wrote: > > > Hello Ignite devs, > > > > I created new subtask <http

INGITE-4302 PR is ready for review

Hello Igniters, I finished my work on IGNITE-4302 *Exchange binary metadata with discovery custom messages*, pull request is open, TC results

IGNITE-4758 - introducing cache memory policies

Hello Ignite devs, I created new subtask under IGNITE-3477 with my vision of how *MemoryPolicy* may be implemented. In a nutshell my idea is as follows: instead of having only one instance of

[GitHub] ignite pull request #1447: IGNITE-4157 mapping updates notification hook

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1447 --- 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

[jira] [Created] (IGNITE-4706) Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs

Sergey Chugunov created IGNITE-4706: --- Summary: Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs Key: IGNITE-4706 URL: https://issues.apache.org/jira/browse/IGNITE-4706

[jira] [Created] (IGNITE-4679) Consistency checks and error tracking during node joining process

Sergey Chugunov created IGNITE-4679: --- Summary: Consistency checks and error tracking during node joining process Key: IGNITE-4679 URL: https://issues.apache.org/jira/browse/IGNITE-4679 Project

[GitHub] ignite pull request #1506: IGNITE-4302 binary metadata component refactored ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1506 IGNITE-4302 binary metadata component refactored to use discovery-based protocol Metadata updates are exchanged using DiscoveryCustomMessage-based protocol instead of utility cache

Re: Unexpected behavior of DiscoveryCustomMessage acks

Yakov, Thanks for clean explanation, also I found exactly that logic in RingMessageWorker code. But I strongly believe that this behavior should have been documented in *DiscoveryCustomMessage* interface (I think it is the best place for this). Messaging managers like discovery manager must

Unexpected behavior of DiscoveryCustomMessage acks

Hello folks, Working on IGNITE-4302 I developed a protocol for delivering metadata updates to all nodes in cluster. This protocol relies on a guarantee of *DiscoveryCustomMessage* that each message is delivered to *CustomEventListener* exactly

[GitHub] ignite pull request #1463: IGNITE-4157 DO NOT MERGE

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1463 --- 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

<    1   2   3   4   5   >