[jira] [Updated] (IGNITE-1384) Compute job ids duplication
[ https://issues.apache.org/jira/browse/IGNITE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Setrakyan updated IGNITE-1384: -- Fix Version/s: ignite-1.5 > Compute job ids duplication > --- > > Key: IGNITE-1384 > URL: https://issues.apache.org/jira/browse/IGNITE-1384 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Sidorov > Labels: user-request > Fix For: ignite-1.5 > > > Configure custom CollisionSpi with any implemenation which keeps waiting jobs > list not empty. Execute considerable amount of tasks (e.g. 1) from 2 or > more nodes with jobs mapped to one node. > Error occurs on mapped node: "Received computation request with duplicate job > ID (could be network malfunction, source node may hang if task timeout was > not set)" > Reason: TaskGridWorker:processMappedJobs generates job ids as following: > IgniteUuid jobId = IgniteUuid.fromUuid(node.id()); > where node.id() is identifier of node the job is mapped to. So parallel > generation of job ids on different nodes leads to ids duplication. > Possible solution: use node.id() of local node in job id generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1275) 'Get' from marshaller cache hangs on topology change
[
https://issues.apache.org/jira/browse/IGNITE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov resolved IGNITE-1275.
--
Fixed issue with topology wait in case of response with invalidPartitions.
> 'Get' from marshaller cache hangs on topology change
>
>
> Key: IGNITE-1275
> URL: https://issues.apache.org/jira/browse/IGNITE-1275
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Observed this hang on TC in test
> IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetries:
> {noformat}
> [11:27:17] : [org.apache.ignite:ignite-core] Thread
> [name="ignite-#91721%sys-dht.IgniteCachePutRetryTransactionalSelfTest2%",
> id=115833, state=WAITING, blockCnt=0, waitCnt=3]
> [11:27:17] : [org.apache.ignite:ignite-core] Lock
> [object=o.a.i.i.processors.cache.distributed.dht.GridPartitionedGetFuture@4a555b67,
> ownerName=null, ownerId=-1]
> [11:27:17] : [org.apache.ignite:ignite-core] at
> sun.misc.Unsafe.park(Native Method)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4404)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1448)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.MarshallerContextImpl.className(MarshallerContextImpl.java:139)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:166)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:252)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:246)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.lang.IgniteBiTuple.readExternal(IgniteBiTuple.java:268)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:451)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:746)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:252)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readLinkedList(OptimizedObjectInputStream.java:610)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:227)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:236)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.transactions.IgniteTxEntry.unmarshal(IgniteTxEntry.java:749)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheMessage.unmarshalTx(GridCacheMessage.ja
[jira] [Updated] (IGNITE-647) org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs
[ https://issues.apache.org/jira/browse/IGNITE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-647: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1345 > org.apache.ignite.IgniteCacheAffinitySelfTest.testAffinity() hangs > -- > > Key: IGNITE-647 > URL: https://issues.apache.org/jira/browse/IGNITE-647 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov >Assignee: Alexey Goncharuk >Priority: Blocker > Attachments: threaddump.txt > > > 1-2 runs out of ~10 local runs hanged for me -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration
[
https://issues.apache.org/jira/browse/IGNITE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734363#comment-14734363
]
Enrico Olivelli commented on IGNITE-1374:
-
I will try to reproduce, maybe I did an error doing copy&paste.
Working code (with PeerClassLoadingEnabled=false, and the KeyPrefixPredicate
class deployed on all the nodes):
{code}
ScanQuery scan = new ScanQuery<>(new
KeyPrefixPredicate(prefix));
Set keys = new HashSet<>();
try (QueryCursor> cursor =
getCache().query(scan)) {
for (Cache.Entry entry : cursor) {
String key = entry.getKey();
if (key.startsWith(prefix)) { // inutile
String remaining = key.substring(prefixlenght);
keys.add(remaining);
}
}
return keys;
}
public class KeyPrefixPredicate implements IgniteBiPredicate,
Serializable {
private static final long serialVersionUID = 1;
private final String prefix;
public KeyPrefixPredicate(String prefix) {
this.prefix = prefix;
}
@Override
public boolean apply(String e1, Object e2) {
return e1 != null && e1.startsWith(prefix);
}
}
{code}
Code with the error (PeerClassLoadingEnabled=true, using lambda expression):
{code}
String prefix = "myprefix...";
ScanQuery scan = new ScanQuery<>((key, value) -> {
return key.startsWith(prefix);
});
Set keys = new HashSet<>();
try (QueryCursor> cursor =
getCache().query(scan)) {
for (Cache.Entry entry : cursor) {
String key = entry.getKey();
if (key.startsWith(prefix)) { // redundant
String remaining = key.substring(prefixlenght);
keys.add(remaining);
}
}
return keys;
}
{code}
The error is not throw on the thead which execute the example but is printed on
on system log (maybe System.err or System.out, not in a "logger"), maybe it
could be a system wiade UncatchedExceptionHandler
> Error org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type during a cache iteration
> -
>
> Key: IGNITE-1374
> URL: https://issues.apache.org/jira/browse/IGNITE-1374
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Enrico Olivelli
>Assignee: Anton Vinogradov
>Priority: Blocker
> Labels: user-request
>
> Using ignite 1.3.0-incubating I get this error while issuing an iteration on
> a cache
> {code}
> Set keys = new HashSet<>();
> for (Iterator> it = cache.iterator();
> it.hasNext();) {
> String key = it.next().getKey();
> if (key.startsWith(prefix)) {
> keys.add(remaining);
> }
> }
> {code}
> This is the error
> {code}
> GRAVE: Failed to process message
> [senderId=a9548f63-2ac4-4600-a593-dfcdca71aa38, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse
> [finished=false, reqId=934, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:507)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:232)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1018)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2086)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:942)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:911)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1123) Instability and broken topology when multiple server and client nodes are restarted
[
https://issues.apache.org/jira/browse/IGNITE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734370#comment-14734370
]
Denis Magda commented on IGNITE-1123:
-
Quite similar topology related issues arise when executing
{{testMultiThreadedClientsRestart}} that only restarts clients node from
multiple threads.
{noformat}
[09:31:15]W: [org.apache.ignite:ignite-core]
java.lang.AssertionError: lastVer=961, newVer=963, locNode=TcpDiscoveryNode
[id=601f5093-d79b-413a-989f-17c319cce006, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:0], discPort=0, order=963, intOrder=0,
lastExchangeTime=1441693875034, loc=true, ver=1.4.0#19700101-sha1:,
isClient=true], msg=TcpDiscoveryNodeAddFinishedMessage
[nodeId=601f5093-d79b-413a-989f-17c319cce006, super=TcpDiscoveryAbstractMessage
[sndNodeId=40033004-b638-488e-9883-4fde13a9f004,
id=eacf7bbaf41-1044072a-f3d6-4d26-94cd-31c6325e3001,
verifierNodeId=1044072a-f3d6-4d26-94cd-31c6325e3001, topVer=963, pendingIdx=0,
isClient=false]]
[09:31:15]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ClientImpl.updateTopologyHistory(ClientImpl.java:720)
[09:31:15]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ClientImpl.access$2700(ClientImpl.java:118)
[09:31:15]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1656)
[09:31:15]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1537)
[09:31:15]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1465)
[09:31:15]W: [org.apache.ignite:ignite-core]at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{noformat}
We have to revisit client discovery SPI impl.
> Instability and broken topology when multiple server and client nodes are
> restarted
> ---
>
> Key: IGNITE-1123
> URL: https://issues.apache.org/jira/browse/IGNITE-1123
> Project: Ignite
> Issue Type: Bug
> Components: clients, general
>Affects Versions: sprint-7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> The bug is always reproduced with
> TcpDiscoveryMultiThreadedTest.testMultiThreadedClientsServersRestart.
> The test starts multiple servers and clients and then restarts them from
> multiple thread. At some point it will lead to one or all of the following:
> 1) Broken topology on a client side:
> {noformat}
> java.lang.AssertionError: TcpDiscoveryNodeAddFinishedMessage
> [nodeId=70576075-b528-43f4-b490-33d079dc7007,
> super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> id=8f7e19c8e41-10b88275-1868-4faf-9ae0-d61d627b1001,
> verifierNodeId=10b88275-1868-4faf-9ae0-d61d627b1001, topVer=89, pendingIdx=0,
> isClient=false]]
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.updateTopologyHistory(ClientImpl.java:589)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$2500(ClientImpl.java:48)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1370)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1227)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processClientReconnectMessage(ClientImpl.java:1552)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1235)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1197)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> 2) Clients segmentation that is not properly processed by
> GridCachePartionExchangeManager and that leads to the test hang:
> {noformat}
> Still waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
> reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=60b736c0-a2ad-4465-a3c1-7656e1fa9006, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:0], discPort=0, order=255, intOrder=0, loc=true,
> ver=1.4.1#19700101-sha1:, isClient=true], topVer=255,
> nodeId8=60b736c0, msg=null, type=NODE_JOINED, tstamp=1436877471568],
> rcvdIds=GridConcurrentHashSet
> [elements=[7098ffd9-f81b-40bf-9b9e-b0935d394007,
> 30b30924-a9e7-45fb-9aeb-361bbb482003, 00d7e953-ce8b-45e0-a1f3-be7a6dea1000,
> 301559de-a129-4b85-852f-f8325649f003, 70
[jira] [Closed] (IGNITE-1275) 'Get' from marshaller cache hangs on topology change
[
https://issues.apache.org/jira/browse/IGNITE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov closed IGNITE-1275.
Assignee: (was: Semen Boikov)
> 'Get' from marshaller cache hangs on topology change
>
>
> Key: IGNITE-1275
> URL: https://issues.apache.org/jira/browse/IGNITE-1275
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Observed this hang on TC in test
> IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetries:
> {noformat}
> [11:27:17] : [org.apache.ignite:ignite-core] Thread
> [name="ignite-#91721%sys-dht.IgniteCachePutRetryTransactionalSelfTest2%",
> id=115833, state=WAITING, blockCnt=0, waitCnt=3]
> [11:27:17] : [org.apache.ignite:ignite-core] Lock
> [object=o.a.i.i.processors.cache.distributed.dht.GridPartitionedGetFuture@4a555b67,
> ownerName=null, ownerId=-1]
> [11:27:17] : [org.apache.ignite:ignite-core] at
> sun.misc.Unsafe.park(Native Method)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4404)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1448)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.MarshallerContextImpl.className(MarshallerContextImpl.java:139)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:166)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:252)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:246)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.lang.IgniteBiTuple.readExternal(IgniteBiTuple.java:268)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:451)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:746)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:252)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readLinkedList(OptimizedObjectInputStream.java:610)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:227)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:236)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.transactions.IgniteTxEntry.unmarshal(IgniteTxEntry.java:749)
> [11:27:17] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheMessage.unmarshalTx(GridCacheMessage.java:367)
> [11:27:17] : [org.apache.ignite:ignite-core] at
>
[jira] [Updated] (IGNITE-1123) Instability and broken topology when multiple server and client nodes are restarted
[
https://issues.apache.org/jira/browse/IGNITE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-1123:
-
Issue Type: Sub-task (was: Bug)
Parent: IGNITE-1345
> Instability and broken topology when multiple server and client nodes are
> restarted
> ---
>
> Key: IGNITE-1123
> URL: https://issues.apache.org/jira/browse/IGNITE-1123
> Project: Ignite
> Issue Type: Sub-task
> Components: clients, general
>Affects Versions: sprint-7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> The bug is always reproduced with
> TcpDiscoveryMultiThreadedTest.testMultiThreadedClientsServersRestart.
> The test starts multiple servers and clients and then restarts them from
> multiple thread. At some point it will lead to one or all of the following:
> 1) Broken topology on a client side:
> {noformat}
> java.lang.AssertionError: TcpDiscoveryNodeAddFinishedMessage
> [nodeId=70576075-b528-43f4-b490-33d079dc7007,
> super=TcpDiscoveryAbstractMessage [sndNodeId=null,
> id=8f7e19c8e41-10b88275-1868-4faf-9ae0-d61d627b1001,
> verifierNodeId=10b88275-1868-4faf-9ae0-d61d627b1001, topVer=89, pendingIdx=0,
> isClient=false]]
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.updateTopologyHistory(ClientImpl.java:589)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$2500(ClientImpl.java:48)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1370)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1227)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processClientReconnectMessage(ClientImpl.java:1552)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1235)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1197)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> 2) Clients segmentation that is not properly processed by
> GridCachePartionExchangeManager and that leads to the test hang:
> {noformat}
> Still waiting for initial partition map exchange
> [fut=GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
> reassign=false, discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=60b736c0-a2ad-4465-a3c1-7656e1fa9006, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:0], discPort=0, order=255, intOrder=0, loc=true,
> ver=1.4.1#19700101-sha1:, isClient=true], topVer=255,
> nodeId8=60b736c0, msg=null, type=NODE_JOINED, tstamp=1436877471568],
> rcvdIds=GridConcurrentHashSet
> [elements=[7098ffd9-f81b-40bf-9b9e-b0935d394007,
> 30b30924-a9e7-45fb-9aeb-361bbb482003, 00d7e953-ce8b-45e0-a1f3-be7a6dea1000,
> 301559de-a129-4b85-852f-f8325649f003, 7078cd7a-e6b9-4bed-b829-a2e792a0c007,
> 20de002e-7e98-4e55-b25f-d873e25db002, 00c444ad-b221-4695-9a6d-5ea529779000,
> 40dc3691-7b20-41d7-a436-65ad27f74004, 308f0e4a-507a-4da6-b086-bdecc08e1003,
> 20b1d488-7aa1-41d7-ac0b-e8730002, 00da0ab2-9441-4cc2-b787-c34dcf6a2000,
> 4096e7dd-e3fe-4704-9d11-3b267430e004, 1059ba84-4ca7-4d8f-9563-b90334d48001]],
> rmtIds=[30b30924-a9e7-45fb-9aeb-361bbb482003,
> 20de002e-7e98-4e55-b25f-d873e25db002, 4096e7dd-e3fe-4704-9d11-3b267430e004,
> 00c444ad-b221-4695-9a6d-5ea529779000], exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=255, minorTopVer=0], nodeId=60b736c0,
> evt=NODE_JOINED], init=true, ready=false, replied=false, added=true,
> initFut=GridFutureAdapter [resFlag=2, res=true, startTime=1436877471578,
> endTime=1436877471578, ignoreInterrupts=false, lsnr=null, state=DONE],
> topSnapshot=null, lastVer=null, partReleaseFut=null, skipPreload=true,
> clientOnlyExchange=true, oldest=20de002e-7e98-4e55-b25f-d873e25db002,
> oldestOrder=254, evtLatch=0, remaining=[], super=GridFutureAdapter
> [resFlag=0, res=null, startTime=1436877471578, endTime=0,
> ignoreInterrupts=false, lsnr=null, state=INIT]]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests
[
https://issues.apache.org/jira/browse/IGNITE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-1377:
-
Issue Type: Sub-task (was: Bug)
Parent: IGNITE-1345
> Portable metadata update on changing topology causes hangs in tests
> ---
>
> Key: IGNITE-1377
> URL: https://issues.apache.org/jira/browse/IGNITE-1377
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Alexey Goncharuk
>
> I removed metadata update on for objects not defined in configuration (this
> is not an introduced bug, it existed before) because it causes portable
> failover suite to hang.
> Need to investigate further the cause of the hang and unmute
> {{testNoConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-829) [Test] BaseH2CompareQueryTest # testCrossCache was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-829: --- Assignee: Artem Shutak Artem, BaseH2CompareQueryTest.testCrossCache does not fail for me, please take a look. If it does not fail anymore please remove TODO from it, enable and unmute on TC. Thanks > [Test] BaseH2CompareQueryTest # testCrossCache was disabled. > > > Key: IGNITE-829 > URL: https://issues.apache.org/jira/browse/IGNITE-829 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Artem Shutak > Labels: failedtest > > BaseH2CompareQueryTest # testCrossCache was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration
[
https://issues.apache.org/jira/browse/IGNITE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1374:
-
Attachment: QueryResponseTest.java
> Error org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type during a cache iteration
> -
>
> Key: IGNITE-1374
> URL: https://issues.apache.org/jira/browse/IGNITE-1374
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Enrico Olivelli
>Assignee: Anton Vinogradov
>Priority: Blocker
> Labels: user-request
> Attachments: QueryResponseTest.java
>
>
> Using ignite 1.3.0-incubating I get this error while issuing an iteration on
> a cache
> {code}
> Set keys = new HashSet<>();
> for (Iterator> it = cache.iterator();
> it.hasNext();) {
> String key = it.next().getKey();
> if (key.startsWith(prefix)) {
> keys.add(remaining);
> }
> }
> {code}
> This is the error
> {code}
> GRAVE: Failed to process message
> [senderId=a9548f63-2ac4-4600-a593-dfcdca71aa38, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse
> [finished=false, reqId=934, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:507)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:232)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1018)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2086)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:942)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:911)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration
[
https://issues.apache.org/jira/browse/IGNITE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734463#comment-14734463
]
Anton Vinogradov commented on IGNITE-1374:
--
Enrico,
I've updated my test and still can not reproduce error.
Could you please check my test (see attachment) and attach runnable solution
(for example simple maven project) produces error?
> Error org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type during a cache iteration
> -
>
> Key: IGNITE-1374
> URL: https://issues.apache.org/jira/browse/IGNITE-1374
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Enrico Olivelli
>Assignee: Anton Vinogradov
>Priority: Blocker
> Labels: user-request
> Attachments: QueryResponseTest.java
>
>
> Using ignite 1.3.0-incubating I get this error while issuing an iteration on
> a cache
> {code}
> Set keys = new HashSet<>();
> for (Iterator> it = cache.iterator();
> it.hasNext();) {
> String key = it.next().getKey();
> if (key.startsWith(prefix)) {
> keys.add(remaining);
> }
> }
> {code}
> This is the error
> {code}
> GRAVE: Failed to process message
> [senderId=a9548f63-2ac4-4600-a593-dfcdca71aa38, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse
> [finished=false, reqId=934, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:507)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:232)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1018)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2086)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:942)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:911)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-613) [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails
[ https://issues.apache.org/jira/browse/IGNITE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734470#comment-14734470 ] Semen Boikov commented on IGNITE-613: - Test was created to check that internal resources are properly cleaned in case of node initiated query failed. It should be rewritten since qeries implementation was completely changed. Test scenario: - start new client node - client node executes query which consists of several pages but gets only first page - stop client node - all resources related to client query should be cleared on server node > [Test] IgniteCacheReplicatedQuerySelfTest # testNodeLeft fails > -- > > Key: IGNITE-613 > URL: https://issues.apache.org/jira/browse/IGNITE-613 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > IgniteCacheReplicatedQuerySelfTest #testNodeLeft test fails by unknown > reason (should be unmuted on TC after fix). > Test works long and fails after. Should be enabled after fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1386) IPC semaphores are not released on server endpoint abrupt stop
[
https://issues.apache.org/jira/browse/IGNITE-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1386:
Affects Version/s: ignite-1.4
> IPC semaphores are not released on server endpoint abrupt stop
> --
>
> Key: IGNITE-1386
> URL: https://issues.apache.org/jira/browse/IGNITE-1386
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
> Fix For: ignite-1.5
>
>
> {{IpcSharedMemoryCrashDetectionSelfTest.testIgfsClientServerInteractionsUponServerKilling}}
> stops a server endpoint abruptly with 'kill' command and right after that
> start a new endpoint.
> The test expects that such a flow will release all previously allocated
> memory segments and semaphores.
> In fact, only memory segments are released while semaphores stay in the
> system. However, the test successfully ends.
> Steps to reproduce:
> - check existing semaphores with {{ipcs -s}};
> - start the test on Linux or Mac OS;
> - call {{ipcs -s}} and you will see that semaphores hasn't been released.
> In addition, TeamCity agents fail a test suite because of this reason from
> time to time
> {noformat}
> [16:14:03][Step 7/7] Failing build because of remaining IPC resources.
> [16:14:03][Step 7/7] Process exited with code 1
> [16:14:03][Step 7/7] Step Check IPC / Clean up (Command Line) failed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1386) IPC semaphores are not released on server endpoint abrupt stop
Denis Magda created IGNITE-1386:
---
Summary: IPC semaphores are not released on server endpoint abrupt
stop
Key: IGNITE-1386
URL: https://issues.apache.org/jira/browse/IGNITE-1386
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Denis Magda
Priority: Critical
Fix For: ignite-1.5
{{IpcSharedMemoryCrashDetectionSelfTest.testIgfsClientServerInteractionsUponServerKilling}}
stops a server endpoint abruptly with 'kill' command and right after that
start a new endpoint.
The test expects that such a flow will release all previously allocated memory
segments and semaphores.
In fact, only memory segments are released while semaphores stay in the system.
However, the test successfully ends.
Steps to reproduce:
- check existing semaphores with {{ipcs -s}};
- start the test on Linux or Mac OS;
- call {{ipcs -s}} and you will see that semaphores hasn't been released.
In addition, TeamCity agents fail a test suite because of this reason from time
to time
{noformat}
[16:14:03][Step 7/7] Failing build because of remaining IPC resources.
[16:14:03][Step 7/7] Process exited with code 1
[16:14:03][Step 7/7] Step Check IPC / Clean up (Command Line) failed
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-829) [Test] BaseH2CompareQueryTest # testCrossCache was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak closed IGNITE-829. --- > [Test] BaseH2CompareQueryTest # testCrossCache was disabled. > > > Key: IGNITE-829 > URL: https://issues.apache.org/jira/browse/IGNITE-829 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Artem Shutak > Labels: failedtest > > BaseH2CompareQueryTest # testCrossCache was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-829) [Test] BaseH2CompareQueryTest # testCrossCache was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak resolved IGNITE-829. - Resolution: Won't Fix Test case has been enabled by Sem as long as test case already fixed. Merged at ignite-1.4. > [Test] BaseH2CompareQueryTest # testCrossCache was disabled. > > > Key: IGNITE-829 > URL: https://issues.apache.org/jira/browse/IGNITE-829 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Artem Shutak > Labels: failedtest > > BaseH2CompareQueryTest # testCrossCache was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart
Pavel Tupitsyn created IGNITE-1387: --- Summary: Platform .Net: cache.Invoke does not work with portable objects without Java counterpart Key: IGNITE-1387 URL: https://issues.apache.org/jira/browse/IGNITE-1387 Project: Ignite Issue Type: Bug Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: ignite-1.4 PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject instead of readObjectDetached, so it tries to deserialize portable objects from other platforms, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-580) [Test] Grid cannot stop with ongoing cache operations
[ https://issues.apache.org/jira/browse/IGNITE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-580. --- > [Test] Grid cannot stop with ongoing cache operations > - > > Key: IGNITE-580 > URL: https://issues.apache.org/jira/browse/IGNITE-580 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > org.gridgain.grid.kernal.GridStartStopSelfTest#testStopWhileInUse > see GG-7704 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-580) [Test] Grid cannot stop with ongoing cache operations
[ https://issues.apache.org/jira/browse/IGNITE-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-580. - Resolution: Fixed Enabled test, this functionality should work now. > [Test] Grid cannot stop with ongoing cache operations > - > > Key: IGNITE-580 > URL: https://issues.apache.org/jira/browse/IGNITE-580 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > org.gridgain.grid.kernal.GridStartStopSelfTest#testStopWhileInUse > see GG-7704 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart
[ https://issues.apache.org/jira/browse/IGNITE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734518#comment-14734518 ] ASF GitHub Bot commented on IGNITE-1387: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/74 IGNITE-1387 Platform .Net: cache.Invoke does not work with portable objects without Java counterpart You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1387 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/74.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 #74 commit 2326bb53fd62104b8816fe6da6f388963dc268cd Author: ptupitsyn Date: 2015-09-08T09:29:34Z IGNITE-1387 Platform .Net: cache.Invoke does not work with portable objects without Java counterpart > Platform .Net: cache.Invoke does not work with portable objects without Java > counterpart > > > Key: IGNITE-1387 > URL: https://issues.apache.org/jira/browse/IGNITE-1387 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.4 > > > PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject > instead of readObjectDetached, so it tries to deserialize portable objects > from other platforms, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1369) CacheClientPortableQueryExample need to update javadoc
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-1369:
---
Assignee: Denis Magda (was: Vasilisa Sidorova)
> CacheClientPortableQueryExample need to update javadoc
> --
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Minor
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1369:
Priority: Critical (was: Minor)
> CacheClientPortableQueryExample fails when remote node is started without
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1369:
Summary: CacheClientPortableQueryExample fails when remote node is started
without test objects in classpath (was: CacheClientPortableQueryExample need
to update javadoc)
> CacheClientPortableQueryExample fails when remote node is started without
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Minor
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reopened IGNITE-1369:
-
> CacheClientPortableQueryExample fails when remote node is started without
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Critical
> Fix For: ignite-1.4
>
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1369:
Fix Version/s: (was: ignite-1.4)
> CacheClientPortableQueryExample fails when remote node is started without
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Critical
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734540#comment-14734540
]
Denis Magda commented on IGNITE-1369:
-
We mustn't alter the documentation. This is a bug in the code.
In fact a remote node doesn't need to have a real object class in its classpath
in order to respond to SQL queries over portable data.
As I see this functionality was broken in the middle of June 2015 in GG
codebase and now the bug migrated to Ignite.
> CacheClientPortableQueryExample fails when remote node is started without
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Critical
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-806) [Test] GridCachePartitionedTxMultiThreadedSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734551#comment-14734551 ] Semen Boikov commented on IGNITE-806: - Now only GridCachePartitionedTxMultiThreadedSelfTest.testOptimisticSerializableCommitMultithreaded fails for me, enabled others testcases. > [Test] GridCachePartitionedTxMultiThreadedSelfTest hangs > > > Key: IGNITE-806 > URL: https://issues.apache.org/jira/browse/IGNITE-806 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > See gg-4066. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-808) [Test] GridReplicatedTxPreloadTest fails
[ https://issues.apache.org/jira/browse/IGNITE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-808: Fix Version/s: ignite-1.5 > [Test] GridReplicatedTxPreloadTest fails > > > Key: IGNITE-808 > URL: https://issues.apache.org/jira/browse/IGNITE-808 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: failedtest > Fix For: ignite-1.5 > > > GridReplicatedTxPreloadTest fails. > See gg-7434 already fixed, but tests fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-808) [Test] GridReplicatedTxPreloadTest fails
[ https://issues.apache.org/jira/browse/IGNITE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-808: --- Assignee: Semen Boikov > [Test] GridReplicatedTxPreloadTest fails > > > Key: IGNITE-808 > URL: https://issues.apache.org/jira/browse/IGNITE-808 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: failedtest > Fix For: ignite-1.5 > > > GridReplicatedTxPreloadTest fails. > See gg-7434 already fixed, but tests fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-808) [Test] GridReplicatedTxPreloadTest fails
[ https://issues.apache.org/jira/browse/IGNITE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-808: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1345 > [Test] GridReplicatedTxPreloadTest fails > > > Key: IGNITE-808 > URL: https://issues.apache.org/jira/browse/IGNITE-808 > Project: Ignite > Issue Type: Sub-task >Reporter: Artem Shutak >Assignee: Semen Boikov > Labels: failedtest > Fix For: ignite-1.5 > > > GridReplicatedTxPreloadTest fails. > See gg-7434 already fixed, but tests fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1385) Confused warning about portable marshaller
[
https://issues.apache.org/jira/browse/IGNITE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-1385.
--
Assignee: (was: Pavel Konstantinov)
Successfully tested in version 1.4
> Confused warning about portable marshaller
> --
>
> Key: IGNITE-1385
> URL: https://issues.apache.org/jira/browse/IGNITE-1385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Priority: Trivial
> Fix For: ignite-1.4
>
>
> I'm set
> {code}
>
> class="org.apache.ignite.marshaller.portable.PortableMarshaller"/>
>
> {code}
> start the node and got warning:
> {code}
> [WARNING][main][GridCachePluginProvider]
> CacheConfiguration.isKeepPortableInStore() configuration property will be
> ignored because PortableMarshaller is not used
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-114) Value is not loaded from store for invoke in transactional cache
[ https://issues.apache.org/jira/browse/IGNITE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-114: Fix Version/s: ignite-1.5 > Value is not loaded from store for invoke in transactional cache > > > Key: IGNITE-114 > URL: https://issues.apache.org/jira/browse/IGNITE-114 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-1 >Reporter: Semen Boikov >Assignee: Alexey Goncharuk > Fix For: ignite-1.5 > > > Added test IgniteCacheInvokeReadThroughTest. Value is not in cache but exists > in store, when invoke EntryProcessor is executed on backup it gets null value > instead of value loaded from store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1388) Platform .Net: cache.Invoke result in async mode should have an error flag
Pavel Tupitsyn created IGNITE-1388: --- Summary: Platform .Net: cache.Invoke result in async mode should have an error flag Key: IGNITE-1388 URL: https://issues.apache.org/jira/browse/IGNITE-1388 Project: Ignite Issue Type: Bug Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: ignite-1.4 In async mode we either write a result directly, or use EntryProcessorExceptionWriter in case of an error. It is impossible to discern an error from good result on the receiving end. Need to write a flag first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart
[ https://issues.apache.org/jira/browse/IGNITE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1387: --- Assignee: Pavel Tupitsyn (was: Vladimir Ozerov) > Platform .Net: cache.Invoke does not work with portable objects without Java > counterpart > > > Key: IGNITE-1387 > URL: https://issues.apache.org/jira/browse/IGNITE-1387 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.4 > > > PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject > instead of readObjectDetached, so it tries to deserialize portable objects > from other platforms, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart
[ https://issues.apache.org/jira/browse/IGNITE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1387: --- Assignee: Vladimir Ozerov (was: Pavel Tupitsyn) > Platform .Net: cache.Invoke does not work with portable objects without Java > counterpart > > > Key: IGNITE-1387 > URL: https://issues.apache.org/jira/browse/IGNITE-1387 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: ignite-1.4 > > > PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject > instead of readObjectDetached, so it tries to deserialize portable objects > from other platforms, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1349) CachePutAllFailoverTxTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-1349. Assignee: (was: Alexey Goncharuk) > CachePutAllFailoverTxTest hangs > --- > > Key: IGNITE-1349 > URL: https://issues.apache.org/jira/browse/IGNITE-1349 > Project: Ignite > Issue Type: Sub-task > Components: cache >Affects Versions: ignite-1.4 >Reporter: Semen Boikov >Priority: Blocker > Fix For: ignite-1.4 > > Attachments: 1349.patch > > > Test CachePutAllFailoverTxTest executes cache.putAll concurrently with node > start/stop. After some time it fails because of there are some transactions > which can not finish prepare step. Hang reproduces if size of map for putAll > is large ehough (~100). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart
[ https://issues.apache.org/jira/browse/IGNITE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734572#comment-14734572 ] ASF GitHub Bot commented on IGNITE-1387: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/74 > Platform .Net: cache.Invoke does not work with portable objects without Java > counterpart > > > Key: IGNITE-1387 > URL: https://issues.apache.org/jira/browse/IGNITE-1387 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: ignite-1.4 > > > PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject > instead of readObjectDetached, so it tries to deserialize portable objects > from other platforms, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1387) Platform .Net: cache.Invoke does not work with portable objects without Java counterpart
[ https://issues.apache.org/jira/browse/IGNITE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1387. --- > Platform .Net: cache.Invoke does not work with portable objects without Java > counterpart > > > Key: IGNITE-1387 > URL: https://issues.apache.org/jira/browse/IGNITE-1387 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: ignite-1.4 > > > PlatformCacheEntryProcessorImpl.readResultAndUpdateEntry uses readObject > instead of readObjectDetached, so it tries to deserialize portable objects > from other platforms, -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1388) Platform .Net: cache.Invoke result in async mode should have an error flag
[ https://issues.apache.org/jira/browse/IGNITE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734576#comment-14734576 ] ASF GitHub Bot commented on IGNITE-1388: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/75 IGNITE-1388 Platform .Net: cache.Invoke result in async mode should have an error flag You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1388 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/75.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 #75 commit 57555af62c93bdc8e012c1be7b6c6edd4d9d2ebe Author: ptupitsyn Date: 2015-09-08T10:25:18Z IGNITE-1388 Platform .Net: cache.Invoke result in async mode should have an error flag > Platform .Net: cache.Invoke result in async mode should have an error flag > -- > > Key: IGNITE-1388 > URL: https://issues.apache.org/jira/browse/IGNITE-1388 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.4 > > > In async mode we either write a result directly, or use > EntryProcessorExceptionWriter in case of an error. It is impossible to > discern an error from good result on the receiving end. Need to write a flag > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1388) Platform .Net: cache.Invoke result in async mode should have an error flag
[ https://issues.apache.org/jira/browse/IGNITE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734585#comment-14734585 ] ASF GitHub Bot commented on IGNITE-1388: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/75 > Platform .Net: cache.Invoke result in async mode should have an error flag > -- > > Key: IGNITE-1388 > URL: https://issues.apache.org/jira/browse/IGNITE-1388 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.4 > > > In async mode we either write a result directly, or use > EntryProcessorExceptionWriter in case of an error. It is impossible to > discern an error from good result on the receiving end. Need to write a flag > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1388) Platform .Net: cache.Invoke result in async mode should have an error flag
[ https://issues.apache.org/jira/browse/IGNITE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-1388. --- > Platform .Net: cache.Invoke result in async mode should have an error flag > -- > > Key: IGNITE-1388 > URL: https://issues.apache.org/jira/browse/IGNITE-1388 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.4 > > > In async mode we either write a result directly, or use > EntryProcessorExceptionWriter in case of an error. It is impossible to > discern an error from good result on the receiving end. Need to write a flag > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1388) Platform .Net: cache.Invoke result in async mode should have an error flag
[ https://issues.apache.org/jira/browse/IGNITE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-1388. - Resolution: Fixed > Platform .Net: cache.Invoke result in async mode should have an error flag > -- > > Key: IGNITE-1388 > URL: https://issues.apache.org/jira/browse/IGNITE-1388 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.4 > > > In async mode we either write a result directly, or use > EntryProcessorExceptionWriter in case of an error. It is impossible to > discern an error from good result on the receiving end. Need to write a flag > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1389) GridCacheAbstractFullApiSelfTest.testWithSkipStore fails periodically on different configuration
Denis Magda created IGNITE-1389:
---
Summary: GridCacheAbstractFullApiSelfTest.testWithSkipStore fails
periodically on different configuration
Key: IGNITE-1389
URL: https://issues.apache.org/jira/browse/IGNITE-1389
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: ignite-1.4
Reporter: Denis Magda
Assignee: Denis Magda
The test fails on different configurations in different places.
As an example, this is a stack trace for
{{GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore}}
configuration
{noformat}
junit.framework.AssertionFailedError: expected:<-1> but was:<21>
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:86)
at junit.framework.TestCase.assertEquals(TestCase.java:253)
at
org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4534)
at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-583) [Test] Need to create test that checks cache queue contents for consistency.
[ https://issues.apache.org/jira/browse/IGNITE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-583. - Resolution: Fixed Fixed muted tests. Also there are already tests for queue consistency, so close this issue. > [Test] Need to create test that checks cache queue contents for consistency. > > > Key: IGNITE-583 > URL: https://issues.apache.org/jira/browse/IGNITE-583 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > See SPT-2 support ticket, we need to add test for customer scenario to make > sure queue contents obtained by different methods are consistent across > nodes. > Ask Alexey Zlobin for details. > see GG-4807 > Next test(s) should be unmuted on TC: GridCacheQueueMultiNodeAbstractSelfTest > # testIterator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-583) [Test] Need to create test that checks cache queue contents for consistency.
[ https://issues.apache.org/jira/browse/IGNITE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-583. --- > [Test] Need to create test that checks cache queue contents for consistency. > > > Key: IGNITE-583 > URL: https://issues.apache.org/jira/browse/IGNITE-583 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > See SPT-2 support ticket, we need to add test for customer scenario to make > sure queue contents obtained by different methods are consistent across > nodes. > Ask Alexey Zlobin for details. > see GG-4807 > Next test(s) should be unmuted on TC: GridCacheQueueMultiNodeAbstractSelfTest > # testIterator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-805) [Test] Need to create multi-threaded tests for full API on GridCache
[ https://issues.apache.org/jira/browse/IGNITE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-805: --- Assignee: Anton Vinogradov > [Test] Need to create multi-threaded tests for full API on GridCache > > > Key: IGNITE-805 > URL: https://issues.apache.org/jira/browse/IGNITE-805 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Anton Vinogradov > Labels: failedtest > > See GG-708 > We have multi-node tesgts, but are there multi-threaded tests? Multi-threaded > tests should be for both, one node and multiple nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1113) GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails
[
https://issues.apache.org/jira/browse/IGNITE-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-1113:
---
Assignee: Andrey Gura
> GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails
> -
>
> Key: IGNITE-1113
> URL: https://issues.apache.org/jira/browse/IGNITE-1113
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Andrey Gura
>
> Next tests fail in multi jvm mode:
> GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired
> GridCacheAtomicNearOnlyMultiJvmP2PDisabledFullApiSelfTest.testEvictExpired
> Need to investigate.
> Log:
> {noformat}
> /home/ashutak/java/jdk7u75/bin/java
> -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:36703,suspend=y,server=n
> -ea
> -javaagent:/home/ashutak/Programms/idea-IC-139.659.2/plugins/Groovy/lib/agent/gragent.jar
> -Dfile.encoding=UTF-8 -classpath
> /home/ashutak/Programms/idea-IC-139.659.2/lib/idea_rt.jar:/home/ashutak/Programms/idea-IC-139.659.2/plugins/junit/lib/junit-rt.jar:/home/ashutak/java/jdk7u75/jre/lib/management-agent.jar:/home/ashutak/java/jdk7u75/jre/lib/javaws.jar:/home/ashutak/java/jdk7u75/jre/lib/deploy.jar:/home/ashutak/java/jdk7u75/jre/lib/rt.jar:/home/ashutak/java/jdk7u75/jre/lib/jce.jar:/home/ashutak/java/jdk7u75/jre/lib/jsse.jar:/home/ashutak/java/jdk7u75/jre/lib/resources.jar:/home/ashutak/java/jdk7u75/jre/lib/plugin.jar:/home/ashutak/java/jdk7u75/jre/lib/jfxrt.jar:/home/ashutak/java/jdk7u75/jre/lib/jfr.jar:/home/ashutak/java/jdk7u75/jre/lib/charsets.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/zipfs.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/dnsns.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/sunjce_provider.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/sunec.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/localedata.jar:/home/ashutak/java/jdk7u75/jre/lib/ext/sunpkcs11.jar:/home/ashutak/dev/incubator-ignite/modules/core/target/test-classes:/home/ashutak/dev/incubator-ignite/modules/core/target/classes:/home/ashutak/.m2/repository/javax/cache/cache-api/1.0.0/cache-api-1.0.0.jar:/home/ashutak/.m2/repository/mx4j/mx4j-tools/3.0.1/mx4j-tools-3.0.1.jar:/home/ashutak/.m2/repository/commons-dbcp/commons-dbcp/1.4/commons-dbcp-1.4.jar:/home/ashutak/.m2/repository/commons-pool/commons-pool/1.5.4/commons-pool-1.5.4.jar:/home/ashutak/.m2/repository/com/thoughtworks/xstream/xstream/1.4.8/xstream-1.4.8.jar:/home/ashutak/.m2/repository/xmlpull/xmlpull/1.1.3.1/xmlpull-1.1.3.1.jar:/home/ashutak/.m2/repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.jar:/home/ashutak/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar:/home/ashutak/.m2/repository/org/hsqldb/hsqldb/1.8.0.10/hsqldb-1.8.0.10.jar:/home/ashutak/.m2/repository/com/h2database/h2/1.3.175/h2-1.3.175.jar:/home/ashutak/.m2/repository/org/mockito/mockito-all/1.9.5/mockito-all-1.9.5.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-servlets/9.2.11.v20150529/jetty-servlets-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-continuation/9.2.11.v20150529/jetty-continuation-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-http/9.2.11.v20150529/jetty-http-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-util/9.2.11.v20150529/jetty-util-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-io/9.2.11.v20150529/jetty-io-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.11.v20150529/jetty-webapp-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-xml/9.2.11.v20150529/jetty-xml-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-servlet/9.2.11.v20150529/jetty-servlet-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-security/9.2.11.v20150529/jetty-security-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/org/eclipse/jetty/jetty-server/9.2.11.v20150529/jetty-server-9.2.11.v20150529.jar:/home/ashutak/.m2/repository/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar:/home/ashutak/.m2/repository/com/esotericsoftware/kryo/kryo/2.20/kryo-2.20.jar:/home/ashutak/.m2/repository/com/esotericsoftware/reflectasm/reflectasm/1.07/reflectasm-1.07-shaded.jar:/home/ashutak/.m2/repository/org/ow2/asm/asm/4.0/asm-4.0.jar:/home/ashutak/.m2/repository/com/esotericsoftware/minlog/minlog/1.2/minlog-1.2.jar:/home/ashutak/.m2/repository/org/objenesis/objenesis/1.2/objenesis-1.2.jar:/home/ashutak/.m2/repository/c3p0/c3p0/0.9.1/c3p0-0.9.1.jar:/home/ashutak/.m2/repository/com/google/guava/guava/14.0.1/guava-14.0.1.jar:/home/ashutak/.m2/repository/net/sf/json-lib/json-lib/2.4/json-lib-2.4-jdk15.jar:/home/ashutak/.m2/repository/commons-beanutils/commons-beanutils/1.8.0/commons-beanutils-1.8.0.jar:/home/ashutak/.m2/repository/commons-colle
[jira] [Assigned] (IGNITE-1112) Atomic cache #get method returns old value if near cache enabled after second putAll.
[
https://issues.apache.org/jira/browse/IGNITE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-1112:
---
Assignee: Andrey Gura (was: Semen Boikov)
> Atomic cache #get method returns old value if near cache enabled after second
> putAll.
> -
>
> Key: IGNITE-1112
> URL: https://issues.apache.org/jira/browse/IGNITE-1112
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Andrey Gura
>
> These tests failed:
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll
> GridCacheAtomicNearEnabledFairAffinityMultiJvmFullApiSelfTest.testPutAllPutAll
>
> These tests work fine in one jvm, but fails in multi-JVM case.
> Looks like, second putAll does not update data at near cache and get method
> returns old value. But iteration from cache return actual data.
> See ignite-648-putAll branch with more debug information.
> Original log for
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll.
> {noformat}
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> 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:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridCachePartitionedMultiNodeFullApiSelfTest.testPutAllPutAll(GridCachePartitionedMultiNodeFullApiSelfTest.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1618)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1561)
> --- Stdout: ---
> [17:59:33,524][INFO ][main][root] >>> Starting test: testPutAllPutAll <<<
> [17:59:33,527][INFO ][test-runner][root] > Grid0:
> 00ac324c-cfd0-4433-b00b-1048858b6000
> [17:59:33,528][INFO ][test-runner][root] > Grid1:
> 0a0c6919-127f-4d44-988d-8a236d033379
> [17:59:33,530][INFO ][test-runner][root] > Grid2:
> 17e5a787-5b00-4c68-88ea-cf0e393fefd1
> [17:59:33,531][INFO ][test-runner][root] > Grid3:
> d63de793-e754-4849-826e-2f43669385ba
> [17:59:33,544][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,544][INFO][ignite-#12%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$10
> [17:59:33,736][INFO ][test-runner][root] >>> Before second put.
> [17:59:33,736][INFO ][test-runner][GridDeploymentLocalStore] Class locally
> deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,741][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,741][INFO][ignite-#16%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,757][INFO ][test-runner][root] >>> After second put.
> [17:59:33,766][INFO ][main][root] >>> Stopping test: testPutAllPutAll in 240
> ms <<<
> [17:59:33,766][INFO ][main][root] Checking grid: 0
> [17:59:33,787][INFO ][main][root] Size after [idx=0, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries
> []]
> [17:59:33,787][INFO ][main][root] Checking grid: 1
> [17:59:33,812][INFO ][main][root] Size after [idx=1, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,815][INFO ][main][root] Checking grid: 2
> [17:59:33,839][INFO ][main][root] Size after [idx=2, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,842][INFO ][main][root] Checking grid: 3
> [17:59:33,866][INFO ][main][root] Size after [idx=3, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> --- Stderr: ---
> [17:59:33,765][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at
[jira] [Updated] (IGNITE-1093) Rebalancing with default parameters is very slow
[ https://issues.apache.org/jira/browse/IGNITE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1093: - Fix Version/s: (was: ignite-1.4) ignite-1.5 > Rebalancing with default parameters is very slow > > > Key: IGNITE-1093 > URL: https://issues.apache.org/jira/browse/IGNITE-1093 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Pavel Konstantinov >Assignee: Anton Vinogradov >Priority: Critical > Fix For: ignite-1.5 > > Attachments: Plot_ThroughputLatencyProbe_01.png, rebalancing.zip > > > # Start one node with partitioned cache with one backup. > # Load into the cache 40billions of keys using DataStreamer > # Start second node on the same host -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-614) Race in preloading/unswapping
[ https://issues.apache.org/jira/browse/IGNITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-614: Fix Version/s: (was: ignite-1.4) ignite-1.5 > Race in preloading/unswapping > - > > Key: IGNITE-614 > URL: https://issues.apache.org/jira/browse/IGNITE-614 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Anton Vinogradov >Priority: Critical > Fix For: ignite-1.5 > > > During unswap entry is removed from swap then unswap listener is notified, > and this logic in preload supply worker: > - register unswap listener > - iterater over heap > - iterate over swap > - remove unswap listener > - iterate over entries recorded by unswap listener > There is a race: entry is removed from unswap, listener is not notified yet, > at this moment supply worker removes unswap listener. > These tests fail from time to time because entry can be missed during > preloading: > GridCacheSwapPreloadSelfTest.testSwapPartitionedMultithreaded > GridCacheSwapPreloadSelfTest.testSwapReplicatedMultithreaded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1040) NPE if indexing fails with exception
[
https://issues.apache.org/jira/browse/IGNITE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1040:
-
Fix Version/s: (was: ignite-1.4)
ignite-1.5
> NPE if indexing fails with exception
>
>
> Key: IGNITE-1040
> URL: https://issues.apache.org/jira/browse/IGNITE-1040
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: ignite-1.5
>
>
> If cache start process fails with exception during indexing, it doesn't
> actually stop and fails with NPE because some other components were not
> started.
> {code}
> Jun 19, 2015 11:44:26 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=1], nodeId=8aec2f87, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Property with name 'id'
> already exists.
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$TypeDescriptor.addProperty(GridQueryProcessor.java:1736)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotationsInClass(GridQueryProcessor.java:978)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotation(GridQueryProcessor.java:1017)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processAnnotationsInClass(GridQueryProcessor.java:976)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.processKeyAndValueClasses(GridQueryProcessor.java:210)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:163)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:242)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:867)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1450)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1372)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:735)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:458)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:997)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:744)
> Jun 19, 2015 11:44:26 AM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Runtime error caught during grid runnable execution: GridWorker
> [name=partition-exchanger, gridName=null, finished=false, isCancelled=false,
> hashCode=1158985979, interrupted=false, runner=exchange-worker-#49%null%]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1519)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:851)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:52)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:313)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:632)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:997)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:744)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-828) [Test] GridIndexingSpiAbstractSelfTest # testResultReuse was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-828. - Resolution: Won't Fix Removed test, it is not valid anymore. > [Test] GridIndexingSpiAbstractSelfTest # testResultReuse was disabled. > -- > > Key: IGNITE-828 > URL: https://issues.apache.org/jira/browse/IGNITE-828 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridIndexingSpiAbstractSelfTest # testResultReuse was disabled. It has to be > fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1230) Add a boolean flag that will indicate that rebalance in progress or not
[ https://issues.apache.org/jira/browse/IGNITE-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1230: - Fix Version/s: (was: ignite-1.4) ignite-1.5 > Add a boolean flag that will indicate that rebalance in progress or not > --- > > Key: IGNITE-1230 > URL: https://issues.apache.org/jira/browse/IGNITE-1230 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexey Kuznetsov >Assignee: Anton Vinogradov > Fix For: ignite-1.5 > > > It will be useful in some cases to check single boolean flag instead of > looping over partitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1231) Show more details in node log when rebalancing started / finished.
[ https://issues.apache.org/jira/browse/IGNITE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-1231: - Fix Version/s: (was: ignite-1.4) ignite-1.5 > Show more details in node log when rebalancing started / finished. > -- > > Key: IGNITE-1231 > URL: https://issues.apache.org/jira/browse/IGNITE-1231 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexey Kuznetsov >Assignee: Anton Vinogradov > Fix For: ignite-1.5 > > > Current implementation just show cache name and elapsed time, but it will be > useful if we will print such info as: > how many partitions will be moved and on what node. > You can add more info if there is something to add. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1021) There isn't $IGNITE_HOME/docs/javadoc/resources directory
[
https://issues.apache.org/jira/browse/IGNITE-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1021:
-
Fix Version/s: (was: ignite-1.4)
ignite-1.5
> There isn't $IGNITE_HOME/docs/javadoc/resources directory
> --
>
> Key: IGNITE-1021
> URL: https://issues.apache.org/jira/browse/IGNITE-1021
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: sprint-6
> Environment: jdk1.7.0_71
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Minor
> Fix For: ignite-1.5
>
> Attachments: LinkCheckerResults.html
>
>
> Steps for reproduce:
> 1. Build ignite from sources:
> {noformat} mvn clean package -DskipTests -Prelease,lgpl -Dscala-2.10
> {noformat}
> 2. Check links in
> {noformat}$IGNITE_HOME/docs/javadoc{noformat}
> (result file in attachment).
> LinkChecker doesn't find
> {noformat}$IGNITE_HOME/docs/javadoc/resources directory{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-828) [Test] GridIndexingSpiAbstractSelfTest # testResultReuse was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-828. --- > [Test] GridIndexingSpiAbstractSelfTest # testResultReuse was disabled. > -- > > Key: IGNITE-828 > URL: https://issues.apache.org/jira/browse/IGNITE-828 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridIndexingSpiAbstractSelfTest # testResultReuse was disabled. It has to be > fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-618) binary release should be buildable without git, but revision should stay
[ https://issues.apache.org/jira/browse/IGNITE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-618: Fix Version/s: (was: ignite-1.4) ignite-1.5 > binary release should be buildable without git, but revision should stay > > > Key: IGNITE-618 > URL: https://issues.apache.org/jira/browse/IGNITE-618 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Anton Vinogradov > Fix For: ignite-1.5 > > > Probably, this may help - > http://git-scm.com/book/it/v2/Customizing-Git-Git-Attributes#Keyword-Expansion -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-424) Update success flag is not checked in atomic cache
[
https://issues.apache.org/jira/browse/IGNITE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-424:
Fix Version/s: (was: ignite-1.4)
ignite-1.5
> Update success flag is not checked in atomic cache
> --
>
> Key: IGNITE-424
> URL: https://issues.apache.org/jira/browse/IGNITE-424
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-2
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
> Fix For: ignite-1.5
>
>
> It looks suspicious {{GridDhtAtomicCache.updatePartialBatch}} calls
> interceptor even if update was not successful.
> This code needs to be reviewed, tested and fixed appropriately if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes
[ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-584: Description: Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; Also see todos here GridCacheSetFailoverAbstractSelfTest was: First, create query failover test then let's see the results. see GG-7952 Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; Also see todos here GridCacheSetFailoverAbstractSelfTest > Need to make sure that scan query returns consistent results on topology > changes > > > Key: IGNITE-584 > URL: https://issues.apache.org/jira/browse/IGNITE-584 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest > testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; > Also see todos here GridCacheSetFailoverAbstractSelfTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes
[ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-584: Summary: Need to make sure that scan query returns consistent results on topology changes (was: [Test] Need to make sure that cache query returns consistent results on topology changes) > Need to make sure that scan query returns consistent results on topology > changes > > > Key: IGNITE-584 > URL: https://issues.apache.org/jira/browse/IGNITE-584 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > First, create query failover test then let's see the results. > see GG-7952 > Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest > testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; > Also see todos here GridCacheSetFailoverAbstractSelfTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes
[ https://issues.apache.org/jira/browse/IGNITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-584: Description: Consistent results on topology changes was implemented for sql queries, but looks like it still does not work for scan queries. This affects 'cache set' tests since set uses scan query for set iteration (to be unmuted on TC): GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; Also see todos here GridCacheSetFailoverAbstractSelfTest was: Next test(s) should be unmuted on TC: GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and testNodeJoinsAndLeavesCollocated; Also see todos here GridCacheSetFailoverAbstractSelfTest > Need to make sure that scan query returns consistent results on topology > changes > > > Key: IGNITE-584 > URL: https://issues.apache.org/jira/browse/IGNITE-584 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > Consistent results on topology changes was implemented for sql queries, but > looks like it still does not work for scan queries. > This affects 'cache set' tests since set uses scan query for set iteration > (to be unmuted on TC): > GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and > testNodeJoinsAndLeavesCollocated; > Also see todos here GridCacheSetFailoverAbstractSelfTest -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-803) [Test] DataStructures failover tests fail with partitioned cache
[ https://issues.apache.org/jira/browse/IGNITE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734626#comment-14734626 ] Semen Boikov commented on IGNITE-803: - Need to look at GridCachePartitionedDataStructuresFailoverSelfTest after IGNITE-264 is fixed. > [Test] DataStructures failover tests fail with partitioned cache > > > Key: IGNITE-803 > URL: https://issues.apache.org/jira/browse/IGNITE-803 > Project: Ignite > Issue Type: Bug > Environment: See GG-2699 >Reporter: Artem Shutak > Labels: failedtest > > See GG-2699 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-803) [Test] DataStructures failover tests fail with partitioned cache
[ https://issues.apache.org/jira/browse/IGNITE-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734642#comment-14734642 ] Semen Boikov commented on IGNITE-803: - Looks like this is the same issue as IGNITE-801, need to check GridCacheReplicatedDataStructuresFailoverSelfTest after this one is fixed. > [Test] DataStructures failover tests fail with partitioned cache > > > Key: IGNITE-803 > URL: https://issues.apache.org/jira/browse/IGNITE-803 > Project: Ignite > Issue Type: Bug > Environment: See GG-2699 >Reporter: Artem Shutak > Labels: failedtest > > See GG-2699 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-170) GridCachePartitionedAtomicSetFailoverSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-170: --- Assignee: Semen Boikov > GridCachePartitionedAtomicSetFailoverSelfTest > - > > Key: IGNITE-170 > URL: https://issues.apache.org/jira/browse/IGNITE-170 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Irina Vasilinets >Assignee: Semen Boikov > > GridCachePartitionedAtomicSetFailoverSelfTest.testNodeRestart fails sometimes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-170) GridCachePartitionedAtomicSetFailoverSelfTest
[ https://issues.apache.org/jira/browse/IGNITE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734646#comment-14734646 ] Semen Boikov commented on IGNITE-170: - Test does not fail for me, unmuted it, will monitor TC. > GridCachePartitionedAtomicSetFailoverSelfTest > - > > Key: IGNITE-170 > URL: https://issues.apache.org/jira/browse/IGNITE-170 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Irina Vasilinets >Assignee: Semen Boikov > > GridCachePartitionedAtomicSetFailoverSelfTest.testNodeRestart fails sometimes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-802) [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
[ https://issues.apache.org/jira/browse/IGNITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-802: -- Assignee: Denis Magda > [Test] GridCachePartitionedQueueEntryMoveSelfTest.testQueue > --- > > Key: IGNITE-802 > URL: https://issues.apache.org/jira/browse/IGNITE-802 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Denis Magda > Labels: failedtest > > The test had been already fixed (see GG-5620), but it was not uncommented > after. Now it fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1390) Use custom classes in failover tests instead of strings/primitives
Semen Boikov created IGNITE-1390: Summary: Use custom classes in failover tests instead of strings/primitives Key: IGNITE-1390 URL: https://issues.apache.org/jira/browse/IGNITE-1390 Project: Ignite Issue Type: Sub-task Components: cache Reporter: Semen Boikov Fix For: ignite-1.5 Now most of failover tests use cache with JDK types (string, primitives), need to change tests to use some custom classes instead. This will help to find issues with marshaller cache. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1192) Provide integration with Spring Data
[ https://issues.apache.org/jira/browse/IGNITE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734788#comment-14734788 ] Vikrant Navalgund commented on IGNITE-1192: --- Hello All, I was held up in some important work for the last 3 weeks, will start working on this ticket now. > Provide integration with Spring Data > > > Key: IGNITE-1192 > URL: https://issues.apache.org/jira/browse/IGNITE-1192 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.1.4 >Reporter: Valentin Kulichenko >Assignee: Vikrant Navalgund >Priority: Minor > Labels: Newbie > > Spring Data docs: > * http://docs.spring.io/spring-data/data-commons/docs/current/reference/html/ > * http://docs.spring.io/spring-data/data-commons/docs/current/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1192) Provide integration with Spring Data
[ https://issues.apache.org/jira/browse/IGNITE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikrant Navalgund updated IGNITE-1192: -- Fix Version/s: ignite-1.5 > Provide integration with Spring Data > > > Key: IGNITE-1192 > URL: https://issues.apache.org/jira/browse/IGNITE-1192 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.1.4 >Reporter: Valentin Kulichenko >Assignee: Vikrant Navalgund >Priority: Minor > Labels: Newbie > Fix For: ignite-1.5 > > > Spring Data docs: > * http://docs.spring.io/spring-data/data-commons/docs/current/reference/html/ > * http://docs.spring.io/spring-data/data-commons/docs/current/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-264) Queue failover tests fail in transactional cache
[
https://issues.apache.org/jira/browse/IGNITE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734798#comment-14734798
]
Semen Boikov commented on IGNITE-264:
-
Reviewed, looks good, have minor comments:
- in GridDhtTransactionalCacheAdapter.lockAllAsync force key request was
removed, so GridEmbeddedFuture is not needed. Also noticed (not related to this
change) that there is the same unneeded GridEmbeddedFuture in
IgniteTxHandler.prepareColocatedTx
- new added method is not used:
GridDhtTxPrepareFuture.originatingNodeHasNearCache
- in PortableContext.registerUserClassDescriptor parameter 'registerMetadata'
is not used, is it ok?
> Queue failover tests fail in transactional cache
>
>
> Key: IGNITE-264
> URL: https://issues.apache.org/jira/browse/IGNITE-264
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> See {{GridCachePartitionedQueueFailoverDataConsistencySelfTest}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-818) [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled
[ https://issues.apache.org/jira/browse/IGNITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-818. - Resolution: Fixed Removed test (it was not a real test, just some demonstration). > [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled > > > Key: IGNITE-818 > URL: https://issues.apache.org/jira/browse/IGNITE-818 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridSuppressedExceptionSelfTest # testStackTrace was disabled. It has to be > fixed or deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-818) [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled
[ https://issues.apache.org/jira/browse/IGNITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-818. --- > [Test] GridSuppressedExceptionSelfTest # testStackTrace was disabled > > > Key: IGNITE-818 > URL: https://issues.apache.org/jira/browse/IGNITE-818 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridSuppressedExceptionSelfTest # testStackTrace was disabled. It has to be > fixed or deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1389) GridCacheAbstractFullApiSelfTest.testWithSkipStore fails periodically on different configuration
[
https://issues.apache.org/jira/browse/IGNITE-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734828#comment-14734828
]
Denis Magda commented on IGNITE-1389:
-
The issue is really hard to reproduce locally.
There should be a race condition that causes the bug because 'skipStore' flag
seems to be passed properly to all the places participating in requests.
However, figured out that when a cache projection with skipStore enabled
returns a wrong value it doesn't retrieve it from a storage. Looks like a near
cache or something else is not cleaned for such projections.
> GridCacheAbstractFullApiSelfTest.testWithSkipStore fails periodically on
> different configuration
>
>
> Key: IGNITE-1389
> URL: https://issues.apache.org/jira/browse/IGNITE-1389
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Denis Magda
>
> The test fails on different configurations in different places.
> As an example, this is a stack trace for
> {{GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore}}
> configuration
> {noformat}
> junit.framework.AssertionFailedError: expected:<-1> but was:<21>
> 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:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testWithSkipStore(GridCacheAbstractFullApiSelfTest.java:4534)
> at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-823) [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-823. --- > [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. > - > > Key: IGNITE-823 > URL: https://issues.apache.org/jira/browse/IGNITE-823 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. It has to > be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-823) [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-823. - Resolution: Fixed This is performance test which is supposed to be run manually, moved it to separate class (GridUnsafeMemoryPerformanceTest). > [Test] GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. > - > > Key: IGNITE-823 > URL: https://issues.apache.org/jira/browse/IGNITE-823 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > > GridUnsafeMemorySelfTest # testGuardedOpsPerformance was disabled. It has to > be fixed or removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734837#comment-14734837
]
Andrey Gura commented on IGNITE-1016:
-
Force update is needed only if {{excludeNeighbors == false}}. Otherwise we risk
to assign partition to neighbor node during force update.
Code from {{AffinityUtils}} are moved to {{GridCacheUtils}}. PR updated.
> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Andrey Gura
> Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for
> {{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-1016:
---
Assignee: Valentin Kulichenko (was: Andrey Gura)
> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for
> {{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1391) Platform .Net: Messaging.RemoteListen causes deadlock when remote node interop is initializing
Pavel Tupitsyn created IGNITE-1391: --- Summary: Platform .Net: Messaging.RemoteListen causes deadlock when remote node interop is initializing Key: IGNITE-1391 URL: https://issues.apache.org/jira/browse/IGNITE-1391 Project: Ignite Issue Type: Bug Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Priority: Critical Fix For: ignite-1.4 * when node joins the topology, interop processor is not yet ready (Ignite instance is not created in .Net) * When that node receives a remote message listener, UnmanagedCallbacks.MessagingFilterCreate gets called, and it blocks on "_initEvent.Wait()" * This blocks whole messaging mechanism, so interop processor initialization can't be completed We need to: * Override onKernalStart in PlatformProcessorImpl and call platform.onStart from there * In .Net, release _initEvent from that callback -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-805) [Test] Need to create multi-threaded tests for full API on GridCache
[ https://issues.apache.org/jira/browse/IGNITE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-805. - Resolution: Fixed Tests fixed & unmuted. Merged to master and 1.4 > [Test] Need to create multi-threaded tests for full API on GridCache > > > Key: IGNITE-805 > URL: https://issues.apache.org/jira/browse/IGNITE-805 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Anton Vinogradov > Labels: failedtest > > See GG-708 > We have multi-node tesgts, but are there multi-threaded tests? Multi-threaded > tests should be for both, one node and multiple nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-805) [Test] Need to create multi-threaded tests for full API on GridCache
[ https://issues.apache.org/jira/browse/IGNITE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov closed IGNITE-805. --- > [Test] Need to create multi-threaded tests for full API on GridCache > > > Key: IGNITE-805 > URL: https://issues.apache.org/jira/browse/IGNITE-805 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Anton Vinogradov > Labels: failedtest > > See GG-708 > We have multi-node tesgts, but are there multi-threaded tests? Multi-threaded > tests should be for both, one node and multiple nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1127) Query with result size more then one page doesn't increase Query executions count metric
[ https://issues.apache.org/jira/browse/IGNITE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734881#comment-14734881 ] Andrey Gura commented on IGNITE-1127: - PR updated because of merge conflicts. > Query with result size more then one page doesn't increase Query executions > count metric > - > > Key: IGNITE-1127 > URL: https://issues.apache.org/jira/browse/IGNITE-1127 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Pavel Konstantinov >Assignee: Yakov Zhdanov > Fix For: ignite-1.4 > > Attachments: master_d9acbd1_ignite-1127.patch > > > Queries for partitioned caches and limited page size doesn't increase > executions count metric in case if not all records was actually fetched by > client code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches
[ https://issues.apache.org/jira/browse/IGNITE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734899#comment-14734899 ] ASF GitHub Bot commented on IGNITE-1383: GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/76 IGNITE-1383 Ability to use apply-pull-request.sh script for non-master branches https://issues.apache.org/jira/browse/IGNITE-1383 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ashutakGG/incubator-ignite ignite-1383-script Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/76.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 #76 commit 108dd8f9721b80a5355bd0b472037276ad7d4c5f Author: ashutak Date: 2015-09-08T14:30:15Z ignite-1383: Fixed. > Need to have ability to use apply-pull-request.sh script for non-master > branches > > > Key: IGNITE-1383 > URL: https://issues.apache.org/jira/browse/IGNITE-1383 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak > > Sometimes it's need to apply patch to non-master branch. So, it need to have > ability to use apply-pull-request.sh script for non-master branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches
[ https://issues.apache.org/jira/browse/IGNITE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735103#comment-14735103 ] ASF GitHub Bot commented on IGNITE-1383: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/76 > Need to have ability to use apply-pull-request.sh script for non-master > branches > > > Key: IGNITE-1383 > URL: https://issues.apache.org/jira/browse/IGNITE-1383 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Artem Shutak > > Sometimes it's need to apply patch to non-master branch. So, it need to have > ability to use apply-pull-request.sh script for non-master branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches
[ https://issues.apache.org/jira/browse/IGNITE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Tikhonov closed IGNITE-1383. > Need to have ability to use apply-pull-request.sh script for non-master > branches > > > Key: IGNITE-1383 > URL: https://issues.apache.org/jira/browse/IGNITE-1383 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Nikolay Tikhonov > > Sometimes it's need to apply patch to non-master branch. So, it need to have > ability to use apply-pull-request.sh script for non-master branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches
[ https://issues.apache.org/jira/browse/IGNITE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735117#comment-14735117 ] Nikolay Tikhonov commented on IGNITE-1383: -- Reviewed. Merged. Thank you for your contribution! > Need to have ability to use apply-pull-request.sh script for non-master > branches > > > Key: IGNITE-1383 > URL: https://issues.apache.org/jira/browse/IGNITE-1383 > Project: Ignite > Issue Type: Task >Reporter: Artem Shutak >Assignee: Nikolay Tikhonov > > Sometimes it's need to apply patch to non-master branch. So, it need to have > ability to use apply-pull-request.sh script for non-master branches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1378) Continuous processor doesn't remove message listener if continuous query failed to start
[
https://issues.apache.org/jira/browse/IGNITE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735409#comment-14735409
]
ASF GitHub Bot commented on IGNITE-1378:
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/69
> Continuous processor doesn't remove message listener if continuous query
> failed to start
>
>
> Key: IGNITE-1378
> URL: https://issues.apache.org/jira/browse/IGNITE-1378
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {{GridContinuousProcessor.startRoutine(..)}} method adds message listener on
> line 538 and never removes it if handler registration fails (e.g., due to
> marshalling issues). Need to fix exception handling in this method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-264) Queue failover tests fail in transactional cache
[
https://issues.apache.org/jira/browse/IGNITE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735753#comment-14735753
]
Alexey Goncharuk commented on IGNITE-264:
-
Thanks for the review, Semyon! I addressed the ticket and will re-run the TC
and merge the ticket if all is ok:
* Removed embedded futures for both cases.
* Removed the method. I planned to use it in the beginning, but later I added
a flag to the tx instance, which should be a smaller overhead.
* This is done intentionally, in favor to fix
https://issues.apache.org/jira/browse/IGNITE-1377 later.
> Queue failover tests fail in transactional cache
>
>
> Key: IGNITE-264
> URL: https://issues.apache.org/jira/browse/IGNITE-264
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-1
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> See {{GridCachePartitionedQueueFailoverDataConsistencySelfTest}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1016:
Assignee: Andrey Gura (was: Valentin Kulichenko)
> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Andrey Gura
> Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for
> {{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735916#comment-14735916
]
Alexey Goncharuk commented on IGNITE-1016:
--
Andrey, {{force}} update is used as a fallback mechanism to make sure that
nodes are evenly loaded even in the case when no non-moving partition
assignments can be made. Can you add a specialized test when all nodes are
resided on one host and exludeNeighbors = true, and then check that nodes are
evenly loaded and there are no missed partitions? It is not possible to assign
partitions to non-neighbors if there are fewer _hosts_ in a grid than the
number of configured backups. I want to make sure that in this case we still
have the required number of partitions in any assignment.
> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Labels: Usability
> Fix For: ignite-1.4
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for
> {{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1392) IGFS example configuration must have IPC endpoint enabled by default.
Vladimir Ozerov created IGNITE-1392: --- Summary: IGFS example configuration must have IPC endpoint enabled by default. Key: IGNITE-1392 URL: https://issues.apache.org/jira/browse/IGNITE-1392 Project: Ignite Issue Type: Bug Components: hadoop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Fix For: ignite-1.4 example-igfs.xml has IPC endpoint disabled. I do not understand why it is so. As a result if user is trying to use this config with Hadoop, he receives "Failed to communicate with IGFS." error. It looks like we have to: 1) Enable IPC endpoint. 2) Improve error message with suggestions to the user (e.g. "did you enable IPC endpoint?"). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1262) CacheJdbcPojoStoreFactory issues
[
https://issues.apache.org/jira/browse/IGNITE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736237#comment-14736237
]
Semen Boikov commented on IGNITE-1262:
--
Reviewed, merged to 1.4,
> CacheJdbcPojoStoreFactory issues
>
>
> Key: IGNITE-1262
> URL: https://issues.apache.org/jira/browse/IGNITE-1262
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Yakov Zhdanov
> Labels: usability
> Fix For: ignite-1.4
>
>
> # {{appContext}} should be transient.
> # {{dataSrc}} in factory looks incorrect. It's transient and is always null
> on remote nodes. How is it supposed to be used?
> # Really strange thing with dialects. They are not serializable for no good
> reason, but can be set in factory. Moreover, there is
> {{CacheJdbcPojoStoreFactorySelfTest.testSerializable()}} which checks that H2
> dialect can't be used (???). I think we should make {{JdbcDialect}} implement
> {{Serializable}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1393) AssertionError when stop node executing transaction
Semen Boikov created IGNITE-1393:
Summary: AssertionError when stop node executing transaction
Key: IGNITE-1393
URL: https://issues.apache.org/jira/browse/IGNITE-1393
Project: Ignite
Issue Type: Sub-task
Components: cache
Reporter: Semen Boikov
Fix For: ignite-1.5
I fixed GridCacheStopSelfTest which was disabled for long time, now it fails
because of asserts:
{noformat}
[10:53:02,362][ERROR][async-runner-1][GridNearTxLocal] Heuristic transaction
failure.
class
org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
Failed to locally write to cache (all transaction entries will be invalidated,
however there was a window when entries for this transaction were visible to
others): GridNearTxLocal [nearLocallyMapped=false, colocatedLocallyMapped=true,
hasRemoteLocks=false, mappings=[009f5238-db3d-426f-b787-9a4a156e8000],
super=GridDhtTxLocalAdapter [dhtThreadId=101, needsCompletedVers=false,
nearNodes=[], dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter
[txMap={IgniteTxKey [key=KeyCacheObjectImpl [val=22, hasValBytes=true],
cacheId=1]=IgniteTxEntry [key=KeyCacheObjectImpl [val=22, hasValBytes=true],
cacheId=1, txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=22,
hasValBytes=true], cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl [val=22,
hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=22,
hasValBytes=true]], entryProcessorsCol=null, entryProcessorCalcVal=null,
ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
dhtVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
globalTime=1441781582327, order=1441781581691], filters=[],
filtersPassed=false, filtersSet=true, entry=GridDhtColocatedCacheEntry
[super=GridDhtCacheEntry [rdrs=[], locPart=GridDhtLocalPartition [id=22,
mapPubSize=1, rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0],
state=OWNING, reservations=0, empty=false, createTime=09/09/2015 10:53:02,
mapPubSize=1], super=GridDistributedCacheEntry [super=GridCacheMapEntry
[key=KeyCacheObjectImpl [val=22, hasValBytes=true], val=CacheObjectImpl
[val=22, hasValBytes=true], startVer=1441781581658, ver=GridCacheVersion
[topVer=53261582, nodeOrderDrId=1, globalTime=1441781582327,
order=1441781581691], hash=2018242870, extras=null, flags=2,
prepared=false, locked=true, nodeId=009f5238-db3d-426f-b787-9a4a156e8000,
locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
xidVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
globalTime=1441781582217, order=1441781581591]]}, completedBase=null,
sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion
[topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217,
order=1441781581591], writeVer=GridCacheVersion [topVer=53261582,
nodeOrderDrId=1, globalTime=1441781582327, order=1441781581691],
implicit=false, implicitSingle=false, loc=true, threadId=101,
startTime=1441781582212, nodeId=009f5238-db3d-426f-b787-9a4a156e8000,
startVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1,
globalTime=1441781582218, order=1441781581611], endVer=GridCacheVersion
[topVer=53261582, nodeOrderDrId=1, globalTime=1441781582336,
order=1441781581738], isolation=REPEATABLE_READ, concurrency=PESSIMISTIC,
timeout=0, sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion
[topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217,
order=1441781581591], finalizing=NONE, preparing=false, state=COMMITTED,
timedOut=false, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0],
duration=138ms, onePhaseCommit=true], size=1]]]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:1036)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.finish(GridNearTxLocal.java:654)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:749)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:741)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitAsync(GridNearTxLocal.java:741)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.commitTxAsync(GridCacheAdapter.java:4024)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedContext.commitTxAsync(GridCacheSharedContext.java:636)
at
org.apache.ignite.internal.processors.cache.transactions.TransactionProxyImpl.commit(TransactionProxyImpl.java:256)
at
org.apache.ignite.internal.processors.cache.GridCacheStopSelfTest$1.ca
