[jira] [Commented] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy
[
https://issues.apache.org/jira/browse/IGNITE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420959#comment-16420959
]
Dmitriy Pavlov commented on IGNITE-6815:
CI:
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=pull%2F3726%2Fhead&tab=buildTypeStatusDiv
> "Unexpected exception during cache update" via NullPointerException thrown
> using TouchedExpiryPolicy
>
>
> Key: IGNITE-6815
> URL: https://issues.apache.org/jira/browse/IGNITE-6815
> Project: Ignite
> Issue Type: Bug
> Components: cache, streaming
>Affects Versions: 2.2, 2.3
> Environment: 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11
> 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Distributor ID: LinuxMint
> Description: Linux Mint 18.2 Sonya
> Release: 18.2
> Codename: sonya
>Reporter: Reed Sandberg
>Priority: Major
>
> This is triggered when I apply an expiry on the cache during an import with
> StreamLoader, with no expiry on the cache, the import runs fine.
> Somehow the following line of code is hit with val == null:
> org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:1253
> Stack trace (version 2.3.0 release package from maven public repo):
> {noformat}
> 16:04:25.259 ERROR o.a.i.i.p.c.d.d.a.GridDhtAtomicCache -
> Unexpected exception during cache update
> org.apache.ignite.IgniteException: Runtime failure on search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@68a4e885
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1632)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1201)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2419)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1882)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1735)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1627)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1116)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:825)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:783)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1338)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1320)
> at
> org.apache.ignite.stream.StreamTransformer.receive(StreamTransformer.java:45)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6631)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.pro
[jira] [Commented] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy
[
https://issues.apache.org/jira/browse/IGNITE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420945#comment-16420945
]
ASF GitHub Bot commented on IGNITE-6815:
GitHub user reed-sandberg opened a pull request:
https://github.com/apache/ignite/pull/3726
IGNITE-6815 NPE when using expiry policy
* storeLoadedVal needs to be set at each branch of these conditionals
or NPE in inevitible.
A recent update on this Jira says a related patch is available from:
https://issues.apache.org/jira/browse/IGNITE-5874
but this is a bit different - has been running in production successfully
at our site with this fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/reed-sandberg/ignite
rsandberg/IGNITE-6815-expiry-npe
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3726.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 #3726
commit 181ec8d2ec928e0ceee418fc16c6148a2c1feea4
Author: Reed Sandberg
Date: 2018-02-07T23:02:05Z
IGNITE-6815 NPE when using expiry policy
* storeLoadedVal needs to be set at each branch of these conditionals
or NPE in inevitible.
> "Unexpected exception during cache update" via NullPointerException thrown
> using TouchedExpiryPolicy
>
>
> Key: IGNITE-6815
> URL: https://issues.apache.org/jira/browse/IGNITE-6815
> Project: Ignite
> Issue Type: Bug
> Components: cache, streaming
>Affects Versions: 2.2, 2.3
> Environment: 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11
> 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Distributor ID: LinuxMint
> Description: Linux Mint 18.2 Sonya
> Release: 18.2
> Codename: sonya
>Reporter: Reed Sandberg
>Priority: Major
>
> This is triggered when I apply an expiry on the cache during an import with
> StreamLoader, with no expiry on the cache, the import runs fine.
> Somehow the following line of code is hit with val == null:
> org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:1253
> Stack trace (version 2.3.0 release package from maven public repo):
> {noformat}
> 16:04:25.259 ERROR o.a.i.i.p.c.d.d.a.GridDhtAtomicCache -
> Unexpected exception during cache update
> org.apache.ignite.IgniteException: Runtime failure on search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@68a4e885
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1632)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1201)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2419)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1882)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1735)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1627)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1116)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:825)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invo
[jira] [Updated] (IGNITE-7935) Add batch update operation to PageMemory and Persistence
[ https://issues.apache.org/jira/browse/IGNITE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh updated IGNITE-7935: - Summary: Add batch update operation to PageMemory and Persistence (was: Add batch update operation to CacheDataStore) > Add batch update operation to PageMemory and Persistence > > > Key: IGNITE-7935 > URL: https://issues.apache.org/jira/browse/IGNITE-7935 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ilya Lantukh >Priority: Major > Labels: iep-16 > > Updating each key-value pair independently is very inefficient when data > arrives in batches (examples: cache.putAll(...), dataStreamer, preloading). > Our internal data structures (B+ tree, FreeList) can be used more efficiently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy
[
https://issues.apache.org/jira/browse/IGNITE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420872#comment-16420872
]
Reed Sandberg edited comment on IGNITE-6815 at 3/30/18 7:50 PM:
The following has fixed the problem in our production environment (stable for 3
months now)
2.3:
[https://github.com/reed-sandberg/ignite/commit/e6310e8d1481396f8cf3a5ede834989d0b277fc5]
2.4:
[https://github.com/reed-sandberg/ignite/commit/29ffe10e7be5ce3193b2fcb89c713c5269761c1c]
was (Author: rsandberg):
The following has fixed the problem in our production environment (stable for 3
months now)
https://github.com/reed-sandberg/ignite/commit/e6310e8d1481396f8cf3a5ede834989d0b277fc5
> "Unexpected exception during cache update" via NullPointerException thrown
> using TouchedExpiryPolicy
>
>
> Key: IGNITE-6815
> URL: https://issues.apache.org/jira/browse/IGNITE-6815
> Project: Ignite
> Issue Type: Bug
> Components: cache, streaming
>Affects Versions: 2.2, 2.3
> Environment: 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11
> 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Distributor ID: LinuxMint
> Description: Linux Mint 18.2 Sonya
> Release: 18.2
> Codename: sonya
>Reporter: Reed Sandberg
>Priority: Major
>
> This is triggered when I apply an expiry on the cache during an import with
> StreamLoader, with no expiry on the cache, the import runs fine.
> Somehow the following line of code is hit with val == null:
> org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:1253
> Stack trace (version 2.3.0 release package from maven public repo):
> {noformat}
> 16:04:25.259 ERROR o.a.i.i.p.c.d.d.a.GridDhtAtomicCache -
> Unexpected exception during cache update
> org.apache.ignite.IgniteException: Runtime failure on search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@68a4e885
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1632)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1201)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2419)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1882)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1735)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1627)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1116)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:825)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:783)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1338)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1320)
> at
> org.apache.ignite.stream.StreamTransformer.receive(StreamTransformer.java:45)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6631)
> at
> org.apache.ignite.internal.processo
[jira] [Commented] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy
[
https://issues.apache.org/jira/browse/IGNITE-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420872#comment-16420872
]
Reed Sandberg commented on IGNITE-6815:
---
The following has fixed the problem in our production environment (stable for 3
months now)
https://github.com/reed-sandberg/ignite/commit/e6310e8d1481396f8cf3a5ede834989d0b277fc5
> "Unexpected exception during cache update" via NullPointerException thrown
> using TouchedExpiryPolicy
>
>
> Key: IGNITE-6815
> URL: https://issues.apache.org/jira/browse/IGNITE-6815
> Project: Ignite
> Issue Type: Bug
> Components: cache, streaming
>Affects Versions: 2.2, 2.3
> Environment: 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11
> 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Distributor ID: LinuxMint
> Description: Linux Mint 18.2 Sonya
> Release: 18.2
> Codename: sonya
>Reporter: Reed Sandberg
>Priority: Major
>
> This is triggered when I apply an expiry on the cache during an import with
> StreamLoader, with no expiry on the cache, the import runs fine.
> Somehow the following line of code is hit with val == null:
> org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:1253
> Stack trace (version 2.3.0 release package from maven public repo):
> {noformat}
> 16:04:25.259 ERROR o.a.i.i.p.c.d.d.a.GridDhtAtomicCache -
> Unexpected exception during cache update
> org.apache.ignite.IgniteException: Runtime failure on search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@68a4e885
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1632)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1201)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2419)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1882)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1735)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1627)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1116)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:825)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:783)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1338)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1320)
> at
> org.apache.ignite.stream.StreamTransformer.receive(StreamTransformer.java:45)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6631)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException: null
> at
> o
[jira] [Updated] (IGNITE-8091) Create Ignite monitoring guide describing metrics and monitoring facilities
[ https://issues.apache.org/jira/browse/IGNITE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8091: Summary: Create Ignite monitoring guide describing metrics and monitoring facilities (was: Create a documentation section describing metrics and monitoring facilities) > Create Ignite monitoring guide describing metrics and monitoring facilities > --- > > Key: IGNITE-8091 > URL: https://issues.apache.org/jira/browse/IGNITE-8091 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Priority: Major > Labels: iep-6 > Fix For: 2.6 > > > Ignite doesn't have a single documentation section which would aggregate all > the metrics the project has. There are random documentation pages spread out > across data grid, memory, persistence and other topics. > The new section will include the following: > * How to gather metrics (JMX, logs, APIs) > * Detailed metrics coverage for memory, persistence, rebalancing, compute, > etc. Consider IGNITE-8078 and IGNITE-8077 > * Monitoring tools > * How to integrate with 3rd party tools. > Use a draft of a monitoring guide as a reference: > https://docs.google.com/document/d/1yl7XoiWWPg_XGhwZJUg9Mm3muEApefoMiNLxEUxggV4/edit# -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8091) Create a documentation section describing metrics and monitoring facilities
[ https://issues.apache.org/jira/browse/IGNITE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8091: Description: Ignite doesn't have a single documentation section which would aggregate all the metrics the project has. There are random documentation pages spread out across data grid, memory, persistence and other topics. The new section will include the following: * How to gather metrics (JMX, logs, APIs) * Detailed metrics coverage for memory, persistence, rebalancing, compute, etc. Consider IGNITE-8078 and IGNITE-8077 * Monitoring tools * How to integrate with 3rd party tools. Use a draft of a monitoring guide as a reference: https://docs.google.com/document/d/1yl7XoiWWPg_XGhwZJUg9Mm3muEApefoMiNLxEUxggV4/edit# was: Ignite doesn't have a single documentation section which would aggregate all the metrics the project has. There are random documentation pages spread out across data grid, memory, persistence and other topics. The new section will include the following: * How to gather metrics (JMX, logs, APIs) * Detailed metrics coverage for memory, persistence, rebalancing, compute, etc. Consider IGNITE-8078 and IGNITE-8077 * Monitoring tools * How to integrate with 3rd party tools. > Create a documentation section describing metrics and monitoring facilities > --- > > Key: IGNITE-8091 > URL: https://issues.apache.org/jira/browse/IGNITE-8091 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Priority: Major > Labels: iep-6 > Fix For: 2.6 > > > Ignite doesn't have a single documentation section which would aggregate all > the metrics the project has. There are random documentation pages spread out > across data grid, memory, persistence and other topics. > The new section will include the following: > * How to gather metrics (JMX, logs, APIs) > * Detailed metrics coverage for memory, persistence, rebalancing, compute, > etc. Consider IGNITE-8078 and IGNITE-8077 > * Monitoring tools > * How to integrate with 3rd party tools. > Use a draft of a monitoring guide as a reference: > https://docs.google.com/document/d/1yl7XoiWWPg_XGhwZJUg9Mm3muEApefoMiNLxEUxggV4/edit# -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8091) Create a documentation section describing metrics and monitoring facilities
[ https://issues.apache.org/jira/browse/IGNITE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8091: Labels: iep-6 (was: ) > Create a documentation section describing metrics and monitoring facilities > --- > > Key: IGNITE-8091 > URL: https://issues.apache.org/jira/browse/IGNITE-8091 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Priority: Major > Labels: iep-6 > Fix For: 2.6 > > > Ignite doesn't have a single documentation section which would aggregate all > the metrics the project has. There are random documentation pages spread out > across data grid, memory, persistence and other topics. > The new section will include the following: > * How to gather metrics (JMX, logs, APIs) > * Detailed metrics coverage for memory, persistence, rebalancing, compute, > etc. Consider IGNITE-8078 and IGNITE-8077 > * Monitoring tools > * How to integrate with 3rd party tools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8091) Create a documentation section describing metrics and monitoring facilities
Denis Magda created IGNITE-8091: --- Summary: Create a documentation section describing metrics and monitoring facilities Key: IGNITE-8091 URL: https://issues.apache.org/jira/browse/IGNITE-8091 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Denis Magda Fix For: 2.6 Ignite doesn't have a single documentation section which would aggregate all the metrics the project has. There are random documentation pages spread out across data grid, memory, persistence and other topics. The new section will include the following: * How to gather metrics (JMX, logs, APIs) * Detailed metrics coverage for memory, persistence, rebalancing, compute, etc. Consider IGNITE-8078 and IGNITE-8077 * Monitoring tools * How to integrate with 3rd party tools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6980) Automatic cancelling of hanging Ignite operations
[ https://issues.apache.org/jira/browse/IGNITE-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6980: Issue Type: New Feature (was: Bug) > Automatic cancelling of hanging Ignite operations > - > > Key: IGNITE-6980 > URL: https://issues.apache.org/jira/browse/IGNITE-6980 > Project: Ignite > Issue Type: New Feature >Reporter: Denis Magda >Assignee: Aleksey Plekhanov >Priority: Blocker > Labels: iep-7, important > Fix For: 2.5 > > > If an Ignite operation hangs due to some reason due to an internal problem or > buggy application code it needs to eventual fail after a timeout fires. > An application must not freeze waiting for a human being intervention if an > atomic update fails internally. > Even more, I would let all possible operation to fail after a timeout fires: > - Ignite compute computations (covered by IGNITE-6940). > - Ignite services calls. > - Atomic cache updates (see devlist discussion - > [http://apache-ignite-developers.2346864.n4.nabble.com/Timeouts-in-atomic-cache-td19839.html]). > - Transactional cache updates (covered by IGNITE-6894 and IGNITE-6895). > - SQL queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8044) IgniteQueryGenerator.getOptions() method should properly handle empty list of parameters.
[
https://issues.apache.org/jira/browse/IGNITE-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420743#comment-16420743
]
Denis Magda commented on IGNITE-8044:
-
[~slava.koptilin], [~dpavlov], the changes look good to me. Please feel free to
merge them once you solve all the concerns about the flacky tests.
> IgniteQueryGenerator.getOptions() method should properly handle empty list of
> parameters.
> -
>
> Key: IGNITE-8044
> URL: https://issues.apache.org/jira/browse/IGNITE-8044
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Minor
> Fix For: 2.5
>
>
> {{IgniteQueryGenerator.getOptions()}} method does not check that the
> parameters list can be empty.
> Initial discussion of the issue is available on the user-list:
> http://apache-ignite-users.70518.x6.nabble.com/ArrayIndexOutOfBoundsException-1-in-IgniteQueryGenerator-getOptions-tt20801.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8044) IgniteQueryGenerator.getOptions() method should properly handle empty list of parameters.
[
https://issues.apache.org/jira/browse/IGNITE-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420743#comment-16420743
]
Denis Magda edited comment on IGNITE-8044 at 3/30/18 5:27 PM:
--
[~slava.koptilin], [~dpavlov], the changes look good to me. Please feel free to
merge them once you solve all the concerns about the flaky tests.
was (Author: dmagda):
[~slava.koptilin], [~dpavlov], the changes look good to me. Please feel free to
merge them once you solve all the concerns about the flacky tests.
> IgniteQueryGenerator.getOptions() method should properly handle empty list of
> parameters.
> -
>
> Key: IGNITE-8044
> URL: https://issues.apache.org/jira/browse/IGNITE-8044
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Minor
> Fix For: 2.5
>
>
> {{IgniteQueryGenerator.getOptions()}} method does not check that the
> parameters list can be empty.
> Initial discussion of the issue is available on the user-list:
> http://apache-ignite-users.70518.x6.nabble.com/ArrayIndexOutOfBoundsException-1-in-IgniteQueryGenerator-getOptions-tt20801.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6186) Remove redundant parameter of GridFutureAdapter::unregisterWaiter()
[
https://issues.apache.org/jira/browse/IGNITE-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420733#comment-16420733
]
Andrey Gura commented on IGNITE-6186:
-
[~andrey-kuznetsov] LGTM. But I renamed methid to {{unregisterWaiter}} because
it is symmetrical to {{registerWaiter}}. Merged to master branch.
> Remove redundant parameter of GridFutureAdapter::unregisterWaiter()
> ---
>
> Key: IGNITE-6186
> URL: https://issues.apache.org/jira/browse/IGNITE-6186
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Minor
> Fix For: 2.5
>
>
> The method is not thread-safe unless actual parameter is currentThread.
> Let future state is a list of listeners and two concurrent threads are
> removing two adjacent non-root listener nodes from list simultaneously by
> calling {{unregisterWaiter()}}. Then data race is possible: one of these
> listeners can survive its removal. If the listener is a thread waiting for
> completion in {{get0()}} then this race leads at worst case to 1 extra call
> to {{LockSupport.park()}}, and it's negligible. Otherwise we deal with an
> arbitrary listener, and its {{apply()}} will be called twice.
> To be precise, this Jira issue does not relate to any existing bug, but it
> eliminates fragile construct that can explode on future chages/refactorings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6287) DDL Support for WebConsole
[
https://issues.apache.org/jira/browse/IGNITE-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420722#comment-16420722
]
Denis Magda commented on IGNITE-6287:
-
Hi Stan,
Yes, that bug was definitely fixed a long time ago. Please make sure you're
on the latest Web Console version.
Send a message to user/dev list if the issue is not gone.
--
Denis
> DDL Support for WebConsole
> --
>
> Key: IGNITE-6287
> URL: https://issues.apache.org/jira/browse/IGNITE-6287
> Project: Ignite
> Issue Type: New Feature
>Reporter: Denis Magda
>Assignee: Pavel Konstantinov
>Priority: Critical
> Labels: usability
> Fix For: 2.3
>
> Attachments: screenshot-1.png
>
>
> DDL queries like CREATE TABLE don't work in Web Console.
> First, if Ignite cluster is started with zero caches deployed then "Execute"
> button will be disabled and there is now way to execute CREATE TABLE in
> general.
> Second, if to create a dummy cache on cluster startup and execute this
> {code}
> CREATE TABLE City (
> id LONG PRIMARY KEY, name VARCHAR)
> WITH "template=replicated";
> {code}
> Then the console will generate the exception
> {code}
> Error: class org.apache.ignite.internal.processors.query.IgniteSQLException:
> CREATE TABLE can only be executed on PUBLIC schema.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8080) Partition update counter can be incremented twice in case of transaction commit and near cache enabled
[ https://issues.apache.org/jira/browse/IGNITE-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko reassigned IGNITE-8080: --- Assignee: Alexey Goncharuk (was: Pavel Kovalenko) Fix is ready. PR: https://github.com/apache/ignite/pull/3721 TC: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F3721%2Fhead > Partition update counter can be incremented twice in case of transaction > commit and near cache enabled > -- > > Key: IGNITE-8080 > URL: https://issues.apache.org/jira/browse/IGNITE-8080 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Assignee: Alexey Goncharuk >Priority: Minor > Fix For: 2.5 > > > Problem: > * Commit local transaction (IgniteTxLocalAdapter#userCommit()) > * TxEntry is updated and update counter is incremented. > * Try to update near cache entry and this operation can throw > GridCacheEntryRemovedException > * In case when exception is thrown we start to update TxEntry again and > update counter will be incremented twice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8090) Explain disk space compaction by WAL and compaction techniques
Denis Magda created IGNITE-8090: --- Summary: Explain disk space compaction by WAL and compaction techniques Key: IGNITE-8090 URL: https://issues.apache.org/jira/browse/IGNITE-8090 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Denis Magda Fix For: 2.5 Explain how WAL occupies the disk space and how to enable the compaction: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-WALHistorySize There needs to be a special section in WAL documentation as well as in the capacity planning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7691) Provide info about DECIMAL column scale and precision
[ https://issues.apache.org/jira/browse/IGNITE-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420682#comment-16420682 ] Dmitriy Pavlov commented on IGNITE-7691: First run is more or less ok, let's wait for second run. > Provide info about DECIMAL column scale and precision > - > > Key: IGNITE-7691 > URL: https://issues.apache.org/jira/browse/IGNITE-7691 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > Fix For: 2.5 > > > Currently, it impossible to obtain scale and precision of DECIMAL column from > sql table metadata. > Ignite should provide those type of meta information. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-8087) Assertion error in time to rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh updated IGNITE-8087:
-
Comment: was deleted
(was: Looks like this assertion should be removed.)
> Assertion error in time to rebalancing
> --
>
> Key: IGNITE-8087
> URL: https://issues.apache.org/jira/browse/IGNITE-8087
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.5
>
>
> {noformat}
> 2018-03-30
> 10:06:17.936[ERROR][sys-#308516%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=4754f275-a46b-4df5-b263-8369a9cb899b,
> msg=GridDhtPartitionSupplyMessage [updateSeq=151421,
> topVer=AffinityTopologyVersion [topVer=546, minorTopVer=8], missed=null,
> clean=null, msgSize=524554, estimatedKeysCnt=-1, size=1, parts=[45],
> super=GridCacheGroupIdMessage [grpId=218536256]]]
> java.lang.AssertionError: GridDhtCacheEntry [rdrs=[], part=45,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=45, val=1005, hasValBytes=true], val=null,
> startVer=1522624104073, ver=GridCacheVersion [topVer=133119151,
> order=1522038055581, nodeOrder=13], hash=1005, extras=null, flags=3]]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.onDeferredDelete(GridCacheContext.java:1644)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:377)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2713)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:375)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:354)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1609)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2751)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1515)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1484)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8089) Cache group presence assertion failed in (PM) exchange in IgniteStandByClientReconnectToNewClusterTest
Dmitriy Pavlov created IGNITE-8089:
--
Summary: Cache group presence assertion failed in (PM) exchange in
IgniteStandByClientReconnectToNewClusterTest
Key: IGNITE-8089
URL: https://issues.apache.org/jira/browse/IGNITE-8089
Project: Ignite
Issue Type: Test
Reporter: Dmitriy Pavlov
IgniteStandByClusterSuite:
IgniteStandByClientReconnectToNewClusterTest.testActiveClientReconnectToActiveCluster
(master fail rate 11,3%)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-3118895430102702001&branch=%3Cdefault%3E&tab=testDetails
{noformat}
java.lang.AssertionError: -2100569601
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
at
org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:1003)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2344)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8087) Assertion error in time to rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420629#comment-16420629
]
Ilya Lantukh commented on IGNITE-8087:
--
Looks like this assertion should be removed.
> Assertion error in time to rebalancing
> --
>
> Key: IGNITE-8087
> URL: https://issues.apache.org/jira/browse/IGNITE-8087
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.5
>
>
> {noformat}
> 2018-03-30
> 10:06:17.936[ERROR][sys-#308516%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=4754f275-a46b-4df5-b263-8369a9cb899b,
> msg=GridDhtPartitionSupplyMessage [updateSeq=151421,
> topVer=AffinityTopologyVersion [topVer=546, minorTopVer=8], missed=null,
> clean=null, msgSize=524554, estimatedKeysCnt=-1, size=1, parts=[45],
> super=GridCacheGroupIdMessage [grpId=218536256]]]
> java.lang.AssertionError: GridDhtCacheEntry [rdrs=[], part=45,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=45, val=1005, hasValBytes=true], val=null,
> startVer=1522624104073, ver=GridCacheVersion [topVer=133119151,
> order=1522038055581, nodeOrder=13], hash=1005, extras=null, flags=3]]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.onDeferredDelete(GridCacheContext.java:1644)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:377)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2713)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:375)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:354)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1609)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2751)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1515)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1484)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8088) Flaky assertion in testJoinClientStaticCacheConfigurationOnJoin for cache presence
[
https://issues.apache.org/jira/browse/IGNITE-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8088:
---
Description:
IgniteStandByClusterSuite:
JoinInActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin
(master fail rate 12,8%)
IgniteStandByClusterSuite:
JoinActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin
(master fail rate 10,0%)
Link to test histories:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-1780719797264285338&branch=%3Cdefault%3E&tab=testDetails
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=5703653634172546268&branch=%3Cdefault%3E&tab=testDetails
{noformat}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:621)
at org.junit.Assert.assertNotNull(Assert.java:631)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$9.apply(AbstractNodeJoinTemplate.java:801)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$9.apply(AbstractNodeJoinTemplate.java:791)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$10.run(AbstractNodeJoinTemplate.java:824)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder.execute(AbstractNodeJoinTemplate.java:611)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.join.JoinInActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin(JoinInActiveNodeToActiveCluster.java:228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
at java.lang.Thread.run(Thread.java:745)
{noformat}
was:
IgniteStandByClusterSuite:
JoinInActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin
(master fail rate 12,8%)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-1780719797264285338&branch=%3Cdefault%3E&tab=testDetails
{noformat}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:621)
at org.junit.Assert.assertNotNull(Assert.java:631)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$9.apply(AbstractNodeJoinTemplate.java:801)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$9.apply(AbstractNodeJoinTemplate.java:791)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$10.run(AbstractNodeJoinTemplate.java:824)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder.execute(AbstractNodeJoinTemplate.java:611)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.join.JoinInActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin(JoinInActiveNodeToActiveCluster.java:228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
at java.lang.Thread.run(Thread.java:745)
{noformat}
> Flaky assertion in testJoinClientStaticCacheConfigurationOnJoin for cache
> presence
> --
>
> Key: IGNITE-8088
[jira] [Created] (IGNITE-8088) Flaky assertion in testJoinClientStaticCacheConfigurationOnJoin for cache presence
Dmitriy Pavlov created IGNITE-8088:
--
Summary: Flaky assertion in
testJoinClientStaticCacheConfigurationOnJoin for cache presence
Key: IGNITE-8088
URL: https://issues.apache.org/jira/browse/IGNITE-8088
Project: Ignite
Issue Type: Test
Reporter: Dmitriy Pavlov
IgniteStandByClusterSuite:
JoinInActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin
(master fail rate 12,8%)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-1780719797264285338&branch=%3Cdefault%3E&tab=testDetails
{noformat}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:621)
at org.junit.Assert.assertNotNull(Assert.java:631)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$9.apply(AbstractNodeJoinTemplate.java:801)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$9.apply(AbstractNodeJoinTemplate.java:791)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder$10.run(AbstractNodeJoinTemplate.java:824)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.AbstractNodeJoinTemplate$JoinNodeTestPlanBuilder.execute(AbstractNodeJoinTemplate.java:611)
at
org.apache.ignite.internal.processors.cache.persistence.standbycluster.join.JoinInActiveNodeToActiveCluster.testJoinClientStaticCacheConfigurationOnJoin(JoinInActiveNodeToActiveCluster.java:228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8087) Assertion error in time to rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8087:
-
Fix Version/s: 2.5
> Assertion error in time to rebalancing
> --
>
> Key: IGNITE-8087
> URL: https://issues.apache.org/jira/browse/IGNITE-8087
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.5
>
>
> {noformat}
> 2018-03-30
> 10:06:17.936[ERROR][sys-#308516%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=4754f275-a46b-4df5-b263-8369a9cb899b,
> msg=GridDhtPartitionSupplyMessage [updateSeq=151421,
> topVer=AffinityTopologyVersion [topVer=546, minorTopVer=8], missed=null,
> clean=null, msgSize=524554, estimatedKeysCnt=-1, size=1, parts=[45],
> super=GridCacheGroupIdMessage [grpId=218536256]]]
> java.lang.AssertionError: GridDhtCacheEntry [rdrs=[], part=45,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=45, val=1005, hasValBytes=true], val=null,
> startVer=1522624104073, ver=GridCacheVersion [topVer=133119151,
> order=1522038055581, nodeOrder=13], hash=1005, extras=null, flags=3]]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.onDeferredDelete(GridCacheContext.java:1644)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:377)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2713)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:375)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:354)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1609)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2751)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1515)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1484)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8087) Assertion error in time to rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh reassigned IGNITE-8087:
Assignee: Ilya Lantukh
> Assertion error in time to rebalancing
> --
>
> Key: IGNITE-8087
> URL: https://issues.apache.org/jira/browse/IGNITE-8087
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Ilya Lantukh
>Priority: Major
>
> {noformat}
> 2018-03-30
> 10:06:17.936[ERROR][sys-#308516%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
> Failed processing message [senderId=4754f275-a46b-4df5-b263-8369a9cb899b,
> msg=GridDhtPartitionSupplyMessage [updateSeq=151421,
> topVer=AffinityTopologyVersion [topVer=546, minorTopVer=8], missed=null,
> clean=null, msgSize=524554, estimatedKeysCnt=-1, size=1, parts=[45],
> super=GridCacheGroupIdMessage [grpId=218536256]]]
> java.lang.AssertionError: GridDhtCacheEntry [rdrs=[], part=45,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=45, val=1005, hasValBytes=true], val=null,
> startVer=1522624104073, ver=GridCacheVersion [topVer=133119151,
> order=1522038055581, nodeOrder=13], hash=1005, extras=null, flags=3]]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.onDeferredDelete(GridCacheContext.java:1644)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:377)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2713)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:375)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:354)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1609)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2751)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1515)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1484)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8087) Assertion error in time to rebalancing
Vladislav Pyatkov created IGNITE-8087:
-
Summary: Assertion error in time to rebalancing
Key: IGNITE-8087
URL: https://issues.apache.org/jira/browse/IGNITE-8087
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
{noformat}
2018-03-30
10:06:17.936[ERROR][sys-#308516%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
Failed processing message [senderId=4754f275-a46b-4df5-b263-8369a9cb899b,
msg=GridDhtPartitionSupplyMessage [updateSeq=151421,
topVer=AffinityTopologyVersion [topVer=546, minorTopVer=8], missed=null,
clean=null, msgSize=524554, estimatedKeysCnt=-1, size=1, parts=[45],
super=GridCacheGroupIdMessage [grpId=218536256]]]
java.lang.AssertionError: GridDhtCacheEntry [rdrs=[], part=45,
super=GridDistributedCacheEntry [super=GridCacheMapEntry
[key=KeyCacheObjectImpl [part=45, val=1005, hasValBytes=true], val=null,
startVer=1522624104073, ver=GridCacheVersion [topVer=133119151,
order=1522038055581, nodeOrder=13], hash=1005, extras=null, flags=3]]]
at
org.apache.ignite.internal.processors.cache.GridCacheContext.onDeferredDelete(GridCacheContext.java:1644)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:446)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.unswap(GridCacheMapEntry.java:377)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2713)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:798)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:678)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:375)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:354)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:99)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1609)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:126)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2751)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1515)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:126)
at
org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1484)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7957) TestDistributedJoins fails in CPP Win32 suite
[
https://issues.apache.org/jira/browse/IGNITE-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-7957:
---
Assignee: Igor Sapego
> TestDistributedJoins fails in CPP Win32 suite
> -
>
> Key: IGNITE-7957
> URL: https://issues.apache.org/jira/browse/IGNITE-7957
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Reporter: Dmitriy Pavlov
>Assignee: Igor Sapego
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=417754190398412&branch=%3Cdefault%3E&tab=testDetails
>Ignite Platform CPP Win32 [ tests 1 TC_EXIT_CODE ]
> IgniteOdbcTest: QueriesTestSuite: TestDistributedJoins (fail rate 9,8%)
> {noformat}
> check env != 0 passed
> check dbc != 0 passed
> check stmt != 0 passed
> check rowsNum > 0 passed
> check rowsNum < entriesNum passed
> check env != 0 passed
> check dbc != 0 passed
> check stmt != 0 passed
> check rowsNum == entriesNum failed [2565 != 1000]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8012) CPP: BinaryWriter::WriteElement should accept const reference instead of value.
[ https://issues.apache.org/jira/browse/IGNITE-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-8012: --- Assignee: Igor Sapego > CPP: BinaryWriter::WriteElement should accept const reference instead of > value. > --- > > Key: IGNITE-8012 > URL: https://issues.apache.org/jira/browse/IGNITE-8012 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.0 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: cpp > > This will improve performance in case when large objects are used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8086) Flaky test timeouts in Activate/Deactivate Cluster suite
Dmitriy Pavlov created IGNITE-8086: -- Summary: Flaky test timeouts in Activate/Deactivate Cluster suite Key: IGNITE-8086 URL: https://issues.apache.org/jira/browse/IGNITE-8086 Project: Ignite Issue Type: Test Reporter: Dmitriy Pavlov Activate | Deactivate Cluster IgniteStandByClusterSuite: CacheBaselineTopologyTest.testPrimaryLeftAndClusterRestart (master fail rate 37,1%) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6798733272445954906&branch=%3Cdefault%3E&tab=testDetails IgniteStandByClusterSuite: CacheBaselineTopologyTest.testBaselineTopologyChangesFromClient (master fail rate 24,9%) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-9217764610687235146&branch=%3Cdefault%3E&tab=testDetails IgniteStandByClusterSuite: IgniteClusterActivateDeactivateTest.testClientReconnectClusterDeactivateInProgress (master fail rate 12,8%) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=5210129488604303757&branch=%3Cdefault%3E&tab=testDetails java.util.concurrent.TimeoutException: Test has been timed out [test=testPrimaryLeftAndClusterRestart, timeout=30] - no obivious assertions and exceptions generated in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8012) CPP: BinaryWriter::WriteElement should accept const reference instead of value.
[ https://issues.apache.org/jira/browse/IGNITE-8012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420576#comment-16420576 ] ASF GitHub Bot commented on IGNITE-8012: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3724 IGNITE-8012: CPP: Changed passing by values by passing by reference You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8012 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3724.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 #3724 commit 84816ab77920223d6a9bb454a8742cb792c5b3ca Author: Igor Sapego Date: 2018-03-30T14:47:12Z IGNITE-8012: CPP: Changed passing by values by passing by ref > CPP: BinaryWriter::WriteElement should accept const reference instead of > value. > --- > > Key: IGNITE-8012 > URL: https://issues.apache.org/jira/browse/IGNITE-8012 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.0 >Reporter: Igor Sapego >Priority: Major > Labels: cpp > > This will improve performance in case when large objects are used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.
Dmitriy Pavlov created IGNITE-8085:
--
Summary: Flaky failures in Ignite Client Nodes test suite: Remote
node could not start.
Key: IGNITE-8085
URL: https://issues.apache.org/jira/browse/IGNITE-8085
Project: Ignite
Issue Type: Test
Reporter: Dmitriy Pavlov
Ignite Start Nodes
IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls (master
fail rate 12,1%)
IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodes (master fail rate 10,1%)
IgniteStartStopRestartTestSuite:
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds (master fail rate
10,1%)
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&branch=%3Cdefault%3E&tab=testDetails
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1179745277331816127&branch=%3Cdefault%3E&tab=testDetails
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-842929918974855010&branch=%3Cdefault%3E&tab=testDetails
Test itself is quite old. Last commits were from [~tledkov-gridgain] at 2017.
{noformat}
class org.apache.ignite.IgniteException: Remote node could not start. See log
for details:
/data/teamcity/work/bd85361428dcdb1/work/log/ignite-startNodes/03-29-2018--02-47-24-2003434e.log
at
org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:388)
at
org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:383)
at org.apache.ignite.internal.util.lang.GridFunc.forEach(GridFunc.java:1897)
at
org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls(IgniteProjectionStartStopRestartSelfTest.java:383)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7499) DataRegionMetricsImpl#getPageSize returns ZERO for system data regions
[ https://issues.apache.org/jira/browse/IGNITE-7499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420559#comment-16420559 ] Alexey Goncharuk commented on IGNITE-7499: -- Alexey, System page size is an implementation detail. Internal pages have some overhead needed to track certain runtime page properties. PageSize is an effective page size that is written to the disk. Zero being returned for system regions looks like a bug to me. > DataRegionMetricsImpl#getPageSize returns ZERO for system data regions > -- > > Key: IGNITE-7499 > URL: https://issues.apache.org/jira/browse/IGNITE-7499 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Major > Fix For: 2.5 > > > Working on IGNITE-7492 I found that DataRegionMetricsImpl#getPageSize returns > ZERO for system data regions. > Meanwhile there is also > org.apache.ignite.internal.pagemem.PageMemory#systemPageSize method. > That looks a bit strange, why we need PageSize and SystemPageSize ? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7499) DataRegionMetricsImpl#getPageSize returns ZERO for system data regions
[ https://issues.apache.org/jira/browse/IGNITE-7499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-7499: - Description: Working on IGNITE-7492 I found that DataRegionMetricsImpl#getPageSize returns ZERO for system data regions. Meanwhile there is also org.apache.ignite.internal.pagemem.PageMemory#systemPageSize method. That looks a bit strange, why we need PageSize and SystemPageSize ? was: Working on IGNITE-7492 I found that DataRegionMetricsImpl#getPageSize returns ZERO for system data regions. Mmeanwhile there org.apache.ignite.internal.pagemem.PageMemory#systemPageSize method. That looks a bit strange, why we need PageSize and SystemPageSize ? > DataRegionMetricsImpl#getPageSize returns ZERO for system data regions > -- > > Key: IGNITE-7499 > URL: https://issues.apache.org/jira/browse/IGNITE-7499 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Major > Fix For: 2.5 > > > Working on IGNITE-7492 I found that DataRegionMetricsImpl#getPageSize returns > ZERO for system data regions. > Meanwhile there is also > org.apache.ignite.internal.pagemem.PageMemory#systemPageSize method. > That looks a bit strange, why we need PageSize and SystemPageSize ? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420513#comment-16420513
]
Vladimir Ozerov commented on IGNITE-8078:
-
[~DmitriyGovorukhin], what is the purpose of {{IndexMxBean.getProcessedPuts}}
and {{IndexMxBean.getProcessedGets}} metrics? Do not make sense to me, because
typically we do not do "gets" on indexes, we do searches instead. And for
"puts" it is not clear how to align them with dynamic index creation. I would
avoid exposing this stuff to public API. Instead, we'd better to expose index
statistics here (histograms, selectivity, clustering, etc) when they are ready.
> Add new metrics for data storage
>
>
> Key: IGNITE-8078
> URL: https://issues.apache.org/jira/browse/IGNITE-8078
> Project: Ignite
> Issue Type: New Feature
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Labels: iep-6
>
> 1. Create new MXbean for each index, IndexMxBean
> {code}
> class IndexMxBean{
> /** The number of PUT operations on the index. */
> long getProcessedPuts();
> /** The number of GET operations on the index. */
> long getProcessedGets();
> /** The total index size in bytes. */
> long getIndexSize();
> /** Index name.*/
> String getName();
> }
> {code}
> 2. Add new metrics for data storage and cache group.
> {code}
> class CacheGroupMetricsMXBean{
> /** The total index size in bytes */
> long getIndexesSize();
> /** Total size in bytes for primary key indexes. */
> long getPKIndexesSize();
> /** Total size in bytes. */
> long getTotalSize();
> /** Total size in bytes for pure data.*/
> long getDataSize();
> /** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
> String getType();
> /** Partitions currently assigned to the local node in this cache group. */
> int[] getPartitions();
> }
> {code}
> {code}
> class DataRegionMXBean{
> /** Total size in bytes for indexes. */
> long getIndexesSize();
> /** Total size in bytes for primary key indexes. */
> long getPKIndexesSize();
> /** Total size in bytes. */
> long getTotalSize();
> /** Total size in bytes for pure data.*/
> long getDataSize();
> /** Total used offheap size in bytes. */
> long getOffheapUsedSize();
> /** The number of read pages from last restart. */
> long getPagesRead();
> /** The number of writen pages from last restart. */
> long getPagesWriten();
> /** The number of replaced pages from last restart . */
> long getPagesReplaced();
> /** Total dirty pages for the next checkpoint. */
> long getDirtyPagesForNextCheckpoint();
> }
> {code}
> {code}
> class DataStorageMXbean{
> /** Total size in bytes for indexes. */
> long getIndexesSize();
> /** Total size in bytes for primary key indexes. */
> long getPKIndexesSize();
> /** Total size in bytes for all storages. */
> long getTotalSize();
> /** Total offheap size in bytes. */
> long getOffHeapSize();
> /** Total used offheap size in bytes for all data regions. */
> long getOffheapUsedSize();
> /** Total size in bytes for pure data.*/
> long getDataSize();
> /** The number of read pages from last restart. */
> long getPagesRead();
> /** The number of writen pages from last restart. */
> long getPagesWriten();
> /** The number of replaced pages from last restart. */
> long getPagesReplaced();
> /** Total checkpoint time from last restart. */
> long getCheckpointTotalTime();
> /** Total dirty pages for the next checkpoint. */
> long getDirtyPagesForNextCheckpoint();
> /** Total size in bytes for storage wal files. */
> long getWalTotalSize();
> /** Time of the last WAL segment rollover. */
> long getWalLastSwitchTime();
> }
> {code}
> {code}
> class IgniteMxBean {
> /** Returns string containing Node ID, Consistent ID, Node Order */
> String getCurrentCoordinator();
> }
> {code}
> Depricate CacheMetrics.getRebalancingPartitionsCount(); and move to
> CacheGroupMetricsMXBean.getRebalancingPartitionsCount();
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8013) CPP: Check pending snapshots in BinaryTypeManager::GetHandler
[
https://issues.apache.org/jira/browse/IGNITE-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-8013:
---
Assignee: Igor Sapego
> CPP: Check pending snapshots in BinaryTypeManager::GetHandler
> -
>
> Key: IGNITE-8013
> URL: https://issues.apache.org/jira/browse/IGNITE-8013
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
>
> This will improve performance a lot, when using operations like {{PutAll()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8013) CPP: Check pending snapshots in BinaryTypeManager::GetHandler
[
https://issues.apache.org/jira/browse/IGNITE-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420500#comment-16420500
]
ASF GitHub Bot commented on IGNITE-8013:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/3723
IGNITE-8013: CPP: Added check of pending snapshots in GetHandler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8013
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3723.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 #3723
commit 2353c1a856ddcdf377e3644a32ceff28f488fbe5
Author: Igor Sapego
Date: 2018-03-30T13:41:55Z
IGNITE-8013: Added check of pending snapshots in GetHandler
> CPP: Check pending snapshots in BinaryTypeManager::GetHandler
> -
>
> Key: IGNITE-8013
> URL: https://issues.apache.org/jira/browse/IGNITE-8013
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Priority: Major
> Labels: cpp
>
> This will improve performance a lot, when using operations like {{PutAll()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6501) select distinct exception in simple sqlQuery request.
[
https://issues.apache.org/jira/browse/IGNITE-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6501:
Component/s: documentation
> select distinct exception in simple sqlQuery request.
> -
>
> Key: IGNITE-6501
> URL: https://issues.apache.org/jira/browse/IGNITE-6501
> Project: Ignite
> Issue Type: Bug
> Components: documentation, sql
>Affects Versions: 2.0, 2.1
>Reporter: Stanilovsky Evgeny
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.6
>
> Attachments: DistinctTest.java
>
>
> SqlQuery throws exception
> {code}
> Failed to parse query: SELECT distinct Value._KEY, distinct Value._VAL from
> Value
> {code}
> while SqlFieldsQuery works properly well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6501) select distinct exception in simple sqlQuery request.
[
https://issues.apache.org/jira/browse/IGNITE-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6501:
Fix Version/s: 2.6
> select distinct exception in simple sqlQuery request.
> -
>
> Key: IGNITE-6501
> URL: https://issues.apache.org/jira/browse/IGNITE-6501
> Project: Ignite
> Issue Type: Bug
> Components: documentation, sql
>Affects Versions: 2.0, 2.1
>Reporter: Stanilovsky Evgeny
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.6
>
> Attachments: DistinctTest.java
>
>
> SqlQuery throws exception
> {code}
> Failed to parse query: SELECT distinct Value._KEY, distinct Value._VAL from
> Value
> {code}
> while SqlFieldsQuery works properly well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8070) .Net: FailureHandler should be added to Ignite configuration
[
https://issues.apache.org/jira/browse/IGNITE-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-8070:
---
Assignee: (was: Alexander Paschenko)
> .Net: FailureHandler should be added to Ignite configuration
>
>
> Key: IGNITE-8070
> URL: https://issues.apache.org/jira/browse/IGNITE-8070
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Priority: Major
> Labels: MakeTeamcityGreenAgain, iep-14
> Fix For: 2.5
>
>
> {{IgniteConfiguration}} class was extended by new methods:
> {{setFailureHandler}} and {{getFailureHandler}}. Corresponding changes should
> be done in ignite .Net
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6699) Optimize client-side data streamer performance
[
https://issues.apache.org/jira/browse/IGNITE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420444#comment-16420444
]
Ivan Fedotov commented on IGNITE-6699:
--
Example for 7 threads in ignite-6699:
{noformat}
Benchmark Mode Cnt Score Error
Units
JmhStreamerAddDataBenchmark.addDataCollection avgt 11 50,990 ± 5,162 ms/op
{noformat}
{noformat}
Benchmark Mode Cnt Score Error Units
JmhStreamerAddDataBenchmark.addDataKeyValueavgt 11 49,230 ± 3,125 ms/op
{noformat}
> Optimize client-side data streamer performance
> --
>
> Key: IGNITE-6699
> URL: https://issues.apache.org/jira/browse/IGNITE-6699
> Project: Ignite
> Issue Type: Task
> Components: streaming
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Ivan Fedotov
>Priority: Major
> Labels: iep-1, performance
> Fix For: 2.5
>
>
> Currently if a user has several server nodes and a single client node with
> single thread pushing data to streamer, he will not be able to load data at
> maximum speed. On the other hand, if he start several data loading threads,
> throughput will increase.
> One of root causes of this is bad data streamer design. Method
> {{IgniteDataStreamer.addData(K, V)}} returns new feature for every operation,
> this is too fine grained approach. Also it generates a lot of garbage and
> causes contention on streamer internals.
> Proposed implementation flow:
> 1) Compare performance of {{addData(K, V)}} vs {{addData(Collection)}}
> methods from one thread in distributed environment. The latter should show
> considerably higher throughput.
> 2) Users should receive per-batch features, rather than per-key.
> 3) Try caching thread data in some collection until it is large enough to
> avoid contention and unnecessary allocations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6630) Incorrect time units of average transaction commit/rollback duration cache metrics.
[
https://issues.apache.org/jira/browse/IGNITE-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420436#comment-16420436
]
Pavel Pereslegin commented on IGNITE-6630:
--
[~alex_pl]
could you take a look at this change, please?
> Incorrect time units of average transaction commit/rollback duration cache
> metrics.
> ---
>
> Key: IGNITE-6630
> URL: https://issues.apache.org/jira/browse/IGNITE-6630
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Minor
> Labels: metrics, newbie
> Fix For: 2.5
>
>
> AverageTxCommitTime and AverageTxRollbackTime metrics in CacheMetrics counts
> in milliseconds instead of microseconds as pointed in javadoc.
> Simple junit reproducer:
> {code:java}
> public class CacheMetricsTxAvgTimeTest extends GridCommonAbstractTest {
> /** */
> private CacheConfiguration cacheConfiguration(String name) {
> CacheConfiguration cacheConfiguration = new
> CacheConfiguration<>(name);
> cacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
> cacheConfiguration.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> cacheConfiguration.setStatisticsEnabled(true);
> return cacheConfiguration;
> }
> /** */
> public void testTxCommitDuration() throws Exception {
> try ( Ignite node = startGrid(0)) {
> IgniteCache cache =
> node.createCache(cacheConfiguration(DEFAULT_CACHE_NAME));
> try (Transaction tx = node.transactions().txStart()) {
> cache.put(1, 1);
> // Await 1 second.
> U.sleep(1_000);
> tx.commit();
> }
> // Documentation says that this metric is in microseconds.
> float commitTime = cache.metrics().getAverageTxCommitTime();
> // But this assertion will fail because it in milliseconds and
> returns only ~1000.
> assert commitTime >= 1_000_000;
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8084) Unlock write lock in DataStreamerImpl
Ivan Fedotov created IGNITE-8084: Summary: Unlock write lock in DataStreamerImpl Key: IGNITE-8084 URL: https://issues.apache.org/jira/browse/IGNITE-8084 Project: Ignite Issue Type: Improvement Components: streaming Reporter: Ivan Fedotov Assignee: Ivan Fedotov Fix For: 2.5 In method DataStreamerImpl.CloseEx there is wrire lock without unlock [1]. I think this behavior is based on impossibility to call after closing other public method of DataStreamer, that use read lock. It's not correctly that after closing streamer we don't unlock writeLock: I think that we can use *closed* flag to throw exception if streamer will be used after closing. [1]https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1217 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8017) Disable WAL during initial preloading
[ https://issues.apache.org/jira/browse/IGNITE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420428#comment-16420428 ] Ilya Lantukh commented on IGNITE-8017: -- [~avinogradov], We're disabling WAL when node doesn't have OWNING partitions and enabling it right before changing state to OWNING. > Disable WAL during initial preloading > - > > Key: IGNITE-8017 > URL: https://issues.apache.org/jira/browse/IGNITE-8017 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Labels: iep-16 > Fix For: 2.5 > > > While handling SupplyMessage, node handles each supplied data entry > separately, which causes a WAL record for each entry to be written. It > significantly limits preloading speed. > We can improve rebalancing speed and reduce pressure on disk by disabling WAL > until all data is loaded. The disadvantage of this approach is that data > might get corrupted if node crashes - but node that crashed during preloading > has to clear all it's data anyway. However, it is important to distinguish > situations when new node joined cluster or added to baseline topology (and > doesn't hold any data) and when additional partitions got assigned to node > after baseline topology changed (in this case node has to keep all data in > consistent state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8017) Disable WAL during initial preloading
[ https://issues.apache.org/jira/browse/IGNITE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8017: - Labels: iep-16 (was: ) > Disable WAL during initial preloading > - > > Key: IGNITE-8017 > URL: https://issues.apache.org/jira/browse/IGNITE-8017 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Labels: iep-16 > Fix For: 2.5 > > > While handling SupplyMessage, node handles each supplied data entry > separately, which causes a WAL record for each entry to be written. It > significantly limits preloading speed. > We can improve rebalancing speed and reduce pressure on disk by disabling WAL > until all data is loaded. The disadvantage of this approach is that data > might get corrupted if node crashes - but node that crashed during preloading > has to clear all it's data anyway. However, it is important to distinguish > situations when new node joined cluster or added to baseline topology (and > doesn't hold any data) and when additional partitions got assigned to node > after baseline topology changed (in this case node has to keep all data in > consistent state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8018) Avoid unnecessary unswap(...) call in GridCacheMapEntry.initialValue(...)
[ https://issues.apache.org/jira/browse/IGNITE-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8018: - Labels: iep-16 (was: ) > Avoid unnecessary unswap(...) call in GridCacheMapEntry.initialValue(...) > - > > Key: IGNITE-8018 > URL: https://issues.apache.org/jira/browse/IGNITE-8018 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Labels: iep-16 > Fix For: 2.5 > > > GridCacheMapEntry.initialValue(...) method executes unswap(...) to read entry > version from PageMemory, but then it also executes storeValue(...) which > writes new value if entry is obsolete. It means that the same entry is > searched in PageMemory twice, which is not optimal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8019) During rebalancing checkpoint read lock is acquired for each entry (twice).
[ https://issues.apache.org/jira/browse/IGNITE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8019: - Labels: iep-16 (was: ) > During rebalancing checkpoint read lock is acquired for each entry (twice). > --- > > Key: IGNITE-8019 > URL: https://issues.apache.org/jira/browse/IGNITE-8019 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Labels: iep-16 > Fix For: 2.5 > > > In GridDhtPartitionDemander.preloadEntry(...) checkpointReadLock is acquired > twice, which is definitely a mistake. But even acquiring it once per entry > causes unnecessary contention - it should be taken once for SupplyMessage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8020) Rebalancing for persistent caches should transfer file store over network instead of using existing supply/demand protocol
[ https://issues.apache.org/jira/browse/IGNITE-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8020: - Labels: iep-16 (was: ) > Rebalancing for persistent caches should transfer file store over network > instead of using existing supply/demand protocol > -- > > Key: IGNITE-8020 > URL: https://issues.apache.org/jira/browse/IGNITE-8020 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Labels: iep-16 > > Existing rebalancing protocol is suitable for in-memory data storage, but for > data persisted in files it is sub-optimal and requires a lot of unnecessary > steps. Efforts to optimize it led to necessity to completely rework the > protocol - instead of sending batches (SupplyMessages) with cache entries it > is possible to send data files directly. > The algorithm should look like this: > 1. Demander node sends requests with required partition IDs (like now) > 2. Supplier node receives request and performs a checkpoint. > 3. After checkpoint is done, supplier sends files with demanded partitions > using low-level NIO API. > 4. During steps 2-3, demander node should work in special mode - it should > temporary store all incoming updates in such way that they can be quickly > applied later. > 5. After files are transferred, demander applies updates stored at step 4. > The tricky part here is to switch work modes of demander node avoiding all > possible race conditions. Also, the aforementioned algorithm should be > extended to transfer or rebuild query indexes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7935) Add batch update operation to CacheDataStore
[ https://issues.apache.org/jira/browse/IGNITE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-7935: - Labels: iep-16 (was: ) > Add batch update operation to CacheDataStore > > > Key: IGNITE-7935 > URL: https://issues.apache.org/jira/browse/IGNITE-7935 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ilya Lantukh >Priority: Major > Labels: iep-16 > > Updating each key-value pair independently is very inefficient when data > arrives in batches (examples: cache.putAll(...), dataStreamer, preloading). > Our internal data structures (B+ tree, FreeList) can be used more efficiently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8017) Disable WAL during initial preloading
[ https://issues.apache.org/jira/browse/IGNITE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8017: - Fix Version/s: 2.5 > Disable WAL during initial preloading > - > > Key: IGNITE-8017 > URL: https://issues.apache.org/jira/browse/IGNITE-8017 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.5 > > > While handling SupplyMessage, node handles each supplied data entry > separately, which causes a WAL record for each entry to be written. It > significantly limits preloading speed. > We can improve rebalancing speed and reduce pressure on disk by disabling WAL > until all data is loaded. The disadvantage of this approach is that data > might get corrupted if node crashes - but node that crashed during preloading > has to clear all it's data anyway. However, it is important to distinguish > situations when new node joined cluster or added to baseline topology (and > doesn't hold any data) and when additional partitions got assigned to node > after baseline topology changed (in this case node has to keep all data in > consistent state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8018) Avoid unnecessary unswap(...) call in GridCacheMapEntry.initialValue(...)
[ https://issues.apache.org/jira/browse/IGNITE-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8018: - Fix Version/s: 2.5 > Avoid unnecessary unswap(...) call in GridCacheMapEntry.initialValue(...) > - > > Key: IGNITE-8018 > URL: https://issues.apache.org/jira/browse/IGNITE-8018 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.5 > > > GridCacheMapEntry.initialValue(...) method executes unswap(...) to read entry > version from PageMemory, but then it also executes storeValue(...) which > writes new value if entry is obsolete. It means that the same entry is > searched in PageMemory twice, which is not optimal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8019) During rebalancing checkpoint read lock is acquired for each entry (twice).
[ https://issues.apache.org/jira/browse/IGNITE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-8019: - Fix Version/s: 2.5 > During rebalancing checkpoint read lock is acquired for each entry (twice). > --- > > Key: IGNITE-8019 > URL: https://issues.apache.org/jira/browse/IGNITE-8019 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.5 > > > In GridDhtPartitionDemander.preloadEntry(...) checkpointReadLock is acquired > twice, which is definitely a mistake. But even acquiring it once per entry > causes unnecessary contention - it should be taken once for SupplyMessage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6699) Optimize client-side data streamer performance
[
https://issues.apache.org/jira/browse/IGNITE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420420#comment-16420420
]
Ivan Fedotov commented on IGNITE-6699:
--
There are results of benchmarks on streaming 7000 integers with 1 client and 2
server nodes:
*addData(Collection)* -
https://gist.github.com/1vanan/8a1d310526ba3783894f5181067a272c
*addData(Key, Value)* master -
https://gist.github.com/1vanan/cbe10aed7768b00fa6e4176b7e6ed51c
*addData(Key, Value)* ignite-6699 -
https://gist.github.com/1vanan/cef0abf262bcc054aaa9ec54d84bb4f1
According to result, the time of data streaming per key/value has decreased on
*32%* in average and became equal to streaming data per collection. The smaller
data streaming time is better.
> Optimize client-side data streamer performance
> --
>
> Key: IGNITE-6699
> URL: https://issues.apache.org/jira/browse/IGNITE-6699
> Project: Ignite
> Issue Type: Task
> Components: streaming
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Ivan Fedotov
>Priority: Major
> Labels: iep-1, performance
> Fix For: 2.5
>
>
> Currently if a user has several server nodes and a single client node with
> single thread pushing data to streamer, he will not be able to load data at
> maximum speed. On the other hand, if he start several data loading threads,
> throughput will increase.
> One of root causes of this is bad data streamer design. Method
> {{IgniteDataStreamer.addData(K, V)}} returns new feature for every operation,
> this is too fine grained approach. Also it generates a lot of garbage and
> causes contention on streamer internals.
> Proposed implementation flow:
> 1) Compare performance of {{addData(K, V)}} vs {{addData(Collection)}}
> methods from one thread in distributed environment. The latter should show
> considerably higher throughput.
> 2) Users should receive per-batch features, rather than per-key.
> 3) Try caching thread data in some collection until it is large enough to
> avoid contention and unnecessary allocations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7467) Verify partition update counters and sizes on partition map exchange
[ https://issues.apache.org/jira/browse/IGNITE-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-7467: Fix Version/s: 2.5 > Verify partition update counters and sizes on partition map exchange > > > Key: IGNITE-7467 > URL: https://issues.apache.org/jira/browse/IGNITE-7467 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.1 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.5 > > Attachments: partitions_update_counters_and_sizes_affected_tests > > > In Ignite we heavily rely on an invariant that under no load owning > partitions will have equal sizes and, more importantly, equal partition > counters. This invariant becomes even more important when persistence is > enabled. > However, due to a possible bug in the code, this invariant can be violated > which in a long run may lead to an undetected data loss. We need to take best > effort to detect such a situation as soon as possible. > Currently, we already send partition update counters during partition map > exchange. We can also send partition sizes and verify that corresponding > partitions in OWNING state have equal partition update counters and sizes. > If a divergence detected, we can: > 1) Always print out an error message to the log > 2) Move the corresponding caches to the read-only state to prevent further > corruption or operating on invalid data > Also, we can introduce a ./control.sh command which will trigger an empty > exchange to verify the partition states. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8063) Transaction rollback is unmanaged in case when commit produced Runtime exception
[ https://issues.apache.org/jira/browse/IGNITE-8063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-8063: Priority: Minor (was: Major) > Transaction rollback is unmanaged in case when commit produced Runtime > exception > > > Key: IGNITE-8063 > URL: https://issues.apache.org/jira/browse/IGNITE-8063 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Minor > Fix For: 2.5 > > > When 'userCommit' produces an runtime exception transaction state is moved to > UNKNOWN, and tx.finishFuture() completes, after that rollback process runs > asynchronously and there is no simple way to await rollback completion on > such transactions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8017) Disable WAL during initial preloading
[ https://issues.apache.org/jira/browse/IGNITE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420408#comment-16420408 ] Anton Vinogradov commented on IGNITE-8017: -- [~ilantukh] Am I understand correct that we're disabling WAL automatically and only in case node initially join topology (when it has no owhed partitions is rebalancing cache)? > Disable WAL during initial preloading > - > > Key: IGNITE-8017 > URL: https://issues.apache.org/jira/browse/IGNITE-8017 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > > While handling SupplyMessage, node handles each supplied data entry > separately, which causes a WAL record for each entry to be written. It > significantly limits preloading speed. > We can improve rebalancing speed and reduce pressure on disk by disabling WAL > until all data is loaded. The disadvantage of this approach is that data > might get corrupted if node crashes - but node that crashed during preloading > has to clear all it's data anyway. However, it is important to distinguish > situations when new node joined cluster or added to baseline topology (and > doesn't hold any data) and when additional partitions got assigned to node > after baseline topology changed (in this case node has to keep all data in > consistent state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8083) Direct Message types for mongo request/responses duplicate other message' direct type.
Max Shonichev created IGNITE-8083:
-
Summary: Direct Message types for mongo request/responses
duplicate other message' direct type.
Key: IGNITE-8083
URL: https://issues.apache.org/jira/browse/IGNITE-8083
Project: Ignite
Issue Type: Bug
Reporter: Max Shonichev
{noformat}
public class GridMongoExecuteRequest implements Message, Externalizable {
...
/** \{@inheritDoc} */
@Override public short directType() {
return 79;
}
...
}
{noformat}
duplicates
{noformat}
public class MissingMappingResponseMessage implements Message {
...
/** \{@inheritDoc} */
@Override public short directType() {
return 79;
}
...
}
{noformat}
Same for
* GridMongoExecuteResponse/MetadataRequestMessage
* GridMongoQueryRequest/MetadataResponseMessage
* GridMongoQueryResponse/JobStealingRequest
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8082) No management bean for ZookeeperDiscoverySpi
Max Shonichev created IGNITE-8082: - Summary: No management bean for ZookeeperDiscoverySpi Key: IGNITE-8082 URL: https://issues.apache.org/jira/browse/IGNITE-8082 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Max Shonichev Fix For: 2.5 TcpDiscoverySpi provides management bean, allowing user to obtain configuration and metrics from it via JMX. However, Zookeeper discovery spi provides no management bean, please add it with similar attributes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8069) IgniteOutOfMemoryException should be handled accordingly to provided failure handler
[
https://issues.apache.org/jira/browse/IGNITE-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-8069:
-
Assignee: Aleksey Plekhanov
> IgniteOutOfMemoryException should be handled accordingly to provided failure
> handler
>
>
> Key: IGNITE-8069
> URL: https://issues.apache.org/jira/browse/IGNITE-8069
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: iep-14
> Fix For: 2.5
>
>
> {{IgniteOutOfMemoryException}} should be handled accordingly to provided
> failure handler.
> There are a couple of places where this exception can be thrown. Need to find
> a common place(s) where this exception could be handled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-8078:
---
Description:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long getProcessedPuts();
/** The number of GET operations on the index. */
long getProcessedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] getPartitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long getOffheapUsedSize();
/** The number of read pages from last restart. */
long getPagesRead();
/** The number of writen pages from last restart. */
long getPagesWriten();
/** The number of replaced pages from last restart . */
long getPagesReplaced();
/** Total dirty pages for the next checkpoint. */
long getDirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalSize();
/** Total offheap size in bytes. */
long getOffHeapSize();
/** Total used offheap size in bytes for all data regions. */
long getOffheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long getPagesRead();
/** The number of writen pages from last restart. */
long getPagesWriten();
/** The number of replaced pages from last restart. */
long getPagesReplaced();
/** Total checkpoint time from last restart. */
long getCheckpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long getDirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long getWalTotalSize();
/** Time of the last WAL segment rollover. */
long getWalLastSwitchTime();
}
{code}
{code}
class IgniteMxBean {
/** Returns string containing Node ID, Consistent ID, Node Order */
String getCurrentCoordinator();
}
{code}
Depricate CacheMetrics.getRebalancingPartitionsCount(); and move to
CacheGroupMetricsMXBean.getRebalancingPartitionsCount();
was:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long getProcessedPuts();
/** The number of GET operations on the index. */
long getProcessedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] getPartitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long getOffheapUsedSize();
/** The number of read pages from last restart. */
long getPagesRead();
/** The number of writen pages from last restart. */
long getPagesWriten();
/** The number of replaced pages from last restart . */
long getPagesReplaced();
/** Total dirty pages for the next checkpoint. */
long getDirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalSize();
/** Total offheap size in bytes. */
long getOffHeapSize();
/** Total used offheap size in bytes for all data regions. */
long getOffheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize(
[jira] [Commented] (IGNITE-8080) Partition update counter can be incremented twice in case of transaction commit and near cache enabled
[ https://issues.apache.org/jira/browse/IGNITE-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420365#comment-16420365 ] ASF GitHub Bot commented on IGNITE-8080: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3721 IGNITE-8080 Avoid updating tx entries twice You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8080 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3721.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 #3721 commit 9b0adbdf4a251badb7cb0868c598a6a40c6e4a3e Author: Pavel Kovalenko Date: 2018-03-30T10:36:30Z IGNITE-8080 Avoid updating tx entries twice if near entry update throws EntryRemovedException. > Partition update counter can be incremented twice in case of transaction > commit and near cache enabled > -- > > Key: IGNITE-8080 > URL: https://issues.apache.org/jira/browse/IGNITE-8080 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Minor > Fix For: 2.5 > > > Problem: > * Commit local transaction (IgniteTxLocalAdapter#userCommit()) > * TxEntry is updated and update counter is incremented. > * Try to update near cache entry and this operation can throw > GridCacheEntryRemovedException > * In case when exception is thrown we start to update TxEntry again and > update counter will be incremented twice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8077) Implement new JMX metrics for transactions
[
https://issues.apache.org/jira/browse/IGNITE-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-8077:
---
Description:
These additional metrics should be implemented to monitor transactions.
{code}
class TransactionsMXbean{
/** The number of transactions which was commited. */
long getTxCommited();
/** The number of transactions which was rollbacked. */
long getTxRolledBack();
/** The number of transactions holding at least one key lock. */
long getTxHoldingLock();
/** The number of keys locked on the node. */
long getLockedKeys();
/** The number of transactions for which node is the initiator. */
int getOwnerTxs();
}
{code}
For more details see in IgniteTxAdapter and IgniteTxManager.
was:
These additional metrics should be implemented to monitor transactions.
{code}
class TransactionsMXbean{
/** The number of transactions which was commited. */
long getTxCommited();
/** The number of transactions which was rollbacked. */
long getTxRollBacked();
/** The number of transactions holding at least one key lock. */
long getTxHoldingLock();
/** The number of keys locked on the node. */
long getLockedKeys();
/** The number of transactions for which node is the initiator. */
int getOwnerTxs();
}
{code}
For more details see in IgniteTxAdapter and IgniteTxManager.
> Implement new JMX metrics for transactions
> --
>
> Key: IGNITE-8077
> URL: https://issues.apache.org/jira/browse/IGNITE-8077
> Project: Ignite
> Issue Type: New Feature
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Labels: iep-6
>
> These additional metrics should be implemented to monitor transactions.
> {code}
> class TransactionsMXbean{
> /** The number of transactions which was commited. */
> long getTxCommited();
> /** The number of transactions which was rollbacked. */
> long getTxRolledBack();
> /** The number of transactions holding at least one key lock. */
> long getTxHoldingLock();
> /** The number of keys locked on the node. */
> long getLockedKeys();
> /** The number of transactions for which node is the initiator. */
> int getOwnerTxs();
> }
> {code}
> For more details see in IgniteTxAdapter and IgniteTxManager.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky
[
https://issues.apache.org/jira/browse/IGNITE-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420349#comment-16420349
]
Dmitriy Pavlov commented on IGNITE-5960:
Hi [~Alexey Kuznetsov],
I see suspicious failure here:
IgniteCacheTestSuite5:
CacheLateAffinityAssignmentTest.testCreateCloseClientCacheOnCoordinator1
(master fail rate 0,0%)
Probably rebase (merge) of master into branch will solve this failure.
> Ignite Continuous Query (Queries 3):
> CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic
> is flaky
> -
>
> Key: IGNITE-5960
> URL: https://issues.apache.org/jira/browse/IGNITE-5960
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.5
>
>
> According to [TC
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=6546112007182082024&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E]
> test is flaky.
> It is possible to reproduce it locally, sample run shows 9 failed tests out
> of 30 overall executed.
> Test fails with jUnit assertion check:
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :1
> Actual :0
>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.concurrentUpdatesAndQueryStart(CacheContinuousQueryConcurrentPartitionUpdateTest.java:385)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.testConcurrentUpdatesAndQueryStartTx(CacheContinuousQueryConcurrentPartitionUpdateTest.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8078:
-
Description:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long getProcessedPuts();
/** The number of GET operations on the index. */
long getProcessedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] getPartitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long getOffheapUsedSize();
/** The number of read pages from last restart. */
long getPagesRead();
/** The number of writen pages from last restart. */
long getPagesWriten();
/** The number of replaced pages from last restart . */
long getPagesReplaced();
/** Total dirty pages for the next checkpoint. */
long getDirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalSize();
/** Total offheap size in bytes. */
long getOffHeapSize();
/** Total used offheap size in bytes for all data regions. */
long getOffheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long getPagesRead();
/** The number of writen pages from last restart. */
long getPagesWriten();
/** The number of replaced pages from last restart. */
long getPagesReplaced();
/** Total checkpoint time from last restart. */
long getCheckpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long getDirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long getWalTotalSize();
/** Time of the last WAL segment rollover. */
long getWalLastSwitchTime();
}
{code}
{code}
class IgniteMxBean {
/** Returns string containing Node ID, Consistent ID, Node Order */
String getCurrentCoordinator();
}
{code}
was:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] partitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number o
[jira] [Updated] (IGNITE-8077) Implement new JMX metrics for transactions
[
https://issues.apache.org/jira/browse/IGNITE-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8077:
-
Description:
These additional metrics should be implemented to monitor transactions.
{code}
class TransactionsMXbean{
/** The number of transactions which was commited. */
long getTxCommited();
/** The number of transactions which was rollbacked. */
long getTxRollBacked();
/** The number of transactions holding at least one key lock. */
long getTxHoldingLock();
/** The number of keys locked on the node. */
long getLockedKeys();
/** The number of transactions for which node is the initiator. */
int getOwnerTxs();
}
{code}
For more details see in IgniteTxAdapter and IgniteTxManager.
was:
These additional metrics should be implemented to monitor transactions.
{code}
class TransactionsMXbean{
/** The number of transactions which was commited. */
long txCommited();
/** The number of transactions which was rollbacked. */
long txRollBacked();
/** The number of transactions holding at least one key lock. */
long txHoldingLock();
/** The number of keys locked on the node. */
long lockedKeys();
/** The number of transactions for which node is the initiator. */
int ownerTxs();
}
{code}
For more details see in IgniteTxAdapter and IgniteTxManager.
> Implement new JMX metrics for transactions
> --
>
> Key: IGNITE-8077
> URL: https://issues.apache.org/jira/browse/IGNITE-8077
> Project: Ignite
> Issue Type: New Feature
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Labels: iep-6
>
> These additional metrics should be implemented to monitor transactions.
> {code}
> class TransactionsMXbean{
> /** The number of transactions which was commited. */
> long getTxCommited();
> /** The number of transactions which was rollbacked. */
> long getTxRollBacked();
> /** The number of transactions holding at least one key lock. */
> long getTxHoldingLock();
> /** The number of keys locked on the node. */
> long getLockedKeys();
> /** The number of transactions for which node is the initiator. */
> int getOwnerTxs();
> }
> {code}
> For more details see in IgniteTxAdapter and IgniteTxManager.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8078:
-
Description:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] partitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long walTotalSize();
/** Time of the last WAL segment rollover. */
long getWalLastSwitchTime();
}
{code}
{code}
class IgniteMxBean {
/** Returns string containing Node ID, Consistent ID, Node Order */
String getCurrentCoordinator();
}
{code}
was:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] partitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long page
[jira] [Updated] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8078:
-
Description:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] partitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long walTotalSize();
/** Time of the last WAL segment rollover. */
long getWalLastSwitchTime();
}
{code}
was:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] partitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. *
[jira] [Updated] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8078:
-
Description:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
/** Partitions currently assigned to the local node in this cache group. */
int[] partitions();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long walTotalSize();
}
{code}
was:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long walTotalSize();
}
{code}
> Add new metrics for data storage
> -
[jira] [Updated] (IGNITE-8077) Implement new JMX metrics for transactions
[
https://issues.apache.org/jira/browse/IGNITE-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-8077:
-
Description:
These additional metrics should be implemented to monitor transactions.
{code}
class TransactionsMXbean{
/** The number of transactions which was commited. */
long txCommited();
/** The number of transactions which was rollbacked. */
long txRollBacked();
/** The number of transactions holding at least one key lock. */
long txHoldingLock();
/** The number of keys locked on the node. */
long lockedKeys();
/** The number of transactions for which node is the initiator. */
int ownerTxs();
}
{code}
For more details see in IgniteTxAdapter and IgniteTxManager.
was:
These additional metrics should be implemented to monitor transactions.
{code}
class TransactionsMXbean{
/** The number of transactions which was commited. */
long txCommited();
/** The number of transactions which was rollbacked. */
long txRollBacked();
/** The number of transactions in prepared state. */
long txPrepared();
/** The number of keys locked on the node. */
long lockedKeys();
/** The number of transactions for which node is the initiator. */
int ownerTxs();
}
{code}
For more details see in IgniteTxAdapter and IgniteTxManager.
> Implement new JMX metrics for transactions
> --
>
> Key: IGNITE-8077
> URL: https://issues.apache.org/jira/browse/IGNITE-8077
> Project: Ignite
> Issue Type: New Feature
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Labels: iep-6
>
> These additional metrics should be implemented to monitor transactions.
> {code}
> class TransactionsMXbean{
> /** The number of transactions which was commited. */
> long txCommited();
> /** The number of transactions which was rollbacked. */
> long txRollBacked();
> /** The number of transactions holding at least one key lock. */
> long txHoldingLock();
> /** The number of keys locked on the node. */
> long lockedKeys();
> /** The number of transactions for which node is the initiator. */
> int ownerTxs();
> }
> {code}
> For more details see in IgniteTxAdapter and IgniteTxManager.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7657) SQL COPY: minor style fixes
[ https://issues.apache.org/jira/browse/IGNITE-7657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420310#comment-16420310 ] ASF GitHub Bot commented on IGNITE-7657: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3496 > SQL COPY: minor style fixes > --- > > Key: IGNITE-7657 > URL: https://issues.apache.org/jira/browse/IGNITE-7657 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.3, 2.4, 2.5 >Reporter: Kirill Shirokov >Assignee: Taras Ledkov >Priority: Minor > Fix For: 2.5 > > > This issue is for fixing minor style issues in a separate branch in order to > avoid spoiling other COPY-related pull requests with minor refactorings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8078) Add new metrics for data storage
[
https://issues.apache.org/jira/browse/IGNITE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-8078:
---
Description:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. */
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long walTotalSize();
}
{code}
was:
1. Create new MXbean for each index, IndexMxBean
{code}
class IndexMxBean{
/** The number of PUT operations on the index. */
long processedPuts();
/** The number of GET operations on the index. */
long processedGets();
/** The total index size in bytes. */
long getIndexSize();
/** Index name.*/
String getName();
}
{code}
2. Add new metrics for data storage and cache group.
{code}
class CacheGroupMetricsMXBean{
/** The total index size in bytes */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** CacheGroup type. PARTITIONED, REPLICATED, LOCAL.*/
String getType();
}
{code}
{code}
class DataRegionMXBean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes. */
long getTotalsize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** Total used offheap size in bytes. *
long offheapUsedSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart . */
long pagesReplaced();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
}
{code}
{code}
class DataStorageMXbean{
/** Total size in bytes for indexes. */
long getIndexesSize();
/** Total size in bytes for primary key indexes. */
long getPKIndexesSize();
/** Total size in bytes for all storages. */
long getTotalsize();
/** Total offheap size in bytes. */
long offHeapSize();
/** Total used offheap size in bytes for all data regions. */
long offheapUsedSize();
/** Total size in bytes for pure data.*/
long getDataSize();
/** The number of read pages from last restart. */
long pagesRead();
/** The number of writen pages from last restart. */
long pagesWriten();
/** The number of replaced pages from last restart. */
long pagesReplaced();
/** Total checkpoint time from last restart. */
long checkpointTotalTime();
/** Total dirty pages for the next checkpoint. */
long dirtyPagesForNextCheckpoint();
/** Total size in bytes for storage wal files. */
long walTotalSize();
}
{code}
> Add new metrics for data storage
>
>
> Key: IGNITE-8078
> URL: https://issue
[jira] [Comment Edited] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky
[
https://issues.apache.org/jira/browse/IGNITE-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420276#comment-16420276
]
Alexey Kuznetsov edited comment on IGNITE-5960 at 3/30/18 8:32 AM:
---
[~dpavlov] Hi!
Could please review the ticket or suggest somebody to review it?
Seems, [~sergey-chugunov] don't want to review it any longer
The maintener of affected code was [~sboikov].
[TC
run|https://ci.ignite.apache.org/viewLog.html?buildId=1162426&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
I rerun failed tests :
[1 rerun
|https://ci.ignite.apache.org/viewLog.html?buildId=1166871&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache5]
[2
rerun|https://ci.ignite.apache.org/viewLog.html?buildId=1166877&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteQueries2]
[3
rerun|https://ci.ignite.apache.org/viewLog.html?buildId=1166878&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteQueries]
As you can see all failed tests are flacky.
was (Author: alexey kuznetsov):
[~dpavlov] Hi!
Could please review the ticket or suggest somebody to review it?
The maintener of affected code was [~sboikov].
[TC
run|https://ci.ignite.apache.org/viewLog.html?buildId=1162426&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
I rerun failed tests :
[1 rerun
|https://ci.ignite.apache.org/viewLog.html?buildId=1166871&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache5]
[2
rerun|https://ci.ignite.apache.org/viewLog.html?buildId=1166877&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteQueries2]
[3
rerun|https://ci.ignite.apache.org/viewLog.html?buildId=1166878&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteQueries]
As you can see all failed tests are flacky.
> Ignite Continuous Query (Queries 3):
> CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic
> is flaky
> -
>
> Key: IGNITE-5960
> URL: https://issues.apache.org/jira/browse/IGNITE-5960
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.5
>
>
> According to [TC
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=6546112007182082024&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E]
> test is flaky.
> It is possible to reproduce it locally, sample run shows 9 failed tests out
> of 30 overall executed.
> Test fails with jUnit assertion check:
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :1
> Actual :0
>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.concurrentUpdatesAndQueryStart(CacheContinuousQueryConcurrentPartitionUpdateTest.java:385)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.testConcurrentUpdatesAndQueryStartTx(CacheContinuousQueryConcurrentPartitionUpdateTest.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky
[
https://issues.apache.org/jira/browse/IGNITE-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420276#comment-16420276
]
Alexey Kuznetsov commented on IGNITE-5960:
--
[~dpavlov] Hi!
Could please review the ticket or suggest somebody to review it?
The maintener of affected code was [~sboikov].
[TC
run|https://ci.ignite.apache.org/viewLog.html?buildId=1162426&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
I rerun failed tests :
[1 rerun
|https://ci.ignite.apache.org/viewLog.html?buildId=1166871&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache5]
[2
rerun|https://ci.ignite.apache.org/viewLog.html?buildId=1166877&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteQueries2]
[3
rerun|https://ci.ignite.apache.org/viewLog.html?buildId=1166878&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteQueries]
As you can see all failed tests are flacky.
> Ignite Continuous Query (Queries 3):
> CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic
> is flaky
> -
>
> Key: IGNITE-5960
> URL: https://issues.apache.org/jira/browse/IGNITE-5960
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.5
>
>
> According to [TC
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=6546112007182082024&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E]
> test is flaky.
> It is possible to reproduce it locally, sample run shows 9 failed tests out
> of 30 overall executed.
> Test fails with jUnit assertion check:
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :1
> Actual :0
>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.concurrentUpdatesAndQueryStart(CacheContinuousQueryConcurrentPartitionUpdateTest.java:385)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryConcurrentPartitionUpdateTest.testConcurrentUpdatesAndQueryStartTx(CacheContinuousQueryConcurrentPartitionUpdateTest.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7691) Provide info about DECIMAL column scale and precision
[ https://issues.apache.org/jira/browse/IGNITE-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420238#comment-16420238 ] Pavel Tupitsyn commented on IGNITE-7691: Hi [~NIzhikov], changes look good to me in gerenal, thank you. Please make sure TeamCity passes. > Provide info about DECIMAL column scale and precision > - > > Key: IGNITE-7691 > URL: https://issues.apache.org/jira/browse/IGNITE-7691 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Minor > Fix For: 2.5 > > > Currently, it impossible to obtain scale and precision of DECIMAL column from > sql table metadata. > Ignite should provide those type of meta information. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8075) .NET: withLabel, localActiveTransactions
[
https://issues.apache.org/jira/browse/IGNITE-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420235#comment-16420235
]
Pavel Tupitsyn commented on IGNITE-8075:
[~ascherbakov], your branch is for IGNITE-6827 issue, right? And that issue
talks about {{txRollbackTimeoutOnTopologyChange}} property. I'm a bit confused.
Please provide a better descriptions of APIs that are being added in Java.
> .NET: withLabel, localActiveTransactions
>
>
> Key: IGNITE-8075
> URL: https://issues.apache.org/jira/browse/IGNITE-8075
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Alexei Scherbakov
>Priority: Major
> Fix For: 2.5
>
>
> Neet to add two described method as part of .NET API.
> withLabel
> localActiveTransactions
> Java implementation is currently available in branch [1]
> [1] https://github.com/gridgain/apache-ignite/tree/ignite-6827-2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8075) .NET: withLabel, localActiveTransactions
[ https://issues.apache.org/jira/browse/IGNITE-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-8075: --- Summary: .NET: withLabel, localActiveTransactions (was: Add support for two new public methods in .NET API) > .NET: withLabel, localActiveTransactions > > > Key: IGNITE-8075 > URL: https://issues.apache.org/jira/browse/IGNITE-8075 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Alexei Scherbakov >Priority: Major > Fix For: 2.5 > > > Neet to add two described method as part of .NET API. > withLabel > localActiveTransactions > Java implementation is currently available in branch [1] > [1] https://github.com/gridgain/apache-ignite/tree/ignite-6827-2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8075) Add support for two new public methods in .NET API
[ https://issues.apache.org/jira/browse/IGNITE-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-8075: -- Assignee: (was: Pavel Tupitsyn) > Add support for two new public methods in .NET API > -- > > Key: IGNITE-8075 > URL: https://issues.apache.org/jira/browse/IGNITE-8075 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Alexei Scherbakov >Priority: Major > Fix For: 2.5 > > > Neet to add two described method as part of .NET API. > withLabel > localActiveTransactions > Java implementation is currently available in branch [1] > [1] https://github.com/gridgain/apache-ignite/tree/ignite-6827-2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
