[jira] [Closed] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-586. -- > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Vladimir Ozerov > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).
[
https://issues.apache.org/jira/browse/IGNITE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-1534:
Description:
During testing changes related with IGNITE-1171 the following problem was found:
{panel}
Unhandled exception
org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for
cache (all partition nodes left the grid).
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
at io.vertx.core.impl.HAManager.(HAManager.java:147)
at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown
Source)
at
io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
at
io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown
Source)
at
io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown
Source)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745)
Caused by: class
org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
Failed to map keys for cache (all partition nodes left the grid).
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 more
{panel}
This exception occures on topology from 3 nodes that start dynamic cache with
the same configuration on all nodes and performs {{put}} operation. All 3 nodes
are alive.
The problem reproduces periodically.
was:
During testing changes related with IGNITE-1171 the following problem was found:
{panel}
Unhandled exception
org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for
cache (all partition nodes left the grid).
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
at io.vertx.core.impl.HAManager.(HAManager.java:147)
at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown
Source)
at
io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
at
io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown
Source)
at
io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown
Source)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745)
Caused by: class
org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
Failed to map keys for cache (all partition nodes
[jira] [Created] (IGNITE-1534) Failed to map keys for cache (all partition nodes left the grid).
Andrey Gura created IGNITE-1534:
---
Summary: Failed to map keys for cache (all partition nodes left
the grid).
Key: IGNITE-1534
URL: https://issues.apache.org/jira/browse/IGNITE-1534
Project: Ignite
Issue Type: Bug
Reporter: Andrey Gura
During testing changes related with IGNITE-1171 the following problem was found:
{panel}
Unhandled exception
org.apache.ignite.cache.CacheServerNotFoundException: Failed to map keys for
cache (all partition nodes left the grid).
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1612)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1744)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.getAndPut(IgniteCacheProxy.java:1043)
at io.vertx.spi.cluster.ignite.impl.MapImpl.put(MapImpl.java:85)
at io.vertx.core.impl.HAManager.(HAManager.java:147)
at io.vertx.core.impl.VertxImpl.lambda$null$143(VertxImpl.java:156)
at io.vertx.core.impl.VertxImpl$$Lambda$35/2107573573.handle(Unknown
Source)
at
io.vertx.core.net.impl.NetServerImpl.lambda$null$34(NetServerImpl.java:252)
at
io.vertx.core.net.impl.NetServerImpl$$Lambda$39/1662210125.handle(Unknown
Source)
at
io.vertx.core.impl.ContextImpl.lambda$wrapTask$20(ContextImpl.java:324)
at io.vertx.core.impl.ContextImpl$$Lambda$31/1504729381.run(Unknown
Source)
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745)
Caused by: class
org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
Failed to map keys for cache (all partition nodes left the grid).
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:808)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:422)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$100(GridNearAtomicUpdateFuture.java:73)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$1$1.run(GridNearAtomicUpdateFuture.java:406)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6427)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:788)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 more
{panel}
This exception occures on topology from 3 nodes that start dynamic cache with
the same configuration on all nodes and performs {{put}} operation. All 3 nodes
are alive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14904922#comment-14904922
]
Sergey Kozlov commented on IGNITE-973:
--
I ran test during 30 mins and got no failures. The issue fixed
p.s. I didn't find original script (may be it's a typo) and used
bin\tester\tester-win-ig-load.bat
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1523) Need to make marshaller in discovery pluggable
[
https://issues.apache.org/jira/browse/IGNITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1523:
Fix Version/s: (was: ignite-1.4)
ignite-1.5
> Need to make marshaller in discovery pluggable
> --
>
> Key: IGNITE-1523
> URL: https://issues.apache.org/jira/browse/IGNITE-1523
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: user-request
> Fix For: ignite-1.5
>
>
> Currently we always use {{JdkMarshaller}}. It can be useful to use a custom
> one. Need to add {{TcpDiscoverySpi.setMarshaller()}} method to allow this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1524) Client node throws exception when server node killed
[
https://issues.apache.org/jira/browse/IGNITE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14904045#comment-14904045
]
Semen Boikov edited comment on IGNITE-1524 at 9/23/15 6:51 AM:
---
Artem, fix is merged to ignite-1.4, please check if it reproduces for you.
was (Author: sboikov):
Aretm, fix is merged to ignite-1.4, please check if it reproduces for you.
> Client node throws exception when server node killed
>
>
> Key: IGNITE-1524
> URL: https://issues.apache.org/jira/browse/IGNITE-1524
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Artem Shutak
> Fix For: ignite-1.4
>
> Attachments: 1524.path, logs-20150922-120712.zip
>
>
> In process of working on IGNITE-1397 I've found that Ignite client node
> throws CacheException which caused by IgniteClientDisconnectedException
> (stack trace below) sometimes when I kill one server node at cluster.
> My configuration:
> - 3 server nodes
> - 2 client nodes
> - discovery configuration:
> {code}
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
> 127.0.0.1:47500
> 127.0.0.1:47501
> 127.0.0.1:47502
>
>
>
>
>
>
> {code}
> Test description:
> - client nodes make random atomic ops to cluster (pts, gets, invoke, remove)
> - the first client node has a thread which kill with -9 and start one server
> one by one. Kills every 60 seconds and run after 10 seconds.
> Client node fails not always.
> {noformat}
> javax.cache.CacheException: class
> org.apache.ignite.IgniteClientDisconnectedException: Operation has been
> cancelled (client node disconnected).
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1621)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1749)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:815)
> at
> org.apache.ignite.yardstick.cache.failover.IgniteAtomicRetriesFailoverBenchmark.test(IgniteAtomicRetriesFailoverBenchmark.java:39)
> at
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteClientDisconnectedException:
> Operation has been cancelled (client node disconnected).
> at
> org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:801)
> at
> org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:799)
> ... 6 more
> Caused by: class
> org.apache.ignite.internal.IgniteClientDisconnectedCheckedException:
> Operation has been cancelled (client node disconnected).
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager.disconnectedError(GridCacheMvccManager.java:360)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onDisconnected(GridCacheMvccManager.java:334)
> at
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext.onDisconnected(GridCacheSharedContext.java:141)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDisconnected(GridCacheProcessor.java:997)
> at
> org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:2983)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onDiscovery(GridDiscoveryManager.java:592)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2024)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2005)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1422)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1079) Implement Ignite-based cluster manager for Vert.x framework.
[
https://issues.apache.org/jira/browse/IGNITE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14903526#comment-14903526
]
Andrey Gura edited comment on IGNITE-1079 at 9/23/15 9:10 AM:
--
There are two reasons of test failing:
# After killing random node cluster manager chooses the same node as failover.
In this case failover fails but test doesn't provide handler for this
situation. I tested {{Ignite.cluster().nodes}} functionality. It always returns
right nodes list. Need additional investigation.
# While nodes handle failover after killing random node at the same moment of
time the next node is killing and parallel failover running. The test fails
because test's state changes concurrently.
Debug continues.
was (Author: agura):
There are two reasons of test failing:
# After killing random node cluster manager chooses the same node as failover.
In this case failover fails but test doesn't provide handler for this
situation. I tested {{Ignite.cluster().nodes}} functionality. It always returns
right nodes list. Nedd additional investigation.
# While nodes handle failover after killing random node at the same moment of
time the next node is killing and parallel failover running. The test fails
because test's state changes concurrently.
Debug continues.
> Implement Ignite-based cluster manager for Vert.x framework.
>
>
> Key: IGNITE-1079
> URL: https://issues.apache.org/jira/browse/IGNITE-1079
> Project: Ignite
> Issue Type: New Feature
> Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: newbie
> Fix For: ignite-1.4
>
>
> Implement Ignite-based cluster manager for Vert.x framework: http://vertx.io/
> vertx-hazelcast could be used as start point:
> https://github.com/vert-x3/vertx-hazelcast
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1536) Duplicate notification in continuous query
Valentin Kulichenko created IGNITE-1536:
---
Summary: Duplicate notification in continuous query
Key: IGNITE-1536
URL: https://issues.apache.org/jira/browse/IGNITE-1536
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Blocker
Fix For: ignite-1.4
Scenario is the following:
# Start first node with a {{REPLICATED}} cache.
# Execute non-local continuous query.
# Start second node.
# Do several puts for different keys.
Some of the notifications are duplicated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1537) Near TX prepare future is completed early for LOCAL cache
Alexey Goncharuk created IGNITE-1537:
Summary: Near TX prepare future is completed early for LOCAL cache
Key: IGNITE-1537
URL: https://issues.apache.org/jira/browse/IGNITE-1537
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.1.4
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Fix For: ignite-1.4
{{GridCacheContinuousQueryLocalSelfTest}} fails locally for me due to this
issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1536) Duplicate notification in continuous query
[
https://issues.apache.org/jira/browse/IGNITE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1536:
Labels: user-request (was: )
> Duplicate notification in continuous query
> --
>
> Key: IGNITE-1536
> URL: https://issues.apache.org/jira/browse/IGNITE-1536
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: user-request
> Fix For: ignite-1.4
>
>
> Scenario is the following:
> # Start first node with a {{REPLICATED}} cache.
> # Execute non-local continuous query.
> # Start second node.
> # Do several puts for different keys.
> Some of the notifications are duplicated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1537) Near TX prepare future is completed early for LOCAL cache
[
https://issues.apache.org/jira/browse/IGNITE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905402#comment-14905402
]
Alexey Goncharuk commented on IGNITE-1537:
--
Optimistic near tx prepare future is a compound future, however if near or
local cache is involved, it gets completed when lock keys is empty without
waiting for inner futures. This breaks logic with {{MiniFutures}} and
{{proceedPrepare}}.
I created a separate future for lock keys waiting, this seems to fix the
problem. Running TC.
> Near TX prepare future is completed early for LOCAL cache
> -
>
> Key: IGNITE-1537
> URL: https://issues.apache.org/jira/browse/IGNITE-1537
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> {{GridCacheContinuousQueryLocalSelfTest}} fails locally for me due to this
> issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14904082#comment-14904082 ] Pavel Konstantinov edited comment on IGNITE-1489 at 9/23/15 9:35 AM: - SQL page: 1) move results representation buttons (table, charts) to the result panel 2) do not hide result panel header (Page #, Results so far, Export button) in chart view 3) rework Refresh rate - on\off by clicking on the button like 'System columns' and show settings by clicking on the label (as a link) 4) add 5 minutes count down timer was (Author: pkonstantinov): SQL page: 1) move results representation buttons (table, charts) to the result panel 2) do not hide result panel header (Page #, Results so far, Export button) in chart view 3) rework Refresh rate - on\off by clicking on the button like 'System columns' and show settings by clicking on the label (as a link) > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > Attachments: ig-1489-1.png, ig-1489-2.png > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1177: --- Fix Version/s: (was: 1.1.4) ignite-1.5 > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905765#comment-14905765
]
Pavel Konstantinov commented on IGNITE-973:
---
Successfully tested in ignite-1.4
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1538) Query performance is 2 times slower in OFFHEAP_TIERED mode
[ https://issues.apache.org/jira/browse/IGNITE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-1538: Labels: performance user-request (was: user-request) > Query performance is 2 times slower in OFFHEAP_TIERED mode > -- > > Key: IGNITE-1538 > URL: https://issues.apache.org/jira/browse/IGNITE-1538 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Critical > Labels: performance, user-request > Fix For: ignite-1.5 > > > Corresponding user@ thread: > http://apache-ignite-users.70518.x6.nabble.com/SQL-Performance-indexing-performance-on-heap-vs-off-heap-td1352.html > Need to run benchmarks and investigate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-910) Assert with near-only tx cache: Cannot have more then one ready near-local candidate
[
https://issues.apache.org/jira/browse/IGNITE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905646#comment-14905646
]
Alexey Goncharuk commented on IGNITE-910:
-
Should be fixed in ignite-264. Adding the test to suite to check on TC.
> Assert with near-only tx cache: Cannot have more then one ready near-local
> candidate
>
>
> Key: IGNITE-910
> URL: https://issues.apache.org/jira/browse/IGNITE-910
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
>Assignee: Alexey Goncharuk
>Priority: Critical
>
> Added test IgniteCacheNearOnlyTxTest.testNearOnlyPutMultithreaded. Test pass,
> but there are many errors in the log:
> {noformat}
> java.lang.AssertionError: Cannot have more then one ready near-local
> candidate [c=GridCacheMvccCandidate
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254111,
> order=1431748248330], timeout=0, ts=1431748254106, threadId=181, id=282,
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null,
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250,
> nodeOrderDrId=1, globalTime=1431748254113, order=1431748248332],
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> key=KeyCacheObjectImpl [val=1, hasValBytes=true],
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
> prevVer=null, nextVer=null], cand=GridCacheMvccCandidate
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254110,
> order=1431748248323], timeout=0, ts=1431748254106, threadId=182, id=279,
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null,
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250,
> nodeOrderDrId=1, globalTime=1431748254112, order=1431748248328],
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> key=KeyCacheObjectImpl [val=1, hasValBytes=true],
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
> prevVer=null, nextVer=null], mvcc=GridCacheMvcc
> [locs=[GridCacheMvccCandidate [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001,
> ver=GridCacheVersion [topVer=43228250, nodeOrderDrId=2,
> globalTime=1431748254111, order=1431748248331], timeout=0, ts=1431748254106,
> threadId=184, id=283, topVer=AffinityTopologyVersion [topVer=-1,
> minorTopVer=0], reentry=null, otherNodeId=null, otherVer=GridCacheVersion
> [topVer=43228250, nodeOrderDrId=1, globalTime=1431748254113,
> order=1431748248333], mappedDhtNodes=null, mappedNearNodes=null,
> ownerVer=null, key=KeyCacheObjectImpl [val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
> prevVer=null, nextVer=null], GridCacheMvccCandidate
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254111,
> order=1431748248330], timeout=0, ts=1431748254106, threadId=181, id=282,
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null,
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250,
> nodeOrderDrId=1, globalTime=1431748254113, order=1431748248332],
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> key=KeyCacheObjectImpl [val=1, hasValBytes=true],
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
> prevVer=null, nextVer=null], GridCacheMvccCandidate
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254110,
> order=1431748248323], timeout=0, ts=1431748254106, threadId=182, id=279,
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null,
> otherNodeId=null, otherVer=GridCacheVersion [topVer=43228250,
> nodeOrderDrId=1, globalTime=1431748254112, order=1431748248328],
> mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> key=KeyCacheObjectImpl [val=1, hasValBytes=true],
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=0|near_local=1|removed=0,
> prevVer=null, nextVer=null], GridCacheMvccCandidate
> [nodeId=1009df79-3666-4aa3-8136-0b9afbb16001, ver=GridCacheVersion
> [topVer=43228250, nodeOrderDrId=2, globalTime=1431748254110,
> order=1431748248325], timeout=0, ts=1431748254106, threadId=180, id=280,
> topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], reentry=null,
> otherNodeId=null, otherVer=null, mappedDhtNodes=null, mappedNearNodes=null,
> ownerVer=null, key=KeyCacheObjectImpl [val=1, hasValBytes=true],
>
[jira] [Commented] (IGNITE-1536) Duplicate notification in continuous query
[
https://issues.apache.org/jira/browse/IGNITE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905665#comment-14905665
]
ASF GitHub Bot commented on IGNITE-1536:
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/104
> Duplicate notification in continuous query
> --
>
> Key: IGNITE-1536
> URL: https://issues.apache.org/jira/browse/IGNITE-1536
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: user-request
> Fix For: ignite-1.4
>
>
> Scenario is the following:
> # Start first node with a {{REPLICATED}} cache.
> # Execute non-local continuous query.
> # Start second node.
> # Do several puts for different keys.
> Some of the notifications are duplicated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
