[jira] [Updated] (IGNITE-4079) Web Console: SQL - cache name is not displayed for default cache (cache name is null) in 'show query' dialog
[ https://issues.apache.org/jira/browse/IGNITE-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4079: - Summary: Web Console: SQL - cache name is not displayed for default cache (cache name is null) in 'show query' dialog (was: Web console-SQL: cache name is not displayed for default cache (cache name is null) in 'show query' dialog) > Web Console: SQL - cache name is not displayed for default cache (cache name > is null) in 'show query' dialog > > > Key: IGNITE-4079 > URL: https://issues.apache.org/jira/browse/IGNITE-4079 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 1.8 > > > We should display ''. > # choose cache > # SCAN > # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4081) Web Console: Refactor legacy code
Alexey Kuznetsov created IGNITE-4081: Summary: Web Console: Refactor legacy code Key: IGNITE-4081 URL: https://issues.apache.org/jira/browse/IGNITE-4081 Project: Ignite Issue Type: Task Components: wizards Affects Versions: 1.7 Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Fix For: 1.8 This is a root ticket for legacy code refactorings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4082) Refactor filters registration
Alexey Kuznetsov created IGNITE-4082:
Summary: Refactor filters registration
Key: IGNITE-4082
URL: https://issues.apache.org/jira/browse/IGNITE-4082
Project: Ignite
Issue Type: Sub-task
Components: wizards
Affects Versions: 1.7
Reporter: Alexey Kuznetsov
Fix For: 1.8
Refactor filter code like:
{code}
export default ['hasPojo', [() => ({caches} = []) =>
.filter(...hasPojo)
{code}
to
{code}
export default [() => ({caches} = []) => ...
.filter('hasPojo', hasPojo)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4083) Refactor services to classes
Alexey Kuznetsov created IGNITE-4083: Summary: Refactor services to classes Key: IGNITE-4083 URL: https://issues.apache.org/jira/browse/IGNITE-4083 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.7 Reporter: Alexey Kuznetsov Fix For: 1.8 Refactor services from functions to classes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4074) Refactor async (*future) operations in PlatformTarget
[ https://issues.apache.org/jira/browse/IGNITE-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574620#comment-15574620 ] Pavel Tupitsyn commented on IGNITE-4074: Refactoring is needed in: * Compute: only ExecuteJavaTaskAsync, other methods use different mechanism * Cache (27 methods) * Messaging (2 methods) * Events (6 methods) * Services (7 methods) * Transactions (2 methods) > Refactor async (*future) operations in PlatformTarget > - > > Key: IGNITE-4074 > URL: https://issues.apache.org/jira/browse/IGNITE-4074 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Currently async operations are executed in two steps: > - start an operation (Cache.Get) > - get the future (UU.TargetListenFuture* methods) > This separation is unnecessary. See if we can perform asyn operations in one > JNI call. See how PlatformCache.OP_REBALANCE does this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4079) Web Console: SQL - cache name is not displayed for default cache (cache name is null) in 'show query' dialog
[ https://issues.apache.org/jira/browse/IGNITE-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574623#comment-15574623 ] Pavel Konstantinov commented on IGNITE-4079: Tested. > Web Console: SQL - cache name is not displayed for default cache (cache name > is null) in 'show query' dialog > > > Key: IGNITE-4079 > URL: https://issues.apache.org/jira/browse/IGNITE-4079 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 1.8 > > > We should display ''. > # choose cache > # SCAN > # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4079) Web Console: SQL - cache name is not displayed for default cache (cache name is null) in 'show query' dialog
[ https://issues.apache.org/jira/browse/IGNITE-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-4079. -- Assignee: (was: Pavel Konstantinov) > Web Console: SQL - cache name is not displayed for default cache (cache name > is null) in 'show query' dialog > > > Key: IGNITE-4079 > URL: https://issues.apache.org/jira/browse/IGNITE-4079 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Priority: Minor > Fix For: 1.8 > > > We should display ''. > # choose cache > # SCAN > # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4084) Web Console: Register lodash in frontend tests globaly.
Alexey Kuznetsov created IGNITE-4084: Summary: Web Console: Register lodash in frontend tests globaly. Key: IGNITE-4084 URL: https://issues.apache.org/jira/browse/IGNITE-4084 Project: Ignite Issue Type: Task Components: wizards Affects Versions: 1.7 Reporter: Alexey Kuznetsov Assignee: Maxim Afanasiev Fix For: 1.8 When we try to test code that depends on lodash we would get error like "ReferenceError: _ is not defined". For now we could import lodash explicitly in tested code, but better way to fix tests configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4078) Web console: pie chart is not refreshed in corner case
[ https://issues.apache.org/jira/browse/IGNITE-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-4078: Assignee: Alexey Kuznetsov > Web console: pie chart is not refreshed in corner case > -- > > Key: IGNITE-4078 > URL: https://issues.apache.org/jira/browse/IGNITE-4078 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: IGNITE-4078.png > > > # execute SCAN > # open pie chart - you should see 'scan is not supported' > # write a valid query and Execute > Observed - no pie chart was painted, only legend is visible (see attachment) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4076) Web console: can not choose a cache by clicking on it
[ https://issues.apache.org/jira/browse/IGNITE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Afanasiev reassigned IGNITE-4076: --- Assignee: Maxim Afanasiev > Web console: can not choose a cache by clicking on it > - > > Key: IGNITE-4076 > URL: https://issues.apache.org/jira/browse/IGNITE-4076 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev > > # Open SQL page > # Create a second query > # Click by cache name > In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1924) Incomplete marshaller cache rebalancing causes Grid hangs under SSL
[ https://issues.apache.org/jira/browse/IGNITE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1924: - Summary: Incomplete marshaller cache rebalancing causes Grid hangs under SSL (was: Incomplete marshaller cache rebalancing causes Grid hangs) > Incomplete marshaller cache rebalancing causes Grid hangs under SSL > --- > > Key: IGNITE-1924 > URL: https://issues.apache.org/jira/browse/IGNITE-1924 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Priority: Critical > Labels: Muted_test > Fix For: 1.8 > > > End of the log. > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > Hang on: > [11:51:56] : [org.apache.ignite:ignite-core] Thread > [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, > state=WAITING, blockCnt=0, waitCnt=3] > [11:51:56] : [org.apache.ignite:ignite-core] Lock > [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, > ownerName=null, ownerId=-1] > [11:51:56] : [org.apache.ignite:ignite-core] at > sun.misc.Unsafe.park(Native Method) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander
[jira] [Reopened] (IGNITE-1924) Incomplete marshaller cache rebalancing causes Grid hangs under SSL
[ https://issues.apache.org/jira/browse/IGNITE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reopened IGNITE-1924: -- Assignee: Anton Vinogradov > Incomplete marshaller cache rebalancing causes Grid hangs under SSL > --- > > Key: IGNITE-1924 > URL: https://issues.apache.org/jira/browse/IGNITE-1924 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > Labels: Muted_test > Fix For: 1.8 > > > End of the log. > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > Hang on: > [11:51:56] : [org.apache.ignite:ignite-core] Thread > [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, > state=WAITING, blockCnt=0, waitCnt=3] > [11:51:56] : [org.apache.ignite:ignite-core] Lock > [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, > ownerName=null, ownerId=-1] > [11:51:56] : [org.apache.ignite:ignite-core] at > sun.misc.Unsafe.park(Native Method) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:320) > [11:51:56] : [org.apache.ignite:ignite-core]
[jira] [Resolved] (IGNITE-1924) Incomplete marshaller cache rebalancing causes Grid hangs under SSL
[ https://issues.apache.org/jira/browse/IGNITE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-1924. -- > Incomplete marshaller cache rebalancing causes Grid hangs under SSL > --- > > Key: IGNITE-1924 > URL: https://issues.apache.org/jira/browse/IGNITE-1924 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Priority: Critical > Labels: Muted_test > Fix For: 1.8 > > > End of the log. > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > Hang on: > [11:51:56] : [org.apache.ignite:ignite-core] Thread > [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, > state=WAITING, blockCnt=0, waitCnt=3] > [11:51:56] : [org.apache.ignite:ignite-core] Lock > [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, > ownerName=null, ownerId=-1] > [11:51:56] : [org.apache.ignite:ignite-core] at > sun.misc.Unsafe.park(Native Method) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:320) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.GridCachePartitionExchangeManager$Excha
[jira] [Resolved] (IGNITE-1924) Incomplete marshaller cache rebalancing causes Grid hangs under SSL
[ https://issues.apache.org/jira/browse/IGNITE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-1924. -- Resolution: Fixed > Incomplete marshaller cache rebalancing causes Grid hangs under SSL > --- > > Key: IGNITE-1924 > URL: https://issues.apache.org/jira/browse/IGNITE-1924 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Critical > Labels: Muted_test > Fix For: 1.8 > > > End of the log. > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > Hang on: > [11:51:56] : [org.apache.ignite:ignite-core] Thread > [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, > state=WAITING, blockCnt=0, waitCnt=3] > [11:51:56] : [org.apache.ignite:ignite-core] Lock > [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, > ownerName=null, ownerId=-1] > [11:51:56] : [org.apache.ignite:ignite-core] at > sun.misc.Unsafe.park(Native Method) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:320) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.
[jira] [Reopened] (IGNITE-4076) Web console: can not choose a cache by clicking on it
[ https://issues.apache.org/jira/browse/IGNITE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Afanasiev reopened IGNITE-4076: - Assignee: Maxim Afanasiev (was: Pavel Konstantinov) > Web console: can not choose a cache by clicking on it > - > > Key: IGNITE-4076 > URL: https://issues.apache.org/jira/browse/IGNITE-4076 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev > > # Open SQL page > # Create a second query > # Click by cache name > In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4076) Web console: can not choose a cache by clicking on it
[ https://issues.apache.org/jira/browse/IGNITE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Afanasiev resolved IGNITE-4076. - Resolution: Fixed Assignee: Pavel Konstantinov (was: Maxim Afanasiev) Fixed. Please test. > Web console: can not choose a cache by clicking on it > - > > Key: IGNITE-4076 > URL: https://issues.apache.org/jira/browse/IGNITE-4076 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > > # Open SQL page > # Create a second query > # Click by cache name > In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4076) Web console: can not choose a cache by clicking on it
[ https://issues.apache.org/jira/browse/IGNITE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-4076. -- Assignee: (was: Pavel Konstantinov) > Web console: can not choose a cache by clicking on it > - > > Key: IGNITE-4076 > URL: https://issues.apache.org/jira/browse/IGNITE-4076 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov > > # Open SQL page > # Create a second query > # Click by cache name > In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4076) Web console: can not choose a cache by clicking on it
[ https://issues.apache.org/jira/browse/IGNITE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574992#comment-15574992 ] Pavel Konstantinov commented on IGNITE-4076: Tested. > Web console: can not choose a cache by clicking on it > - > > Key: IGNITE-4076 > URL: https://issues.apache.org/jira/browse/IGNITE-4076 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > > # Open SQL page > # Create a second query > # Click by cache name > In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4086) Binary objets: Do not use BinaryField when comparing objects with the same schema.
Vladimir Ozerov created IGNITE-4086: --- Summary: Binary objets: Do not use BinaryField when comparing objects with the same schema. Key: IGNITE-4086 URL: https://issues.apache.org/jira/browse/IGNITE-4086 Project: Ignite Issue Type: Task Components: binary Affects Versions: 1.7 Reporter: Vladimir Ozerov Fix For: 1.8 Most often we perform comparisons of objects with the same schema. When it is so, there is no need to compare them field-by-field. Instead, we should do the following: 1) Skip header 2) Skip footer 3) Compare byte-by-byte everything in between. Please ensure that byte-by-byte comparison is implemented efficiently. E.g. that we actually compare bigger chunks (e.g. 8 bytes at once). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4085) Binary objects: Do not use BinaryField when comparing objects with the same schema.
[
https://issues.apache.org/jira/browse/IGNITE-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4085:
Summary: Binary objects: Do not use BinaryField when comparing objects with
the same schema. (was: c)
> Binary objects: Do not use BinaryField when comparing objects with the same
> schema.
> ---
>
> Key: IGNITE-4085
> URL: https://issues.apache.org/jira/browse/IGNITE-4085
> Project: Ignite
> Issue Type: Task
> Components: binary
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
> Labels: performance
> Fix For: 1.8
>
>
> It is not efficient to use {{BinaryField.value}} directly when comparing
> binary objects because it leads to "materialization" of the field.
> Instead, when well-known type is met, we should simply find field start in
> both objects and perform usual byte-by-byte comparison.
> E.g., for string it will be:
> 1) Find position
> 2) Compare lengths (readInt)
> 3) Compare contents byte-by-byte.
> The same goes for other types:
> 1) Primitive arrays
> 2) UUID
> 3) Data/TimeStamp.
> Please ensure that byte-by-byte comparison is performed efficiently, e.g.
> that we compare bigger chunks (e.g. 8 bytes at once).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4085) c
[
https://issues.apache.org/jira/browse/IGNITE-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4085:
Summary: c (was: Binary objets: Compare fields of well-known types without
deserialization.)
> c
> -
>
> Key: IGNITE-4085
> URL: https://issues.apache.org/jira/browse/IGNITE-4085
> Project: Ignite
> Issue Type: Task
> Components: binary
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
> Labels: performance
> Fix For: 1.8
>
>
> It is not efficient to use {{BinaryField.value}} directly when comparing
> binary objects because it leads to "materialization" of the field.
> Instead, when well-known type is met, we should simply find field start in
> both objects and perform usual byte-by-byte comparison.
> E.g., for string it will be:
> 1) Find position
> 2) Compare lengths (readInt)
> 3) Compare contents byte-by-byte.
> The same goes for other types:
> 1) Primitive arrays
> 2) UUID
> 3) Data/TimeStamp.
> Please ensure that byte-by-byte comparison is performed efficiently, e.g.
> that we compare bigger chunks (e.g. 8 bytes at once).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4086) Binary objects: Do not use BinaryField when comparing objects with the same schema.
[ https://issues.apache.org/jira/browse/IGNITE-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4086: Summary: Binary objects: Do not use BinaryField when comparing objects with the same schema. (was: Binary objets: Do not use BinaryField when comparing objects with the same schema.) > Binary objects: Do not use BinaryField when comparing objects with the same > schema. > --- > > Key: IGNITE-4086 > URL: https://issues.apache.org/jira/browse/IGNITE-4086 > Project: Ignite > Issue Type: Task > Components: binary >Affects Versions: 1.7 >Reporter: Vladimir Ozerov > Labels: performance > Fix For: 1.8 > > > Most often we perform comparisons of objects with the same schema. When it is > so, there is no need to compare them field-by-field. Instead, we should do > the following: > 1) Skip header > 2) Skip footer > 3) Compare byte-by-byte everything in between. > Please ensure that byte-by-byte comparison is implemented efficiently. E.g. > that we actually compare bigger chunks (e.g. 8 bytes at once). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4085) Binary objets: Compare fields of well-known types without deserialization.
Vladimir Ozerov created IGNITE-4085:
---
Summary: Binary objets: Compare fields of well-known types without
deserialization.
Key: IGNITE-4085
URL: https://issues.apache.org/jira/browse/IGNITE-4085
Project: Ignite
Issue Type: Task
Components: binary
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Fix For: 1.8
It is not efficient to use {{BinaryField.value}} directly when comparing binary
objects because it leads to "materialization" of the field.
Instead, when well-known type is met, we should simply find field start in both
objects and perform usual byte-by-byte comparison.
E.g., for string it will be:
1) Find position
2) Compare lengths (readInt)
3) Compare contents byte-by-byte.
The same goes for other types:
1) Primitive arrays
2) UUID
3) Data/TimeStamp.
Please ensure that byte-by-byte comparison is performed efficiently, e.g. that
we compare bigger chunks (e.g. 8 bytes at once).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3432) Multiple IGFS on the same caches.
[ https://issues.apache.org/jira/browse/IGNITE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-3432: Assignee: Taras Ledkov > Multiple IGFS on the same caches. > - > > Key: IGNITE-3432 > URL: https://issues.apache.org/jira/browse/IGNITE-3432 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Taras Ledkov > Fix For: 1.8 > > > # Configure grid with two IGFSs which use the same caches. > # Run two server nodes. > #* Topology is runned. Written data marked in both IGFSs. > # Run client node. > #* On node start showed validation message that two IGFSs cannot use the same > caches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.
[ https://issues.apache.org/jira/browse/IGNITE-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3376: Assignee: Taras Ledkov (was: Vladimir Ozerov) > IGFS: Allow direct PROXY mode invocations. > -- > > Key: IGNITE-3376 > URL: https://issues.apache.org/jira/browse/IGNITE-3376 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > Fix For: 1.8 > > > Currently we do not have special handling for PROXY mode. So we will either > hit AssertionError during dev, or will go to incorrect code path in > productions systems. > We need to fix that - PROXY mode should be handled correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.
[
https://issues.apache.org/jira/browse/IGNITE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575425#comment-15575425
]
Taras Ledkov commented on IGNITE-3432:
--
The scenario isn't reproduced.
Please clarify your point about the scenario. Where is the problem at the {p.2}
or at the {p.3}?
- The problem had already fixed if one at the {p.2}. This is invalid
configuration. The {{IgniteCheckedException("Data/Meta cache names should be
different for different IGFS instances configuration")}} will be thrown.
- The issue is invalid if the problem at the {p.3}.
> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes.
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same
> caches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4053) Task error is always printed to the console.
[
https://issues.apache.org/jira/browse/IGNITE-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4053:
Assignee: Taras Ledkov
> Task error is always printed to the console.
>
>
> Key: IGNITE-4053
> URL: https://issues.apache.org/jira/browse/IGNITE-4053
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Minor
> Fix For: 1.8
>
>
> Currently if something wrong happens to the task, it prints error to the
> console:
> {code}
> java.lang.Throwable.printStackTrace(java.lang.Throwable$PrintStreamOrWriter)
> (line: 653)
> java.lang.Throwable.printStackTrace(java.io.PrintStream) (line: 643)
> org.apache.ignite.internal.util.IgniteUtils.error(org.apache.ignite.IgniteLogger,
> java.lang.Object, java.lang.Object, java.lang.Throwable) (line: 4171)
> org.apache.ignite.internal.util.IgniteUtils.error(org.apache.ignite.IgniteLogger,
> java.lang.Object, java.lang.Throwable) (line: 4189)
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(org.apache.ignite.lang.IgniteInClosure)
> (line: 269)
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners()
> (line: 250)
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(java.lang.Object,
> java.lang.Throwable, boolean) (line: 380)
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(java.lang.Object,
> java.lang.Throwable)
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(java.lang.Object,
> java.lang.Throwable, boolean) (line: 1475)
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(java.lang.Object,
> java.lang.Throwable) (line: 1443)
> org.apache.ignite.internal.processors.task.GridTaskWorker$4.apply() (line:
> 988)
> org.apache.ignite.internal.processors.task.GridTaskWorker$4.apply()
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(java.lang.ClassLoader,
> org.apache.ignite.lang.IgniteOutClosure) (line: 6516)
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(org.apache.ignite.compute.ComputeJobResult,
> java.util.List)
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(org.apache.ignite.internal.GridJobExecuteResponse)
> (line: 810)
> {code}
> This happens because there is no logger in the future, hence error is
> unconditionally printed to the console.
> We need to fix that. Probably we can inject logger into the task future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3432) Multiple IGFS on the same caches.
[ https://issues.apache.org/jira/browse/IGNITE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov resolved IGNITE-3432. -- Resolution: Incomplete > Multiple IGFS on the same caches. > - > > Key: IGNITE-3432 > URL: https://issues.apache.org/jira/browse/IGNITE-3432 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Taras Ledkov > Fix For: 1.8 > > > # Configure grid with two IGFSs which use the same caches. > # Run two server nodes. > #* Topology is runned. Written data marked in both IGFSs. > # Run client node. > #* On node start showed validation message that two IGFSs cannot use the same > caches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3432) Multiple IGFS on the same caches.
[
https://issues.apache.org/jira/browse/IGNITE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575425#comment-15575425
]
Taras Ledkov edited comment on IGNITE-3432 at 10/14/16 2:04 PM:
The scenario isn't reproduced.
Please clarify your point about the scenario. Where is the problem at the *p.2*
or at the *p.3*?
- The problem had already fixed if one at the *p.2*. This is invalid
configuration.
The {{IgniteCheckedException("Data/Meta cache names should be different for
different IGFS instances configuration")}} will be thrown.
- The issue is invalid if the problem at the *p.3*.
was (Author: tledkov-gridgain):
The scenario isn't reproduced.
Please clarify your point about the scenario. Where is the problem at the {p.2}
or at the {p.3}?
- The problem had already fixed if one at the {p.2}. This is invalid
configuration. The {{IgniteCheckedException("Data/Meta cache names should be
different for different IGFS instances configuration")}} will be thrown.
- The issue is invalid if the problem at the {p.3}.
> Multiple IGFS on the same caches.
> -
>
> Key: IGNITE-3432
> URL: https://issues.apache.org/jira/browse/IGNITE-3432
> Project: Ignite
> Issue Type: Bug
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vasiliy Sisko
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> # Configure grid with two IGFSs which use the same caches.
> # Run two server nodes.
> #* Topology is runned. Written data marked in both IGFSs.
> # Run client node.
> #* On node start showed validation message that two IGFSs cannot use the same
> caches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-3432) Multiple IGFS on the same caches.
[ https://issues.apache.org/jira/browse/IGNITE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reopened IGNITE-3432: -- > Multiple IGFS on the same caches. > - > > Key: IGNITE-3432 > URL: https://issues.apache.org/jira/browse/IGNITE-3432 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Taras Ledkov > Fix For: 1.8 > > > # Configure grid with two IGFSs which use the same caches. > # Run two server nodes. > #* Topology is runned. Written data marked in both IGFSs. > # Run client node. > #* On node start showed validation message that two IGFSs cannot use the same > caches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4053) Task error is always printed to the console.
[ https://issues.apache.org/jira/browse/IGNITE-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575768#comment-15575768 ] ASF GitHub Bot commented on IGNITE-4053: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1160 IGNITE-4053 Task error is always printed to the console You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4053 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1160.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 #1160 commit a4c63ae113931615e940ada2411ebce32dba5db8 Author: iveselovskiy Date: 2016-09-30T07:45:13Z IGNITE-3998: IGFS: Enabled IgfsAbstractSelfTest.testCreateConsistencyMultithreaded. This closes #1129. commit a12298c0baf19407f3110ba3c4f0aab88b67946d Author: Igor Sapego Date: 2016-09-30T08:00:51Z IGNITE-3868: ODBC: Fixed connection string parsing. This closes #1051. commit 5e7ef8644ad824b87d4797e59133eb783ff8b098 Author: vozerov-gridgain Date: 2016-10-03T07:37:25Z Merge branch 'ignite-1.6.9' into ignite-1.6.10 commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f Author: vozerov-gridgain Date: 2016-10-03T07:40:04Z IGNITE-2881: Fixed SPI queries. commit 0b66d2d7b695cf370a4b8a717844ad67742c6090 Author: sboikov Date: 2016-10-03T09:04:03Z ignite-3601 Do not check version on commit for read-only serializable transactions. commit 9f211e413332931f0fb1190744ddd7c7f38fd213 Author: tledkov-gridgain Date: 2016-10-03T09:26:12Z IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This closes #1003. commit fa698d6fcfde0006423ef009337dbef58ac62515 Author: vozerov-gridgain Date: 2016-10-03T10:33:12Z Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by multicast IP finder. commit bba019fd5076412ca43c10a32fd300b6031ccd0b Author: vozerov-gridgain Date: 2016-10-03T14:25:20Z IGNITE-3980: Processed failing tests in query suites. This closes #1137. commit a92f20b5cc75e6b80b2731da0192723526b0c1dc Author: vozerov-gridgain Date: 2016-10-04T11:10:26Z IGNITE-3597: Removed static work directory. commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1 Author: vozerov-gridgain Date: 2016-10-06T07:14:59Z IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130. commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497 Author: tledkov-gridgain Date: 2016-10-06T07:22:50Z IGNITE-3163 IGFS: Added working directory support to IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This closes #1132. commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701 Author: vozerov-gridgain Date: 2016-10-06T09:03:48Z IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This closes #903. This closes #1145. commit 952be8b995050b34379006dd6e739da3fe3b49e3 Author: Dmitriy Govorukhin Date: 2016-10-07T12:00:09Z Squashed commit of the following: commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1 Author: sboikov Date: Fri Oct 7 13:08:38 2016 +0300 minor commit 7fe88a1cb21f794ee55a176ab36d895cbf916528 Author: Dmitriy Govorukhin Date: Thu Oct 6 11:11:24 2016 +0300 ignite-update-notifier fix after review (cherry picked from commit a10d2ff) commit f2de749f958a3b18dc479f8a5517d7bf9362b933 Author: Dmitriy Govorukhin Date: Tue Oct 4 12:12:08 2016 +0300 ignite-2079-2 optimize import and change url path (cherry picked from commit 830a3cf) commit 0d1be85ad55b0aa91224690d6c112ae92e8bc0a9 Author: Dmitriy Govorukhin Date: Thu Sep 29 19:54:54 2016 +0300 update-notifier remove parse xml, now parse like properties (cherry picked from commit 9ecaa29) commit e43bca6fb4528a7fc0dcb804a74fca1c59d7468b Author: Dmitriy Govorukhin Date: Tue Sep 27 17:07:21 2016 +0300 remove dom parser (cherry picked from commit d1653b2) commit b9c776a8423471706ecb1dc6176b38f23e799077 Author: Anton Vinogradov Date: 2016-10-10T08:52:57Z IGNITE-3235 Failed to initialize primitive boolean cache property of superclass commit f9a0676fad7fd6c23e3c91c10d7e0412ccb27c06 Author: vozerov-gridgain Date: 2016-10-11T07:23:01Z IGNITE-4041: Created separate processor for thread pools and refactored IO manager. This closes #1150. commit 9a6cfce659df40b0a4624f19fd91c217b74bafea Author: nikolay_tikhonov Date: 2016-10-11T10:59:57Z IGNITE-4014 Fixed "Transaction hangs if entry processor failed during serialization". This closes #1148. commit 1938a17b01fac1e08c30011180bbcc3ed7374d83 Author: And
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575974#comment-15575974 ] Saikat Maitra commented on IGNITE-3303: --- [~avinogradov] Thank you Anton. I will check the failures. Regards Saikat > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4037) High memory consumption when executing TeraSort Hadoop example
[ https://issues.apache.org/jira/browse/IGNITE-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576038#comment-15576038 ] Ivan Veselovsky commented on IGNITE-4037: - My learning of Hadoop have led to the following solution plan: 1) We may continue to use HadoopSkipList as now, or another sorted collection, just should limit it in size. That is , we may store in memory not more than M data. 2) The data are to be partitioned by R parts , as that done now. 3) If map output exceeds 0.8 * M (the coefficient is to be configurable, similar to io.sort.spill.percent Hadoop property ), we freeze the memory colection and start spill it to disk. Meanwhile the writing is continued in another collection. This way amount of in-memory data should not exceed the configured limit, and on disk we will have a number of sorted files for each partition. 4) The spilled files need to be sent to reduce side and merged. Likely they need to be fully merged on reduce side, then sent. 5) Similarly, output obtained from different meppers is to be merged on reduce side. This functionelity can be borrowed from Hadoop implementation, with the difference that Ignite has "push" map -> reduce sending implementation, while Hadoop uses rather "pool" implementation. > High memory consumption when executing TeraSort Hadoop example > -- > > Key: IGNITE-4037 > URL: https://issues.apache.org/jira/browse/IGNITE-4037 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.6 >Reporter: Ivan Veselovsky >Assignee: Ivan Veselovsky > Fix For: 1.7 > > > When executing TeraSort Hadoop example, we observe high memory consumption > that frequently leads to cluster malfunction. > The problem can be reproduced in unit test, even with 1 node, and with not > huge input data set as 100Mb. > Dump analysis shows that memory is taken in various queues: > org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecutorService#queue > > and > task queue of > org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker#evtProcSvc > . > Since objects stored in these queues hold byte arrays of significant size, > memory if consumed very fast. > It looks like real cause of the problem is that some tasks are blocked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4011) Automatically compute hash codes for newly built binary objects
[ https://issues.apache.org/jira/browse/IGNITE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko reassigned IGNITE-4011: --- Assignee: Valentin Kulichenko (was: Alexander Paschenko) > Automatically compute hash codes for newly built binary objects > --- > > Key: IGNITE-4011 > URL: https://issues.apache.org/jira/browse/IGNITE-4011 > Project: Ignite > Issue Type: Task > Components: binary, cache >Reporter: Alexander Paschenko >Assignee: Valentin Kulichenko > Fix For: 1.8 > > > For binary keys built automatically inside SQL engine during INSERT or MERGE, > we need to compute hash codes automatically because in this case the user > does not interact with any builders and can't set hash code explicitly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3191) BinaryObjectBuilder: binary schema id depends on the order of fields addition
[
https://issues.apache.org/jira/browse/IGNITE-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-3191:
Assignee: (was: Valentin Kulichenko)
> BinaryObjectBuilder: binary schema id depends on the order of fields addition
> -
>
> Key: IGNITE-3191
> URL: https://issues.apache.org/jira/browse/IGNITE-3191
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 1.8
>
>
> Presently if an object is created using BinaryObjectBuilder then several
> BinarySchemes can be generated for the same set of fields in case when fields
> are added in a different order.
> This happens because {{LinkedHashMap}} is used underneath. However we should
> rely on order-free structure like {{TreeMap}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
