[jira] [Created] (IGNITE-3666) Print out an information message if LGPL module is in classpath
Sergey Kozlov created IGNITE-3666: - Summary: Print out an information message if LGPL module is in classpath Key: IGNITE-3666 URL: https://issues.apache.org/jira/browse/IGNITE-3666 Project: Ignite Issue Type: Improvement Reporter: Sergey Kozlov The fabric edition can be complied with LGPL support. For such cases a node should print out the message that will inform the user about LGPL modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3661) Process failing web sessions tests.
[ https://issues.apache.org/jira/browse/IGNITE-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414809#comment-15414809 ] Vladimir Ozerov commented on IGNITE-3661: - Implemented. But with these changes we have a failure in Licenses suite. Not sure why. > Process failing web sessions tests. > --- > > Key: IGNITE-3661 > URL: https://issues.apache.org/jira/browse/IGNITE-3661 > Project: Ignite > Issue Type: Sub-task > Components: general, websession >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2268) Implement CacheKeyConfiguration on cluster page
[ https://issues.apache.org/jira/browse/IGNITE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414772#comment-15414772 ] Andrey Novikov edited comment on IGNITE-2268 at 8/10/16 6:01 AM: - Reviewed. Merged. Pavel, please test was (Author: anovikov): Reviewed. Merged. > Implement CacheKeyConfiguration on cluster page > --- > > Key: IGNITE-2268 > URL: https://issues.apache.org/jira/browse/IGNITE-2268 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov > Fix For: 1.8 > > > Extend binary configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3519) Web console: add ability to specify a node filter in cache configuration
[
https://issues.apache.org/jira/browse/IGNITE-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414750#comment-15414750
]
Andrey Novikov commented on IGNITE-3519:
Fixed
> Web console: add ability to specify a node filter in cache configuration
>
>
> Key: IGNITE-3519
> URL: https://issues.apache.org/jira/browse/IGNITE-3519
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.8
>
>
> For example:
> {code}
>
> class="org.gridgain.visor.tester.cache.VisorCacheNodeAttrFilter">
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3519) Web console: add ability to specify a node filter in cache configuration
[
https://issues.apache.org/jira/browse/IGNITE-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Novikov resolved IGNITE-3519.
Resolution: Fixed
Assignee: Pavel Konstantinov (was: Andrey Novikov)
> Web console: add ability to specify a node filter in cache configuration
>
>
> Key: IGNITE-3519
> URL: https://issues.apache.org/jira/browse/IGNITE-3519
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.8
>
>
> For example:
> {code}
>
> class="org.gridgain.visor.tester.cache.VisorCacheNodeAttrFilter">
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3665) Update KafkaStreamer dependencies
Roman Shtykh created IGNITE-3665: Summary: Update KafkaStreamer dependencies Key: IGNITE-3665 URL: https://issues.apache.org/jira/browse/IGNITE-3665 Project: Ignite Issue Type: Improvement Reporter: Roman Shtykh Assignee: Roman Shtykh Update for Kafka 0.10 https://archive.apache.org/dist/kafka/0.10.0.0/RELEASE_NOTES.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2559) Transaction hangs if entry processor is not serializable
[
https://issues.apache.org/jira/browse/IGNITE-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414275#comment-15414275
]
Nikolay Tikhonov commented on IGNITE-2559:
--
In this case first transaction does't release a locks on near node. The second
transaction sends NearLockRequest and doesn't receive NearLockResponce on the
lock request.
> Transaction hangs if entry processor is not serializable
>
>
> Key: IGNITE-2559
> URL: https://issues.apache.org/jira/browse/IGNITE-2559
> Project: Ignite
> Issue Type: Bug
>Reporter: Valentin Kulichenko
>Assignee: Nikolay Tikhonov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: TxTest.java
>
>
> Test attached.
> If entry processor doesn't implement {{Serializable}}, the exception is
> thrown, but transaction hangs forever. If you try to join more nodes after
> this happens, they will not be able to do this as well.
> Hanged thread dump:
> {noformat}
> "main" #1 prio=5 os_prio=31 tid=0x7f8b6580 nid=0x1703 waiting on
> condition [0x70218000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00076ca274f8> (a
> org.apache.ignite.internal.util.future.GridEmbeddedFuture)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:117)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$24.op(GridCacheAdapter.java:2296)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$24.op(GridCacheAdapter.java:2283)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4291)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke0(GridCacheAdapter.java:2283)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke(GridCacheAdapter.java:2261)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.invoke(IgniteCacheProxy.java:1518)
> at TxTest.main(TxTest.java:27)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3407) HTTP REST: query commands without pageSize failed with NPE
[ https://issues.apache.org/jira/browse/IGNITE-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413975#comment-15413975 ] Saikat Maitra commented on IGNITE-3407: --- [~agura] Hi Andrey, Thank you for reviewing the PR. I will update the PR changes. Regards Saikat > HTTP REST: query commands without pageSize failed with NPE > -- > > Key: IGNITE-3407 > URL: https://issues.apache.org/jira/browse/IGNITE-3407 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.6 >Reporter: Andrey Novikov >Assignee: Saikat Maitra > Fix For: 1.8 > > > org/apache/ignite/internal/processors/rest/handlers/query/QueryCommandHandler.java:125 > Need return response with error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3263) Affinity function must check for null keys
[
https://issues.apache.org/jira/browse/IGNITE-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413968#comment-15413968
]
Saikat Maitra commented on IGNITE-3263:
---
[~dmagda]
Hi Denis,
Thank you for reviewing the PR. I will update the changes. The reason I added
CacheAffinityPutGetExample.java is to demonstrate that the changes are tested
as I had challenges to reproduce this exception using unit test.
Regards
Saikat
> Affinity function must check for null keys
> --
>
> Key: IGNITE-3263
> URL: https://issues.apache.org/jira/browse/IGNITE-3263
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Saikat Maitra
> Labels: community
> Fix For: 1.8
>
>
> AffinityFunction implementations must check for {{null}} keys and through
> meaningful exceptions in such a cases.
> As an example the following code trows NPE since the keys is not validated
> {code}
> Cache, Person> personCache = ..;
> personCache.get(new AffinityKey<>(key, affKey)); // returns value
> personCache.get(new AffinityKey<>(key)); // throws NPE
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction.partition(RendezvousAffinityFunction.java:428)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.partition(GridCacheAffinityManager.java:206)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1801)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get(GridDhtAtomicCache.java:339)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4650)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1391)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:907)
> at
> my.apache.ignite.examples.collocation.CacheCollocationExample.main(CacheCollocationExample.java:69)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2546) Need to introduce transformers to SCAN queries
[
https://issues.apache.org/jira/browse/IGNITE-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev reassigned IGNITE-2546:
-
Assignee: Eduard Shangareev (was: Valentin Kulichenko)
> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public QueryCursor query(Query qry, IgniteClosure
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2546) Need to introduce transformers to SCAN queries
[
https://issues.apache.org/jira/browse/IGNITE-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev reassigned IGNITE-2546:
-
Assignee: Valentin Kulichenko (was: Eduard Shangareev)
> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public QueryCursor query(Query qry, IgniteClosure
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2546) Need to introduce transformers to SCAN queries
[
https://issues.apache.org/jira/browse/IGNITE-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev reassigned IGNITE-2546:
-
Assignee: Eduard Shangareev
> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public QueryCursor query(Query qry, IgniteClosure
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3588) Cassandra store should use batching in writeAll and deleteAll methods
[
https://issues.apache.org/jira/browse/IGNITE-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Rudyak reassigned IGNITE-3588:
---
Assignee: Igor Rudyak
> Cassandra store should use batching in writeAll and deleteAll methods
> -
>
> Key: IGNITE-3588
> URL: https://issues.apache.org/jira/browse/IGNITE-3588
> Project: Ignite
> Issue Type: Improvement
> Components: ignite-cassandra
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Igor Rudyak
> Fix For: 1.8
>
>
> In current implementation Cassandra store executes all updates one by one
> when {{writeAll}} or {{deleteAll}} method is called.
> We should add an option to use {{BatchStatement}} instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2546) Need to introduce transformers to SCAN queries
[
https://issues.apache.org/jira/browse/IGNITE-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-2546:
Assignee: (was: Valentin Kulichenko)
> Need to introduce transformers to SCAN queries
> --
>
> Key: IGNITE-2546
> URL: https://issues.apache.org/jira/browse/IGNITE-2546
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> Need to add new method to {{IgniteCache}} API:
> {code}
> public QueryCursor query(Query qry, IgniteClosure
> transformer);
> {code}
> For now this will be supported only for {{ScanQuery}}, for all others we
> should throw {{UnsupportedOperationException}} with proper message.
> Example and documentation should be also added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3579) Message type should be short.
[
https://issues.apache.org/jira/browse/IGNITE-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3579:
Priority: Critical (was: Blocker)
> Message type should be short.
> -
>
> Key: IGNITE-3579
> URL: https://issues.apache.org/jira/browse/IGNITE-3579
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.0
>
>
> Currently we encode internal messages with {{byte}}. It turns out that we
> almost exhausted possible IDs.
> We should change {{byte}} to {{short}} for message ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3650) IGFS: Local secondary: Implement "info()" operation.
[ https://issues.apache.org/jira/browse/IGNITE-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413500#comment-15413500 ] ASF GitHub Bot commented on IGNITE-3650: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/939 IGNITE-3650 IGFS: Local secondary: Implement "info()" operation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3650 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/939.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 #939 commit 02ca57cf8d5f9b7381d8d1676314e47e19e49bf6 Author: tledkov-gridgain Date: 2016-08-09T13:20:00Z IGNITE-3650 IGFS: Local secondary: Implement "info()" operation. > IGFS: Local secondary: Implement "info()" operation. > > > Key: IGNITE-3650 > URL: https://issues.apache.org/jira/browse/IGNITE-3650 > Project: Ignite > Issue Type: Sub-task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key
[ https://issues.apache.org/jira/browse/IGNITE-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413480#comment-15413480 ] Alexey Goncharuk commented on IGNITE-3633: -- Updates in PR look good to me. Denis, can you take a look? > Throw an exception when binary object without explicitly set hash code is > used as a key > --- > > Key: IGNITE-3633 > URL: https://issues.apache.org/jira/browse/IGNITE-3633 > Project: Ignite > Issue Type: Task > Components: binary, cache, SQL >Reporter: Alexander Paschenko >Assignee: Alexey Goncharuk > Fix For: 1.8 > > > New binary built keys erroneously get put to cache as having cache code of 0. > We want to force user to set hash code explicitly by throwing an exception > when they do not do so. > Proposed solution by Denis Magda: > http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-BinaryObjectBuilder-stored-at-the-same-partition-by-default-td8042i20.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1421) .Net: Optimize writes of ultra-dense structures.
[ https://issues.apache.org/jira/browse/IGNITE-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1421: --- Assignee: (was: Pavel Tupitsyn) > .Net: Optimize writes of ultra-dense structures. > > > Key: IGNITE-1421 > URL: https://issues.apache.org/jira/browse/IGNITE-1421 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov > Labels: .net > Fix For: 1.8 > > > There is a case when we can dramatically increase marshal/unmarshal > performance: > 1) Type is a structure; > 2) It contains only integer/float/double primitive types with well-defined; > memory layout which is consistent with our serialization protocol; > 3) We are sure that there are no gaps in it's memory layout. > 4) User writes it as "marshal-aware" and fields write order is consistent > with memory layout. > In this case we can copy the whole structure into our stream with a single > memcpy() operation. And we can read it from the stream as easy as [pointer > dereference + position shift] (provided that target is on the stack). > We should also disable handles for structs, since it does not make sense. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3664) IGFS: Local secondary: Support blockSize attribute
Taras Ledkov created IGNITE-3664: Summary: IGFS: Local secondary: Support blockSize attribute Key: IGNITE-3664 URL: https://issues.apache.org/jira/browse/IGNITE-3664 Project: Ignite Issue Type: Sub-task Reporter: Taras Ledkov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2547) Expand node with metadata for current selected cache
[ https://issues.apache.org/jira/browse/IGNITE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2547: --- Fix Version/s: (was: 1.7) 1.8 > Expand node with metadata for current selected cache > > > Key: IGNITE-2547 > URL: https://issues.apache.org/jira/browse/IGNITE-2547 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Kuznetsov >Priority: Minor > Fix For: 1.8 > > > In current implementation we show all caches metadata collapsed, but it make > sense to expand node for current selected cache. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3263) Affinity function must check for null keys
[
https://issues.apache.org/jira/browse/IGNITE-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-3263:
---
Fix Version/s: (was: 1.7)
1.8
> Affinity function must check for null keys
> --
>
> Key: IGNITE-3263
> URL: https://issues.apache.org/jira/browse/IGNITE-3263
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Saikat Maitra
> Labels: community
> Fix For: 1.8
>
>
> AffinityFunction implementations must check for {{null}} keys and through
> meaningful exceptions in such a cases.
> As an example the following code trows NPE since the keys is not validated
> {code}
> Cache, Person> personCache = ..;
> personCache.get(new AffinityKey<>(key, affKey)); // returns value
> personCache.get(new AffinityKey<>(key)); // throws NPE
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction.partition(RendezvousAffinityFunction.java:428)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.partition(GridCacheAffinityManager.java:206)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheKeyObject(GridCacheContext.java:1801)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get(GridDhtAtomicCache.java:339)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4650)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1391)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:907)
> at
> my.apache.ignite.examples.collocation.CacheCollocationExample.main(CacheCollocationExample.java:69)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2769) Document store session listeners
[ https://issues.apache.org/jira/browse/IGNITE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2769: --- Fix Version/s: (was: 1.7) 1.8 > Document store session listeners > > > Key: IGNITE-2769 > URL: https://issues.apache.org/jira/browse/IGNITE-2769 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2425) BinaryObject.readField() called for an object Java array field reads objects class
[
https://issues.apache.org/jira/browse/IGNITE-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-2425:
---
Fix Version/s: (was: 1.7)
1.8
> BinaryObject.readField() called for an object Java array field reads objects
> class
> ---
>
> Key: IGNITE-2425
> URL: https://issues.apache.org/jira/browse/IGNITE-2425
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Labels: important
> Fix For: 1.8
>
> Attachments: ExampleNodeStartup.java
>
>
> If there is a {{BinaryObject}} that has a field that refers to an array of
> some custom user objects then during the time {{BinaryObject.field()}} is
> called the class of this custom will be read. This can lead to
> {{ClassNotFoundException}} on a server side or another ones related.
> In the attach example the following issue is demonstrated using
> {{BinaryObjectBuilder}} which class is not listed in classnames.properties.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3036) We need to set red border to empty mandatory fields after Save
[ https://issues.apache.org/jira/browse/IGNITE-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3036: --- Fix Version/s: (was: 1.7) 1.8 > We need to set red border to empty mandatory fields after Save > -- > > Key: IGNITE-3036 > URL: https://issues.apache.org/jira/browse/IGNITE-3036 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Konstantinov >Assignee: Maxim Afanasiev > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-887) Fix ContinuousQueries to support initial state as well as in-focus and out-of-focus events
[ https://issues.apache.org/jira/browse/IGNITE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-887: -- Fix Version/s: (was: 1.7) 1.8 > Fix ContinuousQueries to support initial state as well as in-focus and > out-of-focus events > -- > > Key: IGNITE-887 > URL: https://issues.apache.org/jira/browse/IGNITE-887 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Dmitriy Setrakyan >Assignee: Andrey Kornev > Fix For: 1.8 > > > The discussion on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-Query-td136.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3262) Web console: Implement test runner
[ https://issues.apache.org/jira/browse/IGNITE-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3262: --- Fix Version/s: (was: 1.7) 1.8 > Web console: Implement test runner > --- > > Key: IGNITE-3262 > URL: https://issues.apache.org/jira/browse/IGNITE-3262 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Dmitriyff >Assignee: Dmitriyff > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2436) GridCacheWriteBehindStore flushes a single value when the queue size is reached
[ https://issues.apache.org/jira/browse/IGNITE-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2436: --- Fix Version/s: (was: 1.7) 1.8 > GridCacheWriteBehindStore flushes a single value when the queue size is > reached > --- > > Key: IGNITE-2436 > URL: https://issues.apache.org/jira/browse/IGNITE-2436 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5.0.final >Reporter: Denis Magda > Fix For: 1.8 > > > When the queue size is reached we have to flush a batch as well rather than a > single value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2928) Confusing exception when trying to execute DELETE query
[ https://issues.apache.org/jira/browse/IGNITE-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2928: --- Fix Version/s: (was: 1.7) 1.8 > Confusing exception when trying to execute DELETE query > --- > > Key: IGNITE-2928 > URL: https://issues.apache.org/jira/browse/IGNITE-2928 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.8 > > > See this user thread for details: > http://apache-ignite-users.70518.x6.nabble.com/Help-with-SQL-delete-syntax-on-an-Ignite-Cache-td3822.html > The exception should specifically tell that SQL updates are currently not > supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3338) BinaryObjectException: Failed to get field because type ID of passed object differs from type ID this BinaryField belongs to - during load test with eviction configured
[
https://issues.apache.org/jira/browse/IGNITE-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-3338:
---
Fix Version/s: (was: 1.7)
1.8
> BinaryObjectException: Failed to get field because type ID of passed object
> differs from type ID this BinaryField belongs to - during load test with
> eviction configured
> -
>
> Key: IGNITE-3338
> URL: https://issues.apache.org/jira/browse/IGNITE-3338
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ksenia Rybakova
> Fix For: 1.8
>
>
> The following exceptions occur during load test with eviction configured:
> {noformat}
> ERROR: The benchmark of random operation failed.
> Type '--help' for usage.
> Finishing main test [ts=1466178657166, date=Fri Jun 17 08:50:57 PDT 2016]
> ERROR: Shutting down benchmark driver to unexpected exception.
> Type '--help' for usage.
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [26, 1872066, 1945790, 2405741, 3845651,
> 4830233, 7284502, 8555643]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1467)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1972)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.removeAll(IgniteCacheProxy.java:1416)
> at
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doRemoveAll(IgniteCacheRandomOperationBenchmark.java:809)
> at
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:551)
> at
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:509)
> at
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:156)
> at
> org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
> Failed to update keys (retry update if possible).: [26, 1872066,
> 1945790, 2405741, 3845651, 4830233, 7284502, 8555643]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:311)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2958)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:129)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:266)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:264)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> ... 1 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> update keys on primary node.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFai
[jira] [Updated] (IGNITE-2654) Protocol optimization for GridNearLockRequest/Response
[ https://issues.apache.org/jira/browse/IGNITE-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2654: --- Fix Version/s: (was: 1.7) 1.8 > Protocol optimization for GridNearLockRequest/Response > -- > > Key: IGNITE-2654 > URL: https://issues.apache.org/jira/browse/IGNITE-2654 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Ilya Lantukh > Labels: performance > Fix For: 1.8 > > > Create new, more lightweight versions of GridNearLockRequest/Response: > - Make miniId integer. > - Store boolean flags in a single byte field. > - Remove unused fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2656) Documentation on debugging and fixing the reasons of node disconnection from the cluster
[
https://issues.apache.org/jira/browse/IGNITE-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-2656:
---
Fix Version/s: (was: 1.7)
1.8
> Documentation on debugging and fixing the reasons of node disconnection from
> the cluster
>
>
> Key: IGNITE-2656
> URL: https://issues.apache.org/jira/browse/IGNITE-2656
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 1.8
>
>
> Sometimes a node can be abruptly kicked off from the cluster buy some reason.
> The documentation must contain information on how to get to the root of the
> issue by looking at logs files. Usually the node that was kicked off contains
> "Local node segmented" message and the node that failed its next neighbor
> contains a message with more details "Failed to send message to next node".
> Next the article must list possible reasons of the disconnection:
> - long GC pauses. Give recommendations on how to check;
> - high node utilization so that it responds with a delay;
> - low network configuration parameters that are not suited for an environment;
> There should be a section about
> {{IgniteConfiguration.failureDetectionTimeout}} describing its behavior and
> showing all its pros and cons.
> The article must say when it makes sense to 'disable' this timeout by
> switching to explicit configuration of TcpDiscoverySpi.socketTimeout,
> TcpDiscoverySpi.ackTimeout, TcpDiscoverySpi.maxAckTimeout,
> TcpDiscoverySpi.reconnectCount. Pros and cons of manual configuration has to
> be mentioned as well.
>
> Also I would list the usage of TcpDiscoverySpi.joinTimeout,
> TcpDiscoverySpi.networkTimeout (used on client reconnect, servers waits for
> join result, node stop, socket reader first message.) there as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2558) NearCacheConfiguration should not extend MutableConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-2558:
---
Fix Version/s: (was: 1.7)
1.8
> NearCacheConfiguration should not extend MutableConfiguration
> -
>
> Key: IGNITE-2558
> URL: https://issues.apache.org/jira/browse/IGNITE-2558
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Valentin Kulichenko
> Fix For: 1.8
>
>
> Currently {{NearCacheConfiguration}} extends {{MutableConfiguration}} which
> means that it inherits all the properties that don't make sense for it. Also
> it's possible to use it to create a cache with {{CacheManager}}, which is
> also confusing.
> {{NearCacheConfiguration}} should not extend and classes and should be used
> only directly in {{CacheConfiguration.setNearConfiguration()}} or
> {{Ignite.createCache()}} and similar methods.
> In addition, it would be useful to add {{setCopyOnRead}} property for near
> cache. Now it's not possible to control this behavior for near cache only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3292) Yardstick: add logging of preloading progress
[ https://issues.apache.org/jira/browse/IGNITE-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3292: --- Fix Version/s: (was: 1.7) 1.8 > Yardstick: add logging of preloading progress > - > > Key: IGNITE-3292 > URL: https://issues.apache.org/jira/browse/IGNITE-3292 > Project: Ignite > Issue Type: Wish > Components: yardstick >Reporter: Ksenia Rybakova > Fix For: 1.8 > > > Please, add logging of preloading progress. This is really useful when we > load a lot of entries or they are large. > For instance: "Preloading: 200 of 1000 loaded". > Also adding an option that controls frequency of such output makes sense. For > instance, this might be a step (number of entries loaded) - if entries are > large, we set small step, if entries are integers, the step will be large. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2896) IgniteFutureTimeoutException during load test (yardstick)
[
https://issues.apache.org/jira/browse/IGNITE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-2896:
---
Fix Version/s: (was: 1.7)
1.8
> IgniteFutureTimeoutException during load test (yardstick)
> -
>
> Key: IGNITE-2896
> URL: https://issues.apache.org/jira/browse/IGNITE-2896
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
> Environment: Environment:
> - vCPU 8
> - RAM 15GiB
> - OS Ubuntu 14.04
> - Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Yardstick configuration:
> - client mode (15 servers, 5 clients)
> - PRIMARY SYNC
> - 128 threads
> - 1 backup
>Reporter: Ilya Suntsov
>Assignee: Artem Shutak
>Priority: Critical
> Fix For: 1.8
>
> Attachments: drivers_lods_conf.zip, logs_configs_new_p1.zip,
> logs_configs_new_p2.zip, servers_logs_p1.zip, servers_logs_p2.zip
>
>
> I got the following exception during the run of load test with 1 baskup (+
> sql caches and sql benchmarks) :
> {noformat}
> Got exception: class
> org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached
> before computation completed.
> class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was
> reached before computation completed.
> at
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
> at
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
> at
> org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was
> reached before computation completed.
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
> ... 2 more
> {noformat}
> Logs and configs you can find in attachment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2421) EventTypes are badly documented
[
https://issues.apache.org/jira/browse/IGNITE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-2421:
---
Fix Version/s: (was: 1.7)
1.8
> EventTypes are badly documented
> ---
>
> Key: IGNITE-2421
> URL: https://issues.apache.org/jira/browse/IGNITE-2421
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
> Labels: important
> Fix For: 1.8
>
>
> We have to go through all the {{EventTypes}} and document them well:
> - in which conditions they are fired;
> - what kind of nodes (primary, backups or both) will receive and update;
> - etc.
> As an example.
> From {{EVT_CACHE_ENTRY_CREATED}} is not clear when it's fired at all. However
> it's fired when an entry is loaded from a storage, or when it's initially
> created due to a cache put.
> The same situation is around {{EVT_CACHE_OBJECT_PUT}}. There is no info
> saying that it's fired on both primary and backup nodes. That it's not fired
> due to a loading from a cache, etc.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3296) Validation fail in special case
[ https://issues.apache.org/jira/browse/IGNITE-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-3296: --- Fix Version/s: (was: 1.7) 1.8 > Validation fail in special case > --- > > Key: IGNITE-3296 > URL: https://issues.apache.org/jira/browse/IGNITE-3296 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Assignee: Dmitriyff > Fix For: 1.8 > > > # Enable some section that have disabled fields. > # Input in field invalid value. > # Disable section and try to save. > - Validation show invalid message for disabled field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2787) Hibernate L2 cache doesn't survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2787: --- Fix Version/s: (was: 1.7) 1.8 > Hibernate L2 cache doesn't survive client reconnect > --- > > Key: IGNITE-2787 > URL: https://issues.apache.org/jira/browse/IGNITE-2787 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Fix For: 1.8 > > > After a client disconnects and reconnects with new ID, Hibernate L2 cache > can't be used, because existing cache instance are closed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3663) Failed test: Sporadic failures to WebSessionSelfTest.testSessionRenewalDuringLogin()
Vladimir Ozerov created IGNITE-3663:
---
Summary: Failed test: Sporadic failures to
WebSessionSelfTest.testSessionRenewalDuringLogin()
Key: IGNITE-3663
URL: https://issues.apache.org/jira/browse/IGNITE-3663
Project: Ignite
Issue Type: Bug
Components: websession
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Stack trace:
{code}
java.io.FileNotFoundException: \tmp\realm.properties (The system cannot find
the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:221)
at java.io.FileOutputStream.(FileOutputStream.java:171)
at java.io.FileWriter.(FileWriter.java:90)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.createRealm(WebSessionSelfTest.java:895)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.startServerWithLoginService(WebSessionSelfTest.java:856)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.testSessionRenewalDuringLogin(WebSessionSelfTest.java:308)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.testSessionRenewalDuringLogin(WebSessionSelfTest.java:92)
--- Stdout: ---
[09:22:21,509][INFO ][main][root] >>> Starting test:
WebSessionSelfTest#testSessionRenewalDuringLogin <<<
[09:22:21,524][INFO ][main][root] >>> Stopping test:
WebSessionSelfTest#testSessionRenewalDuringLogin in 15 ms <<<
[09:22:21,524][INFO ][main][root] >>> Stopping test class: WebSessionSelfTest
<<<
--- Stderr: ---
[09:22:21,522][ERROR][main][root] Test failed.
java.io.FileNotFoundException: \tmp\realm.properties (The system cannot find
the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:221)
at java.io.FileOutputStream.(FileOutputStream.java:171)
at java.io.FileWriter.(FileWriter.java:90)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.createRealm(WebSessionSelfTest.java:895)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.startServerWithLoginService(WebSessionSelfTest.java:856)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.testSessionRenewalDuringLogin(WebSessionSelfTest.java:308)
at
org.apache.ignite.internal.websession.WebSessionSelfTest.testSessionRenewalDuringLogin(WebSessionSelfTest.java:92)
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:1760)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
at
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
at java.lang.Thread.run(Thread.java:745)
{code}
--
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
]
Pavel Tupitsyn updated IGNITE-424:
--
Fix Version/s: (was: 1.7)
1.8
> 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: 1.8
>
>
> 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-961) Provide node.js integration
[ https://issues.apache.org/jira/browse/IGNITE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-961: -- Fix Version/s: (was: 1.7) 1.8 > Provide node.js integration > --- > > Key: IGNITE-961 > URL: https://issues.apache.org/jira/browse/IGNITE-961 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 1.8 > > -- 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
]
Pavel Tupitsyn updated IGNITE-1040:
---
Fix Version/s: (was: 1.7)
1.8
> 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: 1.8
>
>
> 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] [Updated] (IGNITE-1160) Ignite.deploy(...) method to automatically deploy user code and libraries
[
https://issues.apache.org/jira/browse/IGNITE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1160:
---
Fix Version/s: (was: 1.7)
1.8
> Ignite.deploy(...) method to automatically deploy user code and libraries
> -
>
> Key: IGNITE-1160
> URL: https://issues.apache.org/jira/browse/IGNITE-1160
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
>
> Implement {{Ignite.deploy(...}} method to automatically deploy user code and
> libraries on all Ignite server nodes.
> The method should accept the following parameters:
> # A collection of URIs to get user archives from (ZIPs and JARs should be
> handled.
> # A collection of GIT repositories with a POM file
> # A collection of Maven artifacts and Maven repositories.
> We should also add {{-deploy}} option to the {{ignite.sh}} script should
> should start a client node and automatically deploy the specified artifacts
> (supporting all the options listed above)
> The process should be as follows:
> # start as many server nodes as needed.
> # start a client node, call {{deploy(...)}} and then start using the client.
> # alternatively, call {{ignite.sh -deploy}} to deploy code on the servers,
> before starting using Ignite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-500) GridCacheLoadingConcurrentGridStartTest fails
[ https://issues.apache.org/jira/browse/IGNITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-500: -- Fix Version/s: (was: 1.7) 1.8 > GridCacheLoadingConcurrentGridStartTest fails > - > > Key: IGNITE-500 > URL: https://issues.apache.org/jira/browse/IGNITE-500 > Project: Ignite > Issue Type: Sub-task >Reporter: Yakov Zhdanov > Labels: Muted_test, important, user-request > Fix For: 1.8 > > Attachments: ignite-500.log > > > http://apacheignite.readme.io/v1.0/discuss/550865a8e35e9c3b0083af3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1081) Create integration for OrientDB
[ https://issues.apache.org/jira/browse/IGNITE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1081: --- Fix Version/s: (was: 1.7) 1.8 > Create integration for OrientDB > --- > > Key: IGNITE-1081 > URL: https://issues.apache.org/jira/browse/IGNITE-1081 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: sprint-7 >Reporter: Alexey Kuznetsov >Assignee: Gianfranco Murador >Priority: Minor > Labels: newbie > Fix For: 1.8 > > > Create integration for OrientDB > Create integration for OrientDB https://github.com/orientechnologies/orientdb > OHazelcastPlugin can be used as start point: > https://github.com/orientechnologies/orientdb/blob/master/distributed/src/main/java/com/orientechnologies/orient/server/hazelcast/OHazelcastPlugin.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-962) node.js: provide json cache object implementation
[ https://issues.apache.org/jira/browse/IGNITE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-962: -- Fix Version/s: (was: 1.7) 1.8 > node.js: provide json cache object implementation > - > > Key: IGNITE-962 > URL: https://issues.apache.org/jira/browse/IGNITE-962 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 1.8 > > > * check if we can optimize strings store with storing byte arrays > * implement SQL indexing support for new object -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1103) Issues with synch evictions
[ https://issues.apache.org/jira/browse/IGNITE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1103: --- Fix Version/s: (was: 1.7) 1.8 > Issues with synch evictions > --- > > Key: IGNITE-1103 > URL: https://issues.apache.org/jira/browse/IGNITE-1103 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk > Fix For: 1.8 > > > - Impossible to enable synch near evictions when server node is configured > without near cache > - Backup entries are not evicted when readers are present -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-735) Need to add support for dynamic indexes
[ https://issues.apache.org/jira/browse/IGNITE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-735: -- Fix Version/s: (was: 1.7) 1.8 > Need to add support for dynamic indexes > --- > > Key: IGNITE-735 > URL: https://issues.apache.org/jira/browse/IGNITE-735 > Project: Ignite > Issue Type: Task > Components: SQL >Reporter: Alexey Kuznetsov >Assignee: Sergi Vladykin > Fix For: 1.8 > > > We should support dynamic index creation and deletion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-809) Old value can be missed for tx near cache entry
[
https://issues.apache.org/jira/browse/IGNITE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-809:
--
Fix Version/s: (was: 1.7)
1.8
> Old value can be missed for tx near cache entry
> ---
>
> Key: IGNITE-809
> URL: https://issues.apache.org/jira/browse/IGNITE-809
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Alexey Goncharuk
> Labels: Muted_test
> Fix For: 1.8
>
>
> GridCacheMultinodeUpdateNearEnabledSelfTest fails.
> {noformat}
> junit.framework.AssertionFailedError: Got null in processor.
> at
> org.apache.ignite.internal.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest.testInvoke(GridCacheMultinodeUpdateAbstractSelfTest.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1361)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1304)
> {noformat}
--
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 ] Pavel Tupitsyn updated IGNITE-618: -- Fix Version/s: (was: 1.7) 1.8 > 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: 1.8 > > > 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-570) Fix javadoc according to Jdk8 rules
[ https://issues.apache.org/jira/browse/IGNITE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-570: -- Fix Version/s: (was: 1.7) 1.8 > Fix javadoc according to Jdk8 rules > --- > > Key: IGNITE-570 > URL: https://issues.apache.org/jira/browse/IGNITE-570 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Minor > Fix For: 1.8 > > > goal is not to use -Xdoclint:none -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-220) Continuations do not work as expected for anonymous IgniteCallable
[ https://issues.apache.org/jira/browse/IGNITE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-220: -- Fix Version/s: (was: 1.7) 1.8 > Continuations do not work as expected for anonymous IgniteCallable > -- > > Key: IGNITE-220 > URL: https://issues.apache.org/jira/browse/IGNITE-220 > Project: Ignite > Issue Type: Bug >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov > Fix For: 1.8 > > Attachments: ContinuationTest.java > > > Please find test in attached file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-966) node.js: documentation on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-966: -- Fix Version/s: (was: 1.7) 1.8 > node.js: documentation on readme.io > --- > > Key: IGNITE-966 > URL: https://issues.apache.org/jira/browse/IGNITE-966 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 1.8 > > > http://apacheignite.readme.io/v1.2/docs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1099) Need to cleanup git
[ https://issues.apache.org/jira/browse/IGNITE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1099: --- Fix Version/s: (was: 1.7) 1.8 > Need to cleanup git > --- > > Key: IGNITE-1099 > URL: https://issues.apache.org/jira/browse/IGNITE-1099 > Project: Ignite > Issue Type: Bug >Reporter: Yakov Zhdanov >Assignee: Artem Shutak > Fix For: 1.8 > > > * Need to resurrect tool (formerly named JiraBranchesToHtml) that shows up > branches for closed tickets in JIRA > * Need to go through the branches and determine what branches are useless: > ** ignite-sprint-* > ** branches with no activity for recent months -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1599) [Test Failed] GridEventConsumeSelfTest assertion error
[ https://issues.apache.org/jira/browse/IGNITE-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1599: --- Fix Version/s: (was: 1.7) 1.8 > [Test Failed] GridEventConsumeSelfTest assertion error > -- > > Key: IGNITE-1599 > URL: https://issues.apache.org/jira/browse/IGNITE-1599 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Blocker > Labels: Muted_test > Fix For: 1.8 > > Attachments: Ignite_Tests_Ignite_Basic_3443.zip > > > There is no guarantee that test failure will be produced each test run, > please analyze logs in case of reproduction problem > See full log for details. > bit of log: > [13:10:27]W: [org.apache.ignite:ignite-core] [13:10:27,466][WARN > ][tcp-disco-msg-worker-#7285%anotherGrid][TcpDiscoverySpi] Local node has > detected failed nodes and started cluster-wide procedure. To speed up failure > detection please see 'Failure Detection' section under javadoc for > 'TcpDiscoverySpi' > [13:10:27]W: [org.apache.ignite:ignite-core] > [13:10:27,467][ERROR][tcp-disco-msg-worker-#7285%anotherGrid][TcpDiscoverySpi] > Runtime error caught during grid runnable execution: IgniteSpiThread > [name=tcp-disco-msg-worker-#7285%anotherGrid] > [13:10:27]W: [org.apache.ignite:ignite-core] > java.lang.AssertionError > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing.node(TcpDiscoveryNodesRing.java:311) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeLeftMessage(ServerImpl.java:3579) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2107) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [13:10:27]W: [org.apache.ignite:ignite-core] Exception in thread > "tcp-disco-msg-worker-#7285%anotherGrid" java.lang.AssertionError > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing.node(TcpDiscoveryNodesRing.java:311) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeLeftMessage(ServerImpl.java:3579) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2107) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382) > [13:10:27]W: [org.apache.ignite:ignite-core]at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [13:10:32]W: [org.apache.ignite:ignite-core] [13:10:32,432][WARN > ][node-restarter-1][TcpDiscoverySpi] Node has not been connected to topology > and will repeat join process. Check remote nodes logs for possible error > messages. Note that large topology may require significant time to start. > Increase 'TcpDiscoverySpi.networkTimeout' configuration property if getting > this message on the starting nodes [networkTimeout=5000] > [13:10:32] : [org.apache.ignite:ignite-core] [13:10:32,546][INFO > ][node-restarter-1][GridCacheProcessor] Started cache > [name=ignite-marshaller-sys-cache, mode=REPLICATED] > [13:10:32] : [org.apache.ignite:ignite-core] [13:10:32,547][INFO > ][node-restarter-1][GridCacheProcessor] Started cache > [name=ignite-atomics-sys-cache, mode=PARTITIONED] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1974) Marshaller error messages are user-unfriendly
[
https://issues.apache.org/jira/browse/IGNITE-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1974:
---
Fix Version/s: (was: 1.7)
1.8
> Marshaller error messages are user-unfriendly
> -
>
> Key: IGNITE-1974
> URL: https://issues.apache.org/jira/browse/IGNITE-1974
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 1.8
>
>
> {code}
> Failed to read class name from file [id=-320567023,
> file=C:\W\incubator-ignite\work\marshaller\-320567023.classname]
> {code}
> Ignite developers may understand that there is some unregistered class, but
> for the user this is meaningless.
> Reading class names from file in an implementation detail.
> We should provide a more user-friendly error message explaining what happened
> and why.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1051) node.js: create nodejs examples
[ https://issues.apache.org/jira/browse/IGNITE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1051: --- Fix Version/s: (was: 1.7) 1.8 > node.js: create nodejs examples > --- > > Key: IGNITE-1051 > URL: https://issues.apache.org/jira/browse/IGNITE-1051 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Semen Boikov >Assignee: Andrey Gura > Fix For: 1.8 > > Attachments: ignite-961_ignite-1051.patch > > > Need to create examples for all implemented nodejs features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1126) Make sure REST is covered with tests
[ https://issues.apache.org/jira/browse/IGNITE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1126: --- Fix Version/s: (was: 1.7) 1.8 > Make sure REST is covered with tests > > > Key: IGNITE-1126 > URL: https://issues.apache.org/jira/browse/IGNITE-1126 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Alexey Goncharuk >Assignee: Artem Shutak > Fix For: 1.8 > > > Need to make sure all REST commands are covered with tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1190) org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same versions of all classes are available on all nod
[ https://issues.apache.org/jira/browse/IGNITE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1190: --- Fix Version/s: (was: 1.7) 1.8 > org.apache.ignite.IgniteCheckedException: Failed to find class with given > class loader for unmarshalling (make sure same versions of all classes are > available on all nodes or enable peer-class-loading) > - > > Key: IGNITE-1190 > URL: https://issues.apache.org/jira/browse/IGNITE-1190 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: xwcheng >Assignee: Alexey Goncharuk > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1618) [Test failed] TransactionHeuristicException: Failed to locally write to cache
[
https://issues.apache.org/jira/browse/IGNITE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1618:
---
Fix Version/s: (was: 1.7)
1.8
> [Test failed] TransactionHeuristicException: Failed to locally write to cache
> -
>
> Key: IGNITE-1618
> URL: https://issues.apache.org/jira/browse/IGNITE-1618
> Project: Ignite
> Issue Type: Test
>Affects Versions: ignite-1.4
>Reporter: Andrey Gura
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
> Attachments: test_deployment.log
>
>
> The following test fail:
> * {{GridCacheDeploymentOffHeapSelfTest.testDeployment}}
> * {{GridCacheDeploymentOffHeapSelfTest.testDeployment6}}
> * {{GridCacheDeploymentOffHeapSelfTest.testDeployment7}}
> The stack trace:
> {noformat}
> org.apache.ignite.IgniteException: class
> org.apache.ignite.transactions.TransactionHeuristicException: 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):
> GridDhtTxLocal [nearNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002,
> nearFutId=c5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9,
> nearMiniId=d5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9,
> nearFinFutId=46e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9,
> nearFinMiniId=b6e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9,
> nearXidVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2,
> globalTime=1444061036097, order=1444061035918], super=GridDhtTxLocalAdapter
> [dhtThreadId=33042, needsCompletedVers=true, nearOnOriginatingNode=true,
> nearNodes=[], dhtNodes=[100ca1fe-f561-4ddd-b6d9-88d7cf12e001],
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1]=IgniteTxEntry
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=13, hasValBytes=true],
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl
> [val=org.apache.ignite.tests.p2p.CacheDeploymentTestValue@6c8704b3,
> hasValBytes=true]], prevVal=[op=NOOP, val=null], entryProcessorsCol=null,
> entryProcessorCalcVal=null, ttl=-1, conflictExpireTime=-1, conflictVer=null,
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false,
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[],
> locPart=GridDhtLocalPartition [id=546, mapPubSize=1,
> rmvQueue=GridCircularBuffer [sizeMask=127, idxGen=0], state=OWNING,
> reservations=0, empty=false, createTime=10/05/2015 16:03:56, mapPubSize=1],
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], val=null,
> startVer=1444061035921, ver=GridCacheVersion [topVer=55541037,
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035921],
> hash=462848615, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc
> [locs=[GridCacheMvccCandidate [nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002,
> ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2,
> globalTime=1444061036098, order=1444061035920], timeout=0, ts=1444061036094,
> threadId=33042, id=2544576, topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=0], reentry=null,
> otherNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, otherVer=GridCacheVersion
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036097,
> order=1444061035918], mappedDhtNodes=null, mappedNearNodes=null,
> ownerVer=null, key=KeyCacheObjectImpl [val=13, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=0]]], prepared=true,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null,
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098,
> order=1444061035920], writeVer=GridCacheVersion [topVer=55541037,
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035922],
> implicit=true, implicitSingle=true, loc=true, threadId=33042,
> startTime=1444061036094, nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002,
> startVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2,
> globalTime=1444061036098, order=1444061035920], endVer=null,
> isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0,
> sysInvalidate=false, sys=false, plc=2, commitVer=null,
> finalizing=USER_FINISH, preparing=false, invalidParts={}, state=COMMITTING,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0],
> duration=10ms, onePhaseCommit=true], size=1]]]
> at
> org.apache.ignite.internal.util.I
[jira] [Updated] (IGNITE-1723) [Test] 2 tests of "Scalar Examples" suite permanently fail due to missing "ignite-schedule" module
[
https://issues.apache.org/jira/browse/IGNITE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1723:
---
Fix Version/s: (was: 1.7)
1.8
> [Test] 2 tests of "Scalar Examples" suite permanently fail due to missing
> "ignite-schedule" module
> --
>
> Key: IGNITE-1723
> URL: https://issues.apache.org/jira/browse/IGNITE-1723
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
>
> The following 2 tests fail:
> ScalarExamplesMultiNodeSelfTest.testScalarScheduleCallableExample
> ScalarExamplesSelfTest.testScalarScheduleCallableExample
> {code}
> org.apache.ignite.IgniteException: Current Ignite configuration does not
> support schedule functionality (consider adding ignite-schedule module to
> classpath).
> at
> org.apache.ignite.internal.processors.schedule.IgniteNoopScheduleProcessor.processorException(IgniteNoopScheduleProcessor.java:50)
> at
> org.apache.ignite.internal.processors.schedule.IgniteNoopScheduleProcessor.schedule(IgniteNoopScheduleProcessor.java:43)
> at
> org.apache.ignite.internal.IgniteSchedulerImpl.scheduleLocal(IgniteSchedulerImpl.java:105)
> at
> org.apache.ignite.scalar.pimps.ScalarGridPimp.scheduleLocalCall(ScalarGridPimp.scala:76)
> at
> org.apache.ignite.scalar.examples.ScalarScheduleExample$$anonfun$1.apply$mcV$sp(ScalarScheduleExample.scala:44)
> at
> org.apache.ignite.scalar.examples.ScalarScheduleExample$$anonfun$1.apply(ScalarScheduleExample.scala:35)
> at
> org.apache.ignite.scalar.examples.ScalarScheduleExample$$anonfun$1.apply(ScalarScheduleExample.scala:35)
> at org.apache.ignite.scalar.scalar$.init0(scalar.scala:181)
> at org.apache.ignite.scalar.scalar$.apply(scalar.scala:237)
> at
> org.apache.ignite.scalar.examples.ScalarScheduleExample$.delayedEndpoint$org$apache$ignite$scalar$examples$ScalarScheduleExample$1(ScalarScheduleExample.scala:35)
> at
> org.apache.ignite.scalar.examples.ScalarScheduleExample$delayedInit$body.apply(ScalarScheduleExample.scala:34)
> at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
> at
> scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.App$$anonfun$main$1.apply(App.scala:76)
> at scala.collection.immutable.List.foreach(List.scala:381)
> at
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
> at scala.App$class.main(App.scala:76)
> at
> org.apache.ignite.scalar.examples.ScalarScheduleExample$.main(ScalarScheduleExample.scala:34)
> at
> org.apache.ignite.scalar.tests.examples.ScalarExamplesSelfTest.testScalarScheduleCallableExample(ScalarExamplesSelfTest.scala:81)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-376) Scala examples should be runnable form sbt.
[ https://issues.apache.org/jira/browse/IGNITE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-376: -- Fix Version/s: (was: 1.7) 1.8 > Scala examples should be runnable form sbt. > --- > > Key: IGNITE-376 > URL: https://issues.apache.org/jira/browse/IGNITE-376 > Project: Ignite > Issue Type: Task > Components: build >Affects Versions: sprint-2 >Reporter: Alexey Kuznetsov > Fix For: 1.8 > > > From dev-list: > I downloaded the latest version of apache-ignite and am trying to run the > scala examples in the examples/ subdir. > However, I am not sure what needs to be done for them to be run. I created > an sbt project, included the dependencies on the correct libraries like > ignite-core, ignite-scalar, ignite-examples, however this line keeps > failing from an example such as the Pi calculation: > import org.apache.ignite.scalar.scalar > If I look at the scala docs there is no scalar.scalar. > Are the examples simply too stale? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-731) ClusterGroup.forRandom() should return empty projection in case of empty source projection
[ https://issues.apache.org/jira/browse/IGNITE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-731: -- Fix Version/s: (was: 1.7) 1.8 > ClusterGroup.forRandom() should return empty projection in case of empty > source projection > -- > > Key: IGNITE-731 > URL: https://issues.apache.org/jira/browse/IGNITE-731 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: sprint-3 >Reporter: Alexey Kuznetsov >Assignee: Anton Vinogradov >Priority: Minor > Fix For: 1.8 > > > I found that ClusterGroup.forRandom() is inconsistent for me. > If I try to take forRandom() on empty cluster group > it throws "java.lang.IllegalArgumentException: n must be positive" > I think forRandom() should return empty cluster group in order to not check > if source projection is empty. > Or at least throws exception with meaningful text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1576) CacheObject.toString() can throw NPE if node already stopped
[
https://issues.apache.org/jira/browse/IGNITE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1576:
---
Fix Version/s: (was: 1.7)
1.8
> CacheObject.toString() can throw NPE if node already stopped
>
>
> Key: IGNITE-1576
> URL: https://issues.apache.org/jira/browse/IGNITE-1576
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
> Fix For: 1.8
>
>
> {{CacheObject}} is not functional when the node that created this object is
> stopped. Currently is user saves this object somewhere (e.g., as a part of
> {{CacheEntryEvent}}, it will throw NPEs from {{toString}} and probably other
> methods. We should throw informative error in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1725) [Test] IgniteProjectionStartStopRestartSelfTest.testStopNodesByIdsC fails
[
https://issues.apache.org/jira/browse/IGNITE-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1725:
---
Fix Version/s: (was: 1.7)
1.8
> [Test] IgniteProjectionStartStopRestartSelfTest.testStopNodesByIdsC fails
> -
>
> Key: IGNITE-1725
> URL: https://issues.apache.org/jira/browse/IGNITE-1725
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Ivan Veselovsky
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
>
> {code}
> java.lang.AssertionError: null
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.afterTest(IgniteProjectionStartStopRestartSelfTest.java:179)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1133) Exception is thrown when atomics are accessed within a user transaction
[
https://issues.apache.org/jira/browse/IGNITE-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1133:
---
Fix Version/s: (was: 1.7)
1.8
> Exception is thrown when atomics are accessed within a user transaction
> ---
>
> Key: IGNITE-1133
> URL: https://issues.apache.org/jira/browse/IGNITE-1133
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 1.8
>
>
> The following code does not work:
> {code}
> try (Transaction tx = ig.transactions().txStart(PESSIMISTIC,
> REPEATABLE_READ)) {
> g.atomicSequence(locSeqName1, 0, true);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance
[
https://issues.apache.org/jira/browse/IGNITE-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1678:
---
Fix Version/s: (was: 1.7)
1.8
> IgniteAtomicSequence: make following reservations in advance
>
>
> Key: IGNITE-1678
> URL: https://issues.apache.org/jira/browse/IGNITE-1678
> Project: Ignite
> Issue Type: Improvement
> Components: data structures
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Artem Shutak
> Fix For: 1.8
>
>
> In current implementation a new reservation is made when the current local
> sequence boundary is exceeded.
> In cases when there are many nodes that use the same atomic sequence there
> can be a situation when all the nodes start doing a new reservation at the
> same time. This can lead to performance drops.
> As a performance optimization it makes sense to start reserving new sequence
> slot in advance (in background), like when around 80% of current reservation
> has already been used. Probably we should add a special parameter to
> {{AtomicConfiguration}} that will manage such behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1648) ignitevisorcmd: key "-t" for command "log" works incorrect
[
https://issues.apache.org/jira/browse/IGNITE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1648:
---
Fix Version/s: (was: 1.7)
1.8
> ignitevisorcmd: key "-t" for command "log" works incorrect
> --
>
> Key: IGNITE-1648
> URL: https://issues.apache.org/jira/browse/IGNITE-1648
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
> Environment: Ubuntu 14.04, Apache-Ignite-1.5.0 build #29
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Fix For: 1.8
>
>
> -
> DESCRIPTION
> -
> The key '-t' works incorrect when it's time to print querying events into log
> - it's print topology snapshot as many times as events are in query. Log
> became difficult to read
> -
> STEPS FOR REPRODUCE
> -
> # Run two nodes in the grid
> # Run ignitevisorcmd.sh
> # Connect visor to the grid (open)
> # Run logging by command, for example:
> {noformat}
> log -l -p=30 -t=120 -f=../work/visor/test_log
> {noformat}
> # Generate several grid-wide events by, for example, start-stop one more node
> -
> ACTUAL RESULT
> -
> There is events query in the log every 30 seconds and topology snapshot
> every 2 minutes and every 30 seconds before events query logging - as many
> times as events are in query. Look at the part of log:
> {noformat}
> 10/09/15, 16:08:27 | Log started.
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:57 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:37 | => NODE_JOINED: id8=85d6f860,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:38 | => NODE_LEFT: id8=85d6f860, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:42 | => NODE_JOINED: id8=b732d4c2,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:44 | => NODE_FAILED: id8=b732d4c2,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:46 | => NODE_JOINED: id8=52265274,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:50 | => NODE_LEFT: id8=52265274, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:54 | => NODE_JOINED: id8=12b6eaf9,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:09:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:09:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:09:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:09:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:09:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:08:59 | => NODE_LEFT: id8=12b6eaf9, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:05 | => NODE_JOINED: id8=1666d860,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:09 | => NODE_LEFT: id8=1666d860, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:13 | => NODE_JOINED: id8=ef2c76f7,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:13 | => NODE_FAILED: id8=ef2c76f7,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:17 | => NODE_JOINED: id8=e15a193f,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:10:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:12:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:14:27 | H/N/C|1 |2 |8 |^...|
> 10/09/15, 16:15:27 | Log stopped.
> {noformat}
> -
> EXPECTED RESULT
> -
> There is events query in the log every 30 seconds and topology snapshot
> every 2 minutes. Something like this:
> {noformat}
> 10/09/15, 16:08:27 | Log started.
> 10/09/15, 16:08:37 | => NODE_JOINED: id8=85d6f860,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:38 | => NODE_LEFT: id8=85d6f860, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:42 | => NODE_JOINED: id8=b732d4c2,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:44 | => NODE_FAILED: id8=b732d4c2,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:46 | => NODE_JOINED: id8=52265274,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:50 | => NODE_LEFT: id8=52265274, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:54 | => NODE_JOINED: id8=12b6eaf9,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:08:59 | => NODE_LEFT: id8=12b6eaf9, ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:05 | => NODE_JOINED: id8=1666d860,
> ip=0:0:0:0:0:0:0:1%1
> 10/09/15, 16:09:09 | => NODE_LEFT: id8=1666d860, ip=0:0:0:0:0:0:0:1%1
>
[jira] [Updated] (IGNITE-1601) [Test Failed] GridCacheNearTxExceptionSelfTest.testTransformBackup
[ https://issues.apache.org/jira/browse/IGNITE-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1601: --- Fix Version/s: (was: 1.7) 1.8 > [Test Failed] GridCacheNearTxExceptionSelfTest.testTransformBackup > --- > > Key: IGNITE-1601 > URL: https://issues.apache.org/jira/browse/IGNITE-1601 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Blocker > Labels: Muted_test > Fix For: 1.8 > > > There is no guarantee that test failure will be produced each test run, > please analyze logs in case of reproduction problem: > junit.framework.AssertionFailedError: Unexpected entry for grid [i=2, > entry=GridNearCacheEntry [topVer=3, dhtVer=GridCacheVersion [topVer=55115678, > nodeOrderDrId=2, globalTime=1443635682299, order=1443635677727], part=5, > super=GridDistributedCacheEntry [super=GridCacheMapEntry > [key=KeyCacheObjectImpl [val=5, hasValBytes=true], val=CacheObjectImpl > [val=1, hasValBytes=true], startVer=1443635677720, ver=GridCacheVersion > [topVer=55115678, nodeOrderDrId=3, globalTime=1443635682301, > order=1443635677719], hash=-871541811, extras=GridCacheMvccEntryExtras > [mvcc=GridCacheMvcc [locs=null, rmts=[GridCacheMvccCandidate > [nodeId=100c7cf0-d287-448c-b6d8-c2d96bda3001, ver=GridCacheVersion > [topVer=55115678, nodeOrderDrId=2, globalTime=1443635682301, > order=1443635677731], timeout=0, ts=1443635682299, threadId=80062, > id=6177849, topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], > reentry=null, otherNodeId=null, otherVer=null, mappedDhtNodes=null, > mappedNearNodes=null, ownerVer=null, key=KeyCacheObjectImpl [val=5, > hasValBytes=true], > masks=local=0|owner=1|ready=0|reentry=0|used=1|tx=1|single_implicit=0|dht_local=0|near_local=0|removed=0, > prevVer=null, nextVer=null, flags=0 > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertFalse(Assert.java:39) > at junit.framework.TestCase.assertFalse(TestCase.java:210) > at > org.apache.ignite.internal.processors.cache.IgniteTxExceptionAbstractSelfTest.checkUnlocked(IgniteTxExceptionAbstractSelfTest.java:396) > at > org.apache.ignite.internal.processors.cache.IgniteTxExceptionAbstractSelfTest.checkTransform(IgniteTxExceptionAbstractSelfTest.java:480) > at > org.apache.ignite.internal.processors.cache.IgniteTxExceptionAbstractSelfTest.testTransformBackup(IgniteTxExceptionAbstractSelfTest.java:234) > 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: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) > --- Stdout: --- > [20:54:42,285][INFO ][main][root] >>> Starting test: testTransformBackup <<< > [20:54:42,286][INFO ][test-runner][root] Going to transform: 2 > [20:54:42,298][INFO ][test-runner][root] Caught expected exception: class > org.apache.ignite.transactions.TransactionHeuristicException: Commit produced > a runtime exception (all transaction entries will be invalidated): > GridDhtTxRemote[id=a1a446f1051-0348ff9e--0002--01501f645bf8, > concurrency=OPTIMISTIC, isolation=READ_COMMITTED, state=COMMITTING, > invalidate=false, rollbackOnly=false, > nodeId=100c7cf0-d287-448c-b6d8-c2d96bda3001, duration=0] > [20:54:42,298][INFO ][test-runner][root] Check key: 2 > [20:54:42,298][INFO ][test-runner][root] Entry: null > [20:54:42,299][INFO ][test-runner][root] Dht entry: GridDhtCacheEntry > [rdrs=[], locPart=GridDhtLocalPartition [id=2, mapPubSize=0, > rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=2], state=OWNING, > reservations=0, empty=false, createTime=09/30/2015 20:54:35, mapPubSize=0], > super=GridDistributedCacheEntry [super=GridCacheMapEntry > [key=KeyCacheObjectImpl [val=2, hasValBytes=true], val=null, > startVer=1443635676707, ver=GridCacheVersion [topVer=55115678, > nodeOrderDrId=2, globalTime=1443635682296, order=1443635677722], > hash=821347078, extras=null, flags=3]]] > [20:54:42,299][INFO ][test-runner][root] Entry: null > [20:54:42,299][INFO ][test-runner][root] Dht entry: GridDhtCacheEntry > [rdrs=[], locPart=GridDhtLocalPartitio
[jira] [Updated] (IGNITE-1720) [Test] GridVersionSelfTest.testVersions fails
[
https://issues.apache.org/jira/browse/IGNITE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1720:
---
Fix Version/s: (was: 1.7)
1.8
> [Test] GridVersionSelfTest.testVersions fails
> -
>
> Key: IGNITE-1720
> URL: https://issues.apache.org/jira/browse/IGNITE-1720
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
>
> Test GridVersionSelfTest.testVersions fails:
> {code}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at
> org.apache.ignite.internal.GridVersionSelfTest.testVersions(GridVersionSelfTest.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1824) IgniteCacheTxNearPeekModesTest.testLocalPeek fails on TC sometimes.
[
https://issues.apache.org/jira/browse/IGNITE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1824:
---
Fix Version/s: (was: 1.7)
1.8
> IgniteCacheTxNearPeekModesTest.testLocalPeek fails on TC sometimes.
> ---
>
> Key: IGNITE-1824
> URL: https://issues.apache.org/jira/browse/IGNITE-1824
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
>
> IgniteCacheTxNearPeekModesTest.testLocalPeek fails on TC sometimes.
> Logs
> {noformat}
> junit.framework.ComparisonFailure: expected: but was:
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.ignite.internal.processors.cache.IgniteCachePeekModesAbstractTest.checkStorage(IgniteCachePeekModesAbstractTest.java:354)
> at
> org.apache.ignite.internal.processors.cache.IgniteCachePeekModesAbstractTest.testLocalPeek(IgniteCachePeekModesAbstractTest.java:142)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> --- Stdout: ---
> [17:38:54,870][INFO ][main][root] >>> Starting test: testLocalPeek <<<
> [17:38:54,935][INFO ][test-runner][root] Keys [swap=65, offheap=5, heap=30]
> [17:38:55,023][INFO ][test-runner][root] Keys [swap=64, offheap=5, heap=31]
> [17:38:55,043][INFO ][main][root] >>> Stopping test: testLocalPeek in 173 ms
> <<<
> [17:38:55,043][INFO ][main][root] >>> Stopping test class:
> IgniteCacheTxNearPeekModesTest <<<
> [17:38:55,044][INFO ][main][root] >>> Stopping grid
> [name=cache.IgniteCacheTxNearPeekModesTest3,
> id=30867bb9-d01f-4435-b1e2-2ddd2195d003]
> [17:38:55,051][INFO
> ][disco-event-worker-#7412%cache.IgniteCacheTxNearPeekModesTest0%][GridDiscoveryManager]
> Node left topology: TcpDiscoveryNode
> [id=30867bb9-d01f-4435-b1e2-2ddd2195d003, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2,
> lastExchangeTime=1446215930223, loc=false, ver=1.5.0#19700101-sha1:,
> isClient=false]
> [17:38:55,051][INFO ][main][GridCacheProcessor] Stopped cache: null
> [17:38:55,052][INFO ][main][GridCacheProcessor] Stopped cache:
> ignite-marshaller-sys-cache
> [17:38:55,052][INFO
> ][disco-event-worker-#7412%cache.IgniteCacheTxNearPeekModesTest0%][GridDiscoveryManager]
> Topology snapshot [ver=5, servers=3, clients=0, CPUs=4, heap=3.6GB]
> [17:38:55,052][INFO ][main][GridCacheProcessor] Stopped cache:
> ignite-sys-cache
> [17:38:55,052][INFO ][main][GridCacheProcessor] Stopped cache:
> ignite-atomics-sys-cache
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Removed undeployed
> class: GridDeployment [ts=1446215930365, depMode=SHARED,
> clsLdr=IsolatedClassLoader{roleName='test'},
> clsLdrId=51c1979b051-30867bb9-d01f-4435-b1e2-2ddd2195d003, userVer=0,
> loc=true,
> sampleClsName=org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
> pendingUndeploy=false, undeployed=true, usage=0]
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Class locally
> undeployed: class
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Task locally
> undeployed: class
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$SizeTask
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Class locally
> undeployed: class org.apache.ignite.internal.util.GridLeanMap
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Class locally
> undeployed: class java.lang.Integer
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Class locally
> undeployed: class org.apache.ignite.internal.util.GridLeanMap$Map3
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Class locally
> undeployed: class
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> [17:38:55,057][INFO ][main][GridDeploymentLocalStore] Class locally
> undeployed: class
> org.apache.ignite.internal.pr
[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
]
Pavel Tupitsyn updated IGNITE-1021:
---
Fix Version/s: (was: 1.7)
1.8
> 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: 1.8
>
> 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] [Updated] (IGNITE-965) node.js: provide npm package
[ https://issues.apache.org/jira/browse/IGNITE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-965: -- Fix Version/s: (was: 1.7) 1.8 > node.js: provide npm package > > > Key: IGNITE-965 > URL: https://issues.apache.org/jira/browse/IGNITE-965 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 1.8 > > > Need to investigate how packages are built and shared. > The result should be a script or automated procedure that build and share the > package -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1757) [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1757:
---
Fix Version/s: (was: 1.7)
1.8
> [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails
> on TC sometimes
>
>
> Key: IGNITE-1757
> URL: https://issues.apache.org/jira/browse/IGNITE-1757
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
>
> CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC
> sometimes.
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:95)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:180)
> at
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:85)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.getDatabaseSnapshot(AbstractEntityPersister.java:1513)
> at
> org.hibernate.engine.internal.StatefulPersistenceContext.getDatabaseSnapshot(StatefulPersistenceContext.java:316)
> at
> org.hibernate.engine.internal.ForeignKeys.isTransient(ForeignKeys.java:217)
> at
> org.hibernate.event.internal.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:497)
> at
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:100)
> at
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:90)
> at
> org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:735)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:727)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:723)
> at
> org.apache.ignite.cache.store.hibernate.CacheHibernateBlobStore.write(CacheHibernateBlobStore.java:190)
> at
> org.apache.ignite.testframework.junits.cache.GridAbstractCacheStoreSelfTest$1.call(GridAbstractCacheStoreSelfTest.java:396)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> --- Stderr: ---
> [21:04:18,410][WARN
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][CacheHibernateBlobStore] No
> Hibernate configuration has been provided for store (will use default).
> [21:04:18,495][WARN
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][DriverManagerConnectionProviderImpl]
> HHH000148: No JDBC Driver class was specified by property
> hibernate.connection.driver_class
> Failure in thread: Thread [id=711,
> name=hibernate.CacheHibernateBlobStoreSelfTest-5]
> java.lang.NullPointerException
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.log
[jira] [Updated] (IGNITE-1525) Return value for cache operation can be lost with onePhaseCommit
[
https://issues.apache.org/jira/browse/IGNITE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1525:
---
Fix Version/s: (was: 1.7)
1.8
> Return value for cache operation can be lost with onePhaseCommit
>
>
> Key: IGNITE-1525
> URL: https://issues.apache.org/jira/browse/IGNITE-1525
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Semen Boikov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 1.8
>
>
> Looks like with {{onePhaseCommit}} return value for cache operation can be
> lost if primary node fails, {{GridNearTxPrepareResponse}} with return value
> is not received, but transaction executes 'check backup' step and finishes
> without error.
> Reproduces in {{IgniteCachePutRetryTransactionalSelfTest.testInvoke}}, also
> added one more test to check return value
> {{IgniteCachePutRetryTransactionalSelfTest.testGetAndPut}}.
> Please unmute tests on TC when fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-184) visorcmd: improve auto-calculation of width of table columns
[ https://issues.apache.org/jira/browse/IGNITE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-184: -- Fix Version/s: (was: 1.7) 1.8 > visorcmd: improve auto-calculation of width of table columns > > > Key: IGNITE-184 > URL: https://issues.apache.org/jira/browse/IGNITE-184 > Project: Ignite > Issue Type: Task > Components: UI >Affects Versions: sprint-1 > Environment: I suggest to use following logic: > if parameter value is a set of values separated by space then print this > separated values from new line > Use terminal width to determine table columns maximum width >Reporter: Alexey Kuznetsov > Fix For: 1.8 > > Attachments: gg-8723.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-898) Ignite does not starts from folder which name contains space
[ https://issues.apache.org/jira/browse/IGNITE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-898: -- Fix Version/s: (was: 1.7) 1.8 > Ignite does not starts from folder which name contains space > > > Key: IGNITE-898 > URL: https://issues.apache.org/jira/browse/IGNITE-898 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov > Fix For: 1.8 > > > Observed: > In case folder name contains space character Ignite node cannot be started. > Expected: > Ingine node should be startable even when folder name contains space > character. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1886) NPE in H2 when running query with subselects
[
https://issues.apache.org/jira/browse/IGNITE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1886:
---
Fix Version/s: (was: 1.7)
1.8
> NPE in H2 when running query with subselects
>
>
> Key: IGNITE-1886
> URL: https://issues.apache.org/jira/browse/IGNITE-1886
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Sergi Vladykin
>Priority: Critical
> Fix For: 1.8
>
> Attachments: QueryTest.java
>
>
> Test reproducing the issue is attached. NPE is thrown as a result (see below).
> Corresponding user@ thread:
> http://apache-ignite-users.70518.x6.nabble.com/Does-Ignite-support-nested-SQL-Queries-td1714.html
> {noformat}
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteException: Failed to parse query: SELECT a.* FROM
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug,
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:636)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:70)
> 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:140)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query:
> SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug,
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:641)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:627)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse
> query: SELECT a.* FROM (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END
> id FROM "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT
> CASE WHEN og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug,
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1510)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:634)
> ... 7 more
> Caused by: javax.cache.CacheException: Failed to parse query: SELECT a.* FROM
> (SELECT CASE WHEN u.id < 100 THEN u.id ELSE ug.id END id FROM
> "UserCache".user u, userorder ug WHERE u.id = ug.usrid) a, (SELECT CASE WHEN
> og.goodid < 5 THEN 100 ELSE og.goodid END id FROM userorder ug,
> "OrderGoodCache".ordergood og WHERE ug.id = og.orderid) b WHERE a.id = b.id
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:938)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:636)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:634)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1492)
> ... 8 more
> Caused by: org.h2.jdbc.JdbcSQLException: General error:
> "java.lang.NullPointerException" [5-175]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
> at org.h2.message.DbException.get(DbException.java:161)
> at org.h2.message.DbException.convert(DbException.java:284)
> at org.h2.message.DbException.toSQLException(DbException.java:257)
> at org.h2.message.TraceObject.logAndConvert(TraceObject.java:368)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:270)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:935)
> ... 12 more
> Caused by: java.lang.NullPointerException
> at org.h2.expression.Function.
[jira] [Updated] (IGNITE-1585) [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine
[ https://issues.apache.org/jira/browse/IGNITE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1585: --- Fix Version/s: (was: 1.7) 1.8 > [Test Failed] TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine > --- > > Key: IGNITE-1585 > URL: https://issues.apache.org/jira/browse/IGNITE-1585 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Blocker > Labels: Muted_test > Fix For: 1.8 > > > There is no guarantee that test failure will be produced each test run, > please analyze logs in case of reproduction problem: > org.apache.ignite.spi.IgniteSpiException: Failed to get registered addresses > for the provider: google-compute-engine > at > com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229) > at > org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.checkGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:124) > at > org.jclouds.compute.internal.FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.sharedNameForGroup(FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java:120) > at > org.jclouds.googlecomputeengine.compute.functions.FirewallTagNamingConvention$Factory.get(FirewallTagNamingConvention.java:39) > at > org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:68) > at > org.jclouds.googlecomputeengine.compute.functions.InstanceToNodeMetadata.apply(InstanceToNodeMetadata.java:43) > at > com.google.common.base.Functions$FunctionComposition.apply(Functions.java:211) > at com.google.common.collect.Iterators$8.transform(Iterators.java:794) > at > com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48) > at com.google.common.collect.Iterators$7.computeNext(Iterators.java:646) > at > com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) > at > com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) > at com.google.common.collect.Iterators.addAll(Iterators.java:356) > at com.google.common.collect.Iterables.addAll(Iterables.java:350) > at com.google.common.collect.Sets.newLinkedHashSet(Sets.java:328) > at > org.jclouds.compute.internal.BaseComputeService.listNodesDetailsMatching(BaseComputeService.java:359) > at > org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:190) > at > org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106) > at > org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71) > --- Stdout: --- > Configured log4j from: > /opt/TeamcityAgent/work/871ff4a46e450b13/modules/core/src/test/config/log4j-test.xml > [14:19:49,901][INFO ][main][root] >>> Starting test class: > TcpDiscoveryCloudIpFinderSelfTest <<< > [14:19:49,944][INFO ][main][root] >>> Starting test: testGoogleComputeEngine > <<< > [14:19:49,945][INFO ][test-runner][root] Testing provider: > google-compute-engine > [14:19:52,312][INFO ][main][root] >>> Stopping test: testGoogleComputeEngine > in 2367 ms <<< > --- Stderr: --- > [14:19:52,310][ERROR][main][root] Test failed. > class org.apache.ignite.spi.IgniteSpiException: Failed to get registered > addresses for the provider: google-compute-engine > at > org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinder.getRegisteredAddresses(TcpDiscoveryCloudIpFinder.java:210) > at > org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testCloudProvider(TcpDiscoveryCloudIpFinderSelfTest.java:106) > at > org.apache.ignite.spi.discovery.tcp.ipfinder.cloud.TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine(TcpDiscoveryCloudIpFinderSelfTest.java:71) > 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:1665) > at > org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111) > at > org.apache.ignite.testframework.junits.GridAbstract
[jira] [Updated] (IGNITE-469) When running selected tests from a test class #afterTestsStopped() is not invoked.
[ https://issues.apache.org/jira/browse/IGNITE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-469: -- Fix Version/s: (was: 1.7) 1.8 > When running selected tests from a test class #afterTestsStopped() is not > invoked. > -- > > Key: IGNITE-469 > URL: https://issues.apache.org/jira/browse/IGNITE-469 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: sprint-1 >Reporter: Ivan Veselovsky > Fix For: 1.8 > > Attachments: IGNITE-469--a.patch > > > JUnit test infrastructure in Ignite has custom test engine that invokes > #afterTestsStopped() when > org.apache.ignite.testframework.junits.GridAbstractTest#isLastTest() == true: > return cntrs.getStopped() == cntrs.getNumberOfTests(); > , where getNumberOfTests() is calculated by counting all the public class > methods starting with "test". > When we execute selected tests (I guess, does not matter from maven or from > IDE), cntrs.getStopped() is always less than the total number of tests in the > test class, so #afterTestsStopped() is not executed. > This leaves unfinished processes like Ignite nodes that afterwards affect the > behavior of other tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-969) Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non String value (Integer in my case)
[
https://issues.apache.org/jira/browse/IGNITE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-969:
--
Fix Version/s: (was: 1.7)
1.8
> Failed to start node if 'textFields' in 'CacheTypeMetadata' contains non
> String value (Integer in my case)
> --
>
> Key: IGNITE-969
> URL: https://issues.apache.org/jira/browse/IGNITE-969
> Project: Ignite
> Issue Type: Bug
> Components: cache, SQL
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: 1.8
>
>
> {code}
>
>
>
> value="org.gridgain.visor.tester.sql.AddressKey"/>
> value="org.gridgain.visor.tester.sql.Address"/>
>
>
> class="org.apache.ignite.cache.CacheTypeFieldMetadata">
>
>
> static-field="java.sql.Types.INTEGER"/>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.cache.CacheTypeFieldMetadata">
>
>
> static-field="java.sql.Types.INTEGER"/>
>
>
>
>
> class="org.apache.ignite.cache.CacheTypeFieldMetadata">
>
>
> static-field="java.sql.Types.VARCHAR"/>
>
>
> value="java.lang.String"/>
>
> class="org.apache.ignite.cache.CacheTypeFieldMetadata">
>
>
> static-field="java.sql.Types.INTEGER"/>
>
>
> value="java.lang.Integer"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> zip
> street
>
>
>
>
>
>
>
> class="org.apache.ignite.lang.IgniteBiTuple">
> value="java.lang.String"/>
>
>
>
>
> class="org.apache.ignite.lang.IgniteBiTuple">
> value="java.lang.Integer"/>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.lang.IgniteBiTuple">
>
>
>
>
>
> class="org.apache.ignite.lang.IgniteBiTuple">
> value="java.lang.String"/>
>
>
>
>
[jira] [Updated] (IGNITE-1495) Cache SQL query metadata index's fields have wrong register.
[ https://issues.apache.org/jira/browse/IGNITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1495: --- Fix Version/s: (was: 1.7) 1.8 > Cache SQL query metadata index's fields have wrong register. > > > Key: IGNITE-1495 > URL: https://issues.apache.org/jira/browse/IGNITE-1495 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: 1.5.0.final >Reporter: Vasiliy Sisko >Assignee: Sergi Vladykin > Fix For: 1.8 > > Attachments: #_IGNITE-1495_Test_for_index_s_fields.patch > > > Index's fields should have register how in table fields (In upper case). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1603) [Test Failed] DataStreamerMultinodeCreateCacheTest.testCreateCacheAndStream
[ https://issues.apache.org/jira/browse/IGNITE-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1603: --- Fix Version/s: (was: 1.7) 1.8 > [Test Failed] DataStreamerMultinodeCreateCacheTest.testCreateCacheAndStream > > > Key: IGNITE-1603 > URL: https://issues.apache.org/jira/browse/IGNITE-1603 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Blocker > Labels: Muted_test > Fix For: 1.8 > > Attachments: > DataStreamerMultinodeCreateCacheTest.testCreateCacheAndStream.zip > > > There is no guarantee that test failure will be produced each test run, > please analyze logs in case of reproduction problem. Logs attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-435) Visor should use smart format for time values
[
https://issues.apache.org/jira/browse/IGNITE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-435:
--
Fix Version/s: (was: 1.7)
1.8
> Visor should use smart format for time values
> -
>
> Key: IGNITE-435
> URL: https://issues.apache.org/jira/browse/IGNITE-435
> Project: Ignite
> Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: YoungGyu Chun
>Priority: Minor
> Labels: visor
> Fix For: 1.8
>
>
> {code}
> Maximum job execute time| 60009ms - should show 1m
> Curent job execute time | 120ms
> Average job execute time| 1126.57ms - should show 1s
> Total busy time | 70769ms - should show 1m 10s
> {code}
> Also please fix the typo 'Curent' - should be 'Current'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1793) [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1793:
---
Fix Version/s: (was: 1.7)
1.8
> [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs
> on TC sometimes
> -
>
> Key: IGNITE-1793
> URL: https://issues.apache.org/jira/browse/IGNITE-1793
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
> Attachments: test.logs
>
>
> IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes.
> Test hangs on IgniteCountDownLatch.count() method.
> {noformat}
> Thread [name="test-runner", id=24157, state=WAITING, blockCnt=0, waitCnt=96]
> Lock [object=o.a.i.i.util.future.GridFutureAdapter$ChainFuture@1e542154,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4525)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1544)
> at
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl$GetCountCallable.call(GridCacheCountDownLatchImpl.java:348)
> at
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl$GetCountCallable.call(GridCacheCountDownLatchImpl.java:342)
> at
> o.a.i.i.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:962)
> at
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl.count(GridCacheCountDownLatchImpl.java:143)
> at
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkRemovedLatch(IgniteCountDownLatchAbstractSelfTest.java:159)
> at
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkCountDown(IgniteCountDownLatchAbstractSelfTest.java:232)
> at
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkLatch(IgniteCountDownLatchAbstractSelfTest.java:84)
> at
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.testLatch(IgniteCountDownLatchAbstractSelfTest.java:72)
> 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
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at
> o.a.i.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1840) Exception in eviction manager on startup
[
https://issues.apache.org/jira/browse/IGNITE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1840:
---
Fix Version/s: (was: 1.7)
1.8
> Exception in eviction manager on startup
>
>
> Key: IGNITE-1840
> URL: https://issues.apache.org/jira/browse/IGNITE-1840
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
>
> It's rarely reproduced and looks like a race condition on startup. In some
> cases eviction backup worker start to work too early which leads to this
> exception on first iterations:
> {noformat}
> Exception in thread "cache-eviction-backup-worker-#40%null%"
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:423)
> at
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:397)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:352)
> at
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager$BackupWorker.body(GridCacheEvictionManager.java:1478)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1584) [Test Failed] IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap
[ https://issues.apache.org/jira/browse/IGNITE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1584: --- Fix Version/s: (was: 1.7) 1.8 > [Test Failed] > IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap > --- > > Key: IGNITE-1584 > URL: https://issues.apache.org/jira/browse/IGNITE-1584 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Blocker > Labels: Muted_test > Fix For: 1.8 > > Attachments: > IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap > > -- 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 ] Pavel Tupitsyn updated IGNITE-614: -- Fix Version/s: (was: 1.7) 1.8 > 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 > Labels: Muted_test > Fix For: 1.8 > > > 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-1338) SQL engine doesn't convert query fields name in upper case before using
[
https://issues.apache.org/jira/browse/IGNITE-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1338:
---
Fix Version/s: (was: 1.7)
1.8
> SQL engine doesn't convert query fields name in upper case before using
> ---
>
> Key: IGNITE-1338
> URL: https://issues.apache.org/jira/browse/IGNITE-1338
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Trivial
> Fix For: 1.8
>
> Attachments: test-cluster-2.xml
>
>
> Node can not be started if query fields name written in *lower case* and key
> fields with the *same* fields in *upper case* in cache type metadata.
> Please use attached configuration file for reproducing.
> {code}
> [14:30:28,526][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> class org.apache.ignite.IgniteCheckedException: Failed to register query
> type: TypeDescriptor [name=org.apache.ignite.Comalgorithm,
> fields={APCSBJCODE=class java.math.BigDecimal, APCID=class
> java.math.BigDecimal, AGRSBJCODE=class java.math.BigDecimal, AGRID=class
> java.math.BigDecimal, DAOSBJCODE=class java.math.BigDecimal, DAOID=class
> java.math.BigDecimal, CTPSBJCODE=class java.math.BigDecimal, CTPID=class
> java.math.BigDecimal, apcsbjcode=class java.math.BigDecimal, apcid=class
> java.math.BigDecimal, algcode=class java.math.BigDecimal,
> algisversioned=class java.lang.Short, algtype=class java.lang.Integer,
> algcalcobjecttype=class java.lang.Integer, algclasspath=class
> java.lang.String, algcomment=class java.lang.String, algopendate=class
> java.sql.Date, algclosedate=class java.sql.Date, algentstatus=class
> java.lang.Integer, agrsbjcode=class java.math.BigDecimal, agrid=class
> java.math.BigDecimal, daosbjcode=class java.math.BigDecimal, daoid=class
> java.math.BigDecimal, ctpsbjcode=class java.math.BigDecimal, ctpid=class
> java.math.BigDecimal, algusefields=class java.lang.String},
> indexes={FK1COMALGORITHM=IndexDescriptor [type=SORTED],
> FK3COMALGORITHM=IndexDescriptor [type=SORTED],
> FK4COMALGORITHM=IndexDescriptor [type=SORTED],
> SQL050208183448780=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
> keyCls=class java.lang.Object, valCls=class java.lang.Object,
> valTextIdx=false, registered=false]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1058)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:194)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:292)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1048)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:820)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:963)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546)
> at org.apache.ignite.Ignition.start(Ignition.java:346)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
> Caused by: org.h2.jdbc.JdbcSQLException: Повтор имени столбца "APCSBJCODE"
> Duplicate column name "APCSBJCODE"; SQL statement:
> CREATE TABLE "cache2".org_apache_ignite_Comalgorithm (_key OTHER NOT
> NULL,_val OTHER,APCSBJCODE DECIMAL,APCID DECIMAL,AGRSBJCODE DECIMAL,AGRID
> DECIMAL,DAOSBJCODE DECIMAL,DAOID DECIMAL,CTPSBJCODE DECIMAL,CTPID
> DECIMAL,apcsbjcode DECIMAL,apcid DECIMAL,algcode DECIMAL,algisversioned
> SMALLINT,algtype INT,algcalcobjecttype INT,algclasspath VARCHAR,algcomment
> VARCHAR,algopendate DATE,algclosedate DATE,algentstatus INT,agrsbjcode
> DECIMAL,agrid DECIMAL,daosbjcode DECIMAL,daoid DECIMAL,ctpsbjcode
> DECIMAL,ctpid DECIMAL,algusefields VARCHAR) engine
> "org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine"
> [42121-175]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java
[jira] [Updated] (IGNITE-1199) Spark integration: problem when start spark-shell with --jars
[
https://issues.apache.org/jira/browse/IGNITE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1199:
---
Fix Version/s: (was: 1.7)
1.8
> Spark integration: problem when start spark-shell with --jars
> --
>
> Key: IGNITE-1199
> URL: https://issues.apache.org/jira/browse/IGNITE-1199
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
> Environment: Cent OS
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1. Start spark master, worker and ignite node with default config
> 2. Start spark-shell:
> {noformat}
> $ ./spark-shell --jars
> /home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-spark/ignite-spark-1.3.2.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/cache-api-1.0.0.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-log4j/ignite-log4j-1.3.2.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-log4j/log4j-1.2.17.jar
> --master spark://fosters-218:7077
> log4j:WARN No appenders could be found for logger
> (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Using Spark's default log4j profile:
> org/apache/spark/log4j-defaults.properties
> 15/07/30 02:57:13 INFO SecurityManager: Changing view acls to: gridgain
> 15/07/30 02:57:13 INFO SecurityManager: Changing modify acls to: gridgain
> 15/07/30 02:57:13 INFO SecurityManager: SecurityManager: authentication
> disabled; ui acls disabled; users with view permissions: Set(gridgain); users
> with modify permissions: Set(gridgain)
> 15/07/30 02:57:13 INFO HttpServer: Starting HTTP Server
> 15/07/30 02:57:13 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:13 INFO AbstractConnector: Started
> SocketConnector@0.0.0.0:51608
> 15/07/30 02:57:13 INFO Utils: Successfully started service 'HTTP class
> server' on port 51608.
> Welcome to
> __
> / __/__ ___ _/ /__
> _\ \/ _ \/ _ `/ __/ '_/
>/___/ .__/\_,_/_/ /_/\_\ version 1.3.1
> /_/
> Using Scala version 2.10.4 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_75)
> Type in expressions to have them evaluated.
> Type :help for more information.
> 15/07/30 02:57:16 INFO SparkContext: Running Spark version 1.3.1
> 15/07/30 02:57:16 INFO SecurityManager: Changing view acls to: gridgain
> 15/07/30 02:57:16 INFO SecurityManager: Changing modify acls to: gridgain
> 15/07/30 02:57:16 INFO SecurityManager: SecurityManager: authentication
> disabled; ui acls disabled; users with view permissions: Set(gridgain); users
> with modify permissions: Set(gridgain)
> 15/07/30 02:57:16 INFO Slf4jLogger: Slf4jLogger started
> 15/07/30 02:57:16 INFO Remoting: Starting remoting
> 15/07/30 02:57:16 INFO Remoting: Remoting started; listening on addresses
> :[akka.tcp://sparkDriver@fosters-221:41342]
> 15/07/30 02:57:16 INFO Utils: Successfully started service 'sparkDriver' on
> port 41342.
> 15/07/30 02:57:16 INFO SparkEnv: Registering MapOutputTracker
> 15/07/30 02:57:16 INFO SparkEnv: Registering BlockManagerMaster
> 15/07/30 02:57:16 INFO DiskBlockManager: Created local directory at
> /tmp/spark-2630fb35-12f4-4e70-920f-30124a4b2657/blockmgr-5a7d7b6f-c296-4d16-82e3-14e020895ed8
> 15/07/30 02:57:16 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
> 15/07/30 02:57:16 INFO HttpFileServer: HTTP File server directory is
> /tmp/spark-6721e343-162b-4d45-bc55-eaadf103719d/httpd-0dc803d3-4bc4-4d23-8983-66c298f88c7d
> 15/07/30 02:57:16 INFO HttpServer: Starting HTTP Server
> 15/07/30 02:57:16 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:16 INFO AbstractConnector: Started
> SocketConnector@0.0.0.0:41602
> 15/07/30 02:57:16 INFO Utils: Successfully started service 'HTTP file server'
> on port 41602.
> 15/07/30 02:57:16 INFO SparkEnv: Registering OutputCommitCoordinator
> 15/07/30 02:57:17 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:17 INFO AbstractConnector: Started
> SelectChannelConnector@0.0.0.0:4040
> 15/07/30 02:57:17 INFO Utils: Successfully started service 'SparkUI' on port
> 4040.
> 15/07/30 02:57:17 INFO SparkUI: Started SparkUI at http://fosters-221:4040
> 15/07/30 02:57:17 INFO SparkContext: Added JAR
> file:/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-spark/ignite-spark-1.3.2.jar
> at http://10.20.0.221:41602/jars/ignite-spark-1.3.2.jar with timestamp
> 1438250237070
> 15/07/30 02:57:17 INFO SparkContext: Added JAR
> file:/home/gridgain/isuntsov/gridgain-c
[jira] [Updated] (IGNITE-1268) CacheAPIExample should have non-empty result
[
https://issues.apache.org/jira/browse/IGNITE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1268:
---
Fix Version/s: (was: 1.7)
1.8
> CacheAPIExample should have non-empty result
> -
>
> Key: IGNITE-1268
> URL: https://issues.apache.org/jira/browse/IGNITE-1268
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
> Environment: Ubuntu 14.04, apache-ignite-1.3.0-incubating
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Fix For: 1.8
>
>
> -
> DESCRIPTION
> -
> CacheAPIExample have empty result. It's non informational and non
> user-friendly.
> -
> STEPS FOR REPRODUCE
> -
> 1. Download apache-ignite-1.3.0-incubating from ignite.apache.org
> 2. Build examples in the IDE
> 3. Run CacheAPIExample
> -
> ACTUAL RESULT
> -
> CacheAPIExample have empty result:
> {noformat}
> >>> Cache API example started.
> >>> Cache atomic map operation examples.
> {noformat}
> -
> EXPECTED RESULT
> -
> CacheAPIExample have informational result. It could be, for example, the
> information about cache contents before and after put operations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1574) Exception is not rethrown on client side if entry processor fails during commit
[ https://issues.apache.org/jira/browse/IGNITE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1574: --- Fix Version/s: (was: 1.7) 1.8 > Exception is not rethrown on client side if entry processor fails during > commit > --- > > Key: IGNITE-1574 > URL: https://issues.apache.org/jira/browse/IGNITE-1574 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko > Fix For: 1.8 > > > See user@ thread: > http://apache-ignite-users.70518.x6.nabble.com/CacheEntryProcessor-failing-on-transactional-cache-td1501.html > Entry processor fails during commit, transaction is correctly rolled back, > but the exception is not rethrown to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1090) GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
[
https://issues.apache.org/jira/browse/IGNITE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1090:
---
Fix Version/s: (was: 1.7)
1.8
> GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
> --
>
> Key: IGNITE-1090
> URL: https://issues.apache.org/jira/browse/IGNITE-1090
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Critical
> Labels: Muted_test
> Fix For: 1.8
>
>
> The test hangs with the following errors:
> {noformat}
> [16:26:33] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Map reducer: {}, init=true,
> res=java.util.concurrent.atomic.AtomicMarkableReference@3c6fff03, err=null,
> done=false, cancelled=false, err=null, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Failed to wait for topology version
> to change: AffinityTopologyVersion [topVer=274, minorTopVer=0]
> at
> org.apache.ignite.internal.processors.cache.distributed.GridFutureRemapTimeoutObject.onTimeout(GridFutureRemapTimeoutObject.java:64)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Remote
> node left grid (will retry): 703c58e1-e099-4f22-b5c3-6c3676338007
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onNodeLeft(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:186)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1719)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1910)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1758)
> ... 2 more
> {noformat}
> This issue appeared after IGNITE-882 was fixed. Until it wasn't fixed the
> tests hung because of this issue:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Remote node ID is
> not as expected [expected=9019c94c-84f5-4065-89b1-f16fdf708009,
> rcvd=707ed613-1b65-4771-ac98-5faa6857e007]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2203)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2025)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-878) Large GC if load data to the cache using datastreamer
[ https://issues.apache.org/jira/browse/IGNITE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-878: -- Fix Version/s: (was: 1.7) 1.8 > Large GC if load data to the cache using datastreamer > -- > > Key: IGNITE-878 > URL: https://issues.apache.org/jira/browse/IGNITE-878 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-4 >Reporter: Pavel Konstantinov >Assignee: Sergi Vladykin > Fix For: 1.8 > > Attachments: #_IGNITE-878_GC_using_on_data_streaming_test.patch, > ig-878.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-768) Failed to start LOCAL cache on part of the grid
[
https://issues.apache.org/jira/browse/IGNITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-768:
--
Fix Version/s: (was: 1.7)
1.8
> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
>Assignee: Anton Vinogradov
> Fix For: 1.8
>
> Attachments:
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException:
> Failed to start cache (a cache with the same name is already started):
> local-nid
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
> at
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1776) [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1776:
---
Fix Version/s: (was: 1.7)
1.8
> [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails
> sometimes
> ---
>
> Key: IGNITE-1776
> URL: https://issues.apache.org/jira/browse/IGNITE-1776
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Blocker
> Labels: Muted_test
> Fix For: 1.8
>
>
> TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails on TC
> sometimes.
> Looks like a test bug, need just increase awaitTime(). I see Node FAILED
> message exactly after 10 seconds. But it's strange that it's require too long
> time. May be something wrong on agent.
> Logs:
> {noformat}
> junit.framework.AssertionFailedError: Latch count: 1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.await(TcpClientDiscoverySpiSelfTest.java:2030)
> at
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer(TcpClientDiscoverySpiSelfTest.java:811)
> --- Stdout: ---
> [03:18:46,228][INFO ][main][root] >>> Starting test:
> testClientNodeFailOneServer <<<
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0]
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Config URL: n/a
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Daemon mode: off
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS: Mac OS X 10.7.5
> x86_64
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS user: teamcity
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Language runtime:
> Java Platform API Specification ver. 1.7
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM information:
> Java(TM) SE Runtime Environment 1.7.0_67-b01 Oracle Corporation Java
> HotSpot(TM) 64-Bit Server VM 24.65-b04
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM total memory:
> 2.7GB
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Remote Management
> [restart: off, REST: off, JMX (remote: off)]
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0]
> IGNITE_HOME=/Users/teamcity/buildAgent/work/871ff4a46e450b13
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM arguments:
> [-DJAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home,
> -DMCAST_GRP=229.116.1.2, -Dagent.home.dir=/Users/teamcity/buildAgent,
> -Dagent.name=ip_192.168.1.116, -Dagent.ownPort=9090,
> -Dagent.work.dir=/Users/teamcity/buildAgent/work, -Dbuild.number=3345,
> -Dbuild.vcs.number=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
> -Dbuild.vcs.number.1=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
> -Dbuild.vcs.number.ApacheIgniteMirrorOnGitHub=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
>
> -Dclassworlds.conf=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.m2.conf,
> -Dcom.jetbrains.maven.watcher.report.file=/Users/teamcity/buildAgent/temp/buildTmp/maven-build-info.xml,
> -Djava.io.tmpdir=/Users/teamcity/buildAgent/temp/buildTmp,
> -Dmaven.home=/Users/teamcity/buildAgent/tools/maven3,
> -Dmaven.repo.local=/Users/teamcity/.m2/repository,
> -Dteamcity.agent.cpuBenchmark=605,
> -Dteamcity.agent.dotnet.agent_url=http://localhost:9090/RPC2,
> -Dteamcity.agent.dotnet.build_id=555612,
> -Dteamcity.auth.password=j1gKlVPBOa3H6Wnrjp3Q3sK7ZqR4biuf,
> -Dteamcity.auth.userId=TeamCityBuildId=555612,
> -Dteamcity.build.changedFiles.file=/Users/teamcity/buildAgent/temp/buildTmp/changedFiles5940678572218707636.txt,
>
> -Dteamcity.build.checkoutDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13,
> -Dteamcity.build.id=555612,
> -Dteamcity.build.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.build3844607694634646095.properties,
> -Dteamcity.build.tempDir=/Users/teamcity/buildAgent/temp/buildTmp,
> -Dteamcity.build.workingDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13,
> -Dteamcity.buildConfName=Ignite SPI, -Dteamcity.buildType.id=Ignite_Spi,
> -Dteamcity.configuration.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.config8915518964213838573.properties,
> -Dteamcity.idea.home=/Users/teamcity/buildAgent/plugins/idea,
[jira] [Updated] (IGNITE-1604) Provide ability to get notification on rebalancing finish
[ https://issues.apache.org/jira/browse/IGNITE-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1604: --- Fix Version/s: (was: 1.7) 1.8 > Provide ability to get notification on rebalancing finish > - > > Key: IGNITE-1604 > URL: https://issues.apache.org/jira/browse/IGNITE-1604 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Anton Vinogradov > Fix For: 1.8 > > > It would be nice if user have ability to wait until rebalancing is finished > across whole topology on current topology version. > Need to add method: > * Future IgniteCache.rebalanceFuture(); > * Future IgniteCache.localRebalanceFuture(); > If currently no rebalancing is running, finished future is returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2097) Splitting Query example
[
https://issues.apache.org/jira/browse/IGNITE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-2097:
---
Fix Version/s: (was: 1.7)
1.8
> Splitting Query example
> ---
>
> Key: IGNITE-2097
> URL: https://issues.apache.org/jira/browse/IGNITE-2097
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4, 1.5.0.final
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.8
>
>
> CacheQueryExample is overloaded by query features. What's about to introduce
> a new package e.g. called {{org.apache.ignite.examples.query}} and split
> {{org.apache.ignite.examples.datagrid.CacheQueryExample}} into separate
> examples like:
> QueryScanExample
> QueryJoinExample
> QueryTextExample
> QueryAggregationExample
> QueryFieldsExample
> QueryFieldsJoinExample
> And add new ones:
> QueryCrossCacheExample
> QueryExplainExample
> upd YZ: I think this should be done in separate package
> {{org.apache.ignite.examples.datagrid.query}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized
[
https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1238:
---
Fix Version/s: (was: 1.7)
1.8
> Joining node should be discarded in case discovery exchange data can't be
> deserialized
> --
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: 1.8
>
>
> Currently a node will join even if unmarshalling fails (see
> {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected
> behaviour. For example, a continuous query listener is not deployed on some
> nodes in topology. Everything works, but some updates are lost. We should
> discard the node in this case and give a good error message to user with
> information on how to fix it properly.
--
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 ] Pavel Tupitsyn updated IGNITE-1192: --- Fix Version/s: (was: 1.7) 1.8 > 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: Eduard Shangareev >Priority: Minor > Labels: Newbie > Fix For: 1.8 > > > 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-1606) NPE during node stop due to nullified logger in TcpCommunicationSpi
[
https://issues.apache.org/jira/browse/IGNITE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1606:
---
Fix Version/s: (was: 1.7)
1.8
> NPE during node stop due to nullified logger in TcpCommunicationSpi
> ---
>
> Key: IGNITE-1606
> URL: https://issues.apache.org/jira/browse/IGNITE-1606
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Valentin Kulichenko
> Fix For: 1.8
>
>
> Probably we should check other components as well. Not sure why we need to
> nullify logger.
> {noformat}
> Exception in thread "ignite-#101%sys-t1-1%" java.lang.NullPointerException
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1896)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1880)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1066)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1214)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1071)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1034)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1017)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processNotification(GridContinuousProcessor.java:851)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$1500(GridContinuousProcessor.java:85)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.onMessage(GridContinuousProcessor.java:556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
