[jira] [Comment Edited] (IGNITE-640) Implement IgniteMultimap data structures
[
https://issues.apache.org/jira/browse/IGNITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606116#comment-16606116
]
Amir Akhmedov edited comment on IGNITE-640 at 9/6/18 5:28 PM:
--
[~avinogradov],
In this [#comment-16520147] you mentioned to create an **AbsractMap** that
IgniteSet and IgniteMultimap could inherit. But the problem is IgniteSet
already extends AbstractCollection. Do you think it's still an option to have a
common abstract parent class for both Set and Multimap?
I can come up with solution to rename Set "header" classes to Map and reuse an
existing code as much as possible but I don't see how to combine the
implementation of Set and Map so far. Any thoughts?
was (Author: aakhmedov):
[~avinogradov],
In this [#comment-16520147] you mentioned to create an **AbsractMap** that
IgniteSet and IgniteMultimap could inherit. But the problem is IgniteSet
already extends AbstractCollection. Do you think it's still an option to have a
common abstract parent class for both Set and Multimap?
> Implement IgniteMultimap data structures
>
>
> Key: IGNITE-640
> URL: https://issues.apache.org/jira/browse/IGNITE-640
> Project: Ignite
> Issue Type: Sub-task
> Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Amir Akhmedov
>Priority: Major
> Fix For: 2.7
>
>
> We need to add {{IgniteMultimap}} data structure in addition to other data
> structures provided by Ignite. {{IgniteMultiMap}} should have similar API to
> {{java.util.Map}} class in JDK, but support the semantics of multiple values
> per key, similar to [Guava
> Multimap|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/collect/Multimap.html].
>
> However, unlike in Guava, our multi-map should work with Lists, not
> Collections. Lists should make it possible to support the following methods:
> {code}
> // Gets value at a certain index for a key.
> V get(K, index);
> // Gets all values for a collection of keys at a certain index.
> Map getAll(Collection, index);
> // Gets values for specified indexes for a key.
> List get(K, Iterable indexes);
> // Gets all values for a collection of keys at specified indexes.
> Map> getAll(Collection, Iterable indexes);
> // Gets values for specified range of indexes, between min and max.
> List get(K, int min, int max);
> // Gets all values for a collection of keys for a specified index range,
> between min and max.
> Map> getAll(Collection, int min, int max);
> // Gets all values for a specific key.
> List get(K);
> // Gets all values for a collection of keys.
> Map> getAll(Collection);
> // Iterate through all elements with a certain index.
> Iterator> iterate(int idx);
> // Do we need this?
> Collection> get(K, IgniteBiPredicate)
> {code}
> Multimap should also support colocated and non-colocated modes, similar to
> [IgniteQueue|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteQueue.java]
> and its implementation,
> [GridAtomicCacheQueueImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridAtomicCacheQueueImpl.java].
> h2. Design Details
> The most natural way to implement such map, would be to store every value
> under a separate key in an Ignite cache. For example, let's say that we have
> a key {{K}} with multiple values: {{V0, V1, V2, ...}}. Then the cache should
> end up with the following values {{K0, V0}}, {{K1, V1}}, {{K2, V2}}, etc.
> This means that we need to wrap user key into our own, internal key, which
> will also have {{index}} field.
> Also note that we need to collocate all the values for the same key on the
> same node, which means that we need to define user key K as the affinity key,
> like so:
> {code}
> class MultiKey {
> @CacheAffinityMapped
> private K key;
> int index;
> }
> {code}
> Look ups of values at specific indexes becomes very simple. Just attach a
> specific index to a key and do a cache lookup. Look ups for all values for a
> key should work as following:
> {code}
> MultiKey key;
> V v = null;
> int index = 0;
> List res = new LinkedList<>();
> do {
> v = cache.get(MultiKey(K, index));
> if (v != null)
> res.add(v);
> index++;
> }
> while (v != null);
> return res;
> {code}
> We could also use batching for performance reason. In this case the batch
> size should be configurable.
> {code}
> int index = 0;
> List res = new LinkedList<>();
> while (true) {
> List batch = new ArrayList<>(batchSize);
> // Populate batch.
> for (; index < batchSize; index++)
> batch.add(new MultiKey(K, index % batchSize);
> Map batchRes = cache.getAll(batch);
> // Potentially
[jira] [Commented] (IGNITE-640) Implement IgniteMultimap data structures
[
https://issues.apache.org/jira/browse/IGNITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16606116#comment-16606116
]
Amir Akhmedov commented on IGNITE-640:
--
[~avinogradov],
In this [#comment-16520147] you mentioned to create an **AbsractMap** that
IgniteSet and IgniteMultimap could inherit. But the problem is IgniteSet
already extends AbstractCollection. Do you think it's still an option to have a
common abstract parent class for both Set and Multimap?
> Implement IgniteMultimap data structures
>
>
> Key: IGNITE-640
> URL: https://issues.apache.org/jira/browse/IGNITE-640
> Project: Ignite
> Issue Type: Sub-task
> Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Amir Akhmedov
>Priority: Major
> Fix For: 2.7
>
>
> We need to add {{IgniteMultimap}} data structure in addition to other data
> structures provided by Ignite. {{IgniteMultiMap}} should have similar API to
> {{java.util.Map}} class in JDK, but support the semantics of multiple values
> per key, similar to [Guava
> Multimap|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/collect/Multimap.html].
>
> However, unlike in Guava, our multi-map should work with Lists, not
> Collections. Lists should make it possible to support the following methods:
> {code}
> // Gets value at a certain index for a key.
> V get(K, index);
> // Gets all values for a collection of keys at a certain index.
> Map getAll(Collection, index);
> // Gets values for specified indexes for a key.
> List get(K, Iterable indexes);
> // Gets all values for a collection of keys at specified indexes.
> Map> getAll(Collection, Iterable indexes);
> // Gets values for specified range of indexes, between min and max.
> List get(K, int min, int max);
> // Gets all values for a collection of keys for a specified index range,
> between min and max.
> Map> getAll(Collection, int min, int max);
> // Gets all values for a specific key.
> List get(K);
> // Gets all values for a collection of keys.
> Map> getAll(Collection);
> // Iterate through all elements with a certain index.
> Iterator> iterate(int idx);
> // Do we need this?
> Collection> get(K, IgniteBiPredicate)
> {code}
> Multimap should also support colocated and non-colocated modes, similar to
> [IgniteQueue|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteQueue.java]
> and its implementation,
> [GridAtomicCacheQueueImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridAtomicCacheQueueImpl.java].
> h2. Design Details
> The most natural way to implement such map, would be to store every value
> under a separate key in an Ignite cache. For example, let's say that we have
> a key {{K}} with multiple values: {{V0, V1, V2, ...}}. Then the cache should
> end up with the following values {{K0, V0}}, {{K1, V1}}, {{K2, V2}}, etc.
> This means that we need to wrap user key into our own, internal key, which
> will also have {{index}} field.
> Also note that we need to collocate all the values for the same key on the
> same node, which means that we need to define user key K as the affinity key,
> like so:
> {code}
> class MultiKey {
> @CacheAffinityMapped
> private K key;
> int index;
> }
> {code}
> Look ups of values at specific indexes becomes very simple. Just attach a
> specific index to a key and do a cache lookup. Look ups for all values for a
> key should work as following:
> {code}
> MultiKey key;
> V v = null;
> int index = 0;
> List res = new LinkedList<>();
> do {
> v = cache.get(MultiKey(K, index));
> if (v != null)
> res.add(v);
> index++;
> }
> while (v != null);
> return res;
> {code}
> We could also use batching for performance reason. In this case the batch
> size should be configurable.
> {code}
> int index = 0;
> List res = new LinkedList<>();
> while (true) {
> List batch = new ArrayList<>(batchSize);
> // Populate batch.
> for (; index < batchSize; index++)
> batch.add(new MultiKey(K, index % batchSize);
> Map batchRes = cache.getAll(batch);
> // Potentially need to properly sort values, based on the key order,
> // if the returning map does not do it automatically.
> res.addAll(batchRes.values());
> if (res.size() < batch.size())
> break;
> }
> return res;
> {code}
> h2. Evictions
> Evictions in the {{IgniteMultiMap}} should have 2 levels: maximum number of
> keys, and maximum number of values for a key. The maximum number of keys
> should be controlled by Ignite standard eviction policy. The maximum number
> of values for a key should be controlled by the implementation of the
> multi-map. Either eviction
[jira] [Assigned] (IGNITE-9282) [ML] Add Naive Bayes classifier
[ https://issues.apache.org/jira/browse/IGNITE-9282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravil Galeyev reassigned IGNITE-9282: - Assignee: Ravil Galeyev > [ML] Add Naive Bayes classifier > --- > > Key: IGNITE-9282 > URL: https://issues.apache.org/jira/browse/IGNITE-9282 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Ravil Galeyev >Priority: Major > > Naive Bayes classifiers are a family of simple probabilistic classifiers > based on applying Bayes' theorem with strong (naive) independence assumptions > between the features. > So we want to add this algorithm to Apache Ignite ML module. > Ideally, implementation should support both multinomial naive Bayes and > Bernoulli naive Bayes. > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9489) CorruptedTreeException on index create.
[
https://issues.apache.org/jira/browse/IGNITE-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-9489:
-
Ignite Flags: (was: Docs Required)
> CorruptedTreeException on index create.
> ---
>
> Key: IGNITE-9489
> URL: https://issues.apache.org/jira/browse/IGNITE-9489
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.4, 2.5, 2.6
>Reporter: Igor Seliverstov
>Priority: Major
> Attachments: Test.java
>
>
> Currently on dynamic index drop with enabled persistence H2TreeIndex
> instances aren't destroyed. That means that their root pages aren't removed
> from meta tree (see
> {{org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getOrAllocateForTree}})
> and reused on subsequent dynamic index create that leads
> CorruptedTreeException on initial index rebuild because there are some items
> with broken links on the root page.
> Reproducer attached.
> Error log:
> {noformat}
> Error during parallel index create/rebuild.
> org.h2.message.DbException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:295)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:251)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.apply(IgniteH2Indexing.java:890)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4320)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:244)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:207)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartitions(SchemaIndexCacheVisitorImpl.java:166)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.access$100(SchemaIndexCacheVisitorImpl.java:50)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl$AsyncWorker.body(SchemaIndexCacheVisitorImpl.java:317)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 12 more
> Caused by: class
>
[jira] [Updated] (IGNITE-9489) CorruptedTreeException on index create.
[
https://issues.apache.org/jira/browse/IGNITE-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-9489:
-
Description:
Currently on dynamic index drop with enabled persistence H2TreeIndex instances
aren't destroyed. That means that their root pages aren't removed from meta
tree (see
{{org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getOrAllocateForTree}})
and reused on subsequent dynamic index create that leads
CorruptedTreeException on initial index rebuild because there are some items
with broken links on the root page.
Reproducer attached.
Error log:
{noformat}
Error during parallel index create/rebuild.
org.h2.message.DbException: Внутренняя ошибка: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on row: Row@7745722d[ key:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
[idHash=2038596277, hash=-1388553726, id=1], val:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
[idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
[topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
General error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on row: Row@7745722d[ key:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
[idHash=2038596277, hash=-1388553726, id=1], val:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
[idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
[topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
[5-195]
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convert(DbException.java:295)
at
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:251)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.apply(IgniteH2Indexing.java:890)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4320)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:244)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:207)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartitions(SchemaIndexCacheVisitorImpl.java:166)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.access$100(SchemaIndexCacheVisitorImpl.java:50)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl$AsyncWorker.body(SchemaIndexCacheVisitorImpl.java:317)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on row: Row@7745722d[ key:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
[idHash=2038596277, hash=-1388553726, id=1], val:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
[idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
[topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
General error: "class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on row: Row@7745722d[ key:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
[idHash=2038596277, hash=-1388553726, id=1], val:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
[idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
[topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
[5-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
... 12 more
Caused by: class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on row: Row@7745722d[ key:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
[idHash=2038596277, hash=-1388553726, id=1], val:
org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
[idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
[topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2285)
at
[jira] [Created] (IGNITE-9489) CorruptedTreeException on index create.
Igor Seliverstov created IGNITE-9489:
Summary: CorruptedTreeException on index create.
Key: IGNITE-9489
URL: https://issues.apache.org/jira/browse/IGNITE-9489
Project: Ignite
Issue Type: Bug
Components: cache, sql
Affects Versions: 2.6, 2.5, 2.4
Reporter: Igor Seliverstov
Attachments: Test.java
Currently on dynamic index drop with enabled persistence H2TreeIndex instances
aren't destroyed. That means that their root pages aren't removed from meta
tree (see
{{org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getOrAllocateForTree}})
and reused on subsequent dynamic index create that leads
CorruptedTreeException on initial index rebuild because there are some items
with broken links on the root page.
Reproducer attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9212) Uncomment 18 test classes in various modules' sutes (see inside)
[
https://issues.apache.org/jira/browse/IGNITE-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605981#comment-16605981
]
Ilya Kasnacheev commented on IGNITE-9212:
-
Not sure if everything will pass right away
> Uncomment 18 test classes in various modules' sutes (see inside)
>
>
> Key: IGNITE-9212
> URL: https://issues.apache.org/jira/browse/IGNITE-9212
> Project: Ignite
> Issue Type: Sub-task
> Components: clients, hadoop, hibernate, jdbc, spring, zookeeper
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> As per the following test suites:
> {code}
> 4
> modules/clients/src/test/java/org/apache/ignite/internal/client/suite/IgniteClientTestSuite.java
> 1
> modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
> 4
> modules/hadoop/src/test/java/org/apache/ignite/testsuites/IgniteHadoopTestSuite.java
> 1
> modules/hadoop/src/test/java/org/apache/ignite/testsuites/IgniteIgfsLinuxAndMacOSTestSuite.java
> 1
> modules/hibernate-4.2/src/test/java/org/apache/ignite/testsuites/IgniteHibernateTestSuite.java
> 1
> modules/hibernate-5.1/src/test/java/org/apache/ignite/testsuites/IgniteHibernate5TestSuite.java
> 2
> modules/spring/src/test/java/org/apache/ignite/testsuites/IgniteSpringTestSuite.java
> 3
> modules/urideploy/src/test/java/org/apache/ignite/testsuites/IgniteUriDeploymentTestSuite.java
> 1
> modules/zookeeper/src/test/java/org/apache/ignite/spi/discovery/zk/ZookeeperDiscoverySpiTestSuite1.java
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9212) Uncomment 18 test classes in various modules' sutes (see inside)
[
https://issues.apache.org/jira/browse/IGNITE-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605965#comment-16605965
]
ASF GitHub Bot commented on IGNITE-9212:
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4700
IGNITE-9212 Uncomment or explain various commented out tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9212
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4700.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 #4700
commit a03273ae00185af6fbc4c4f64e6266465aa41c09
Author: Ilya Kasnacheev
Date: 2018-09-06T15:49:07Z
IGNITE-9212 Uncomment or explain various commented out tests.
> Uncomment 18 test classes in various modules' sutes (see inside)
>
>
> Key: IGNITE-9212
> URL: https://issues.apache.org/jira/browse/IGNITE-9212
> Project: Ignite
> Issue Type: Sub-task
> Components: clients, hadoop, hibernate, jdbc, spring, zookeeper
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> As per the following test suites:
> {code}
> 4
> modules/clients/src/test/java/org/apache/ignite/internal/client/suite/IgniteClientTestSuite.java
> 1
> modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
> 4
> modules/hadoop/src/test/java/org/apache/ignite/testsuites/IgniteHadoopTestSuite.java
> 1
> modules/hadoop/src/test/java/org/apache/ignite/testsuites/IgniteIgfsLinuxAndMacOSTestSuite.java
> 1
> modules/hibernate-4.2/src/test/java/org/apache/ignite/testsuites/IgniteHibernateTestSuite.java
> 1
> modules/hibernate-5.1/src/test/java/org/apache/ignite/testsuites/IgniteHibernate5TestSuite.java
> 2
> modules/spring/src/test/java/org/apache/ignite/testsuites/IgniteSpringTestSuite.java
> 3
> modules/urideploy/src/test/java/org/apache/ignite/testsuites/IgniteUriDeploymentTestSuite.java
> 1
> modules/zookeeper/src/test/java/org/apache/ignite/spi/discovery/zk/ZookeeperDiscoverySpiTestSuite1.java
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9419) Avoid saving cache configuration synchronously during PME
[ https://issues.apache.org/jira/browse/IGNITE-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605879#comment-16605879 ] Ilya Lantukh edited comment on IGNITE-9419 at 9/6/18 3:48 PM: -- [~Jokser], Thanks for contribution! In my opinion, adding public-mutable GridDhtPartitionsExchangeFuture.registerCachesFuture breaks encapsulation. Is it possible to re-design your solution to make this field modifiable only by ExchangeFuture itself? Also, please add tests for this functionality. was (Author: ilantukh): [~Jokser], Thanks for contribution! In my opinion, adding publicly-mutable GridDhtPartitionsExchangeFuture.registerCachesFuture breaks encapsulation. Is it possible to re-design your solution to make this field modifiable only by ExchangeFuture itself? Also, please add tests for this functionality. > Avoid saving cache configuration synchronously during PME > - > > Key: IGNITE-9419 > URL: https://issues.apache.org/jira/browse/IGNITE-9419 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > Currently, we save cache configuration during PME at the activation phase > here > org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.CachesInfo#updateCachesInfo > . We should avoid this, as it performs operations to a disk. We should save > it asynchronously or lazy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9488) GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs
[ https://issues.apache.org/jira/browse/IGNITE-9488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Cherkasov reassigned IGNITE-9488: - Assignee: Mikhail Cherkasov > GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs > --- > > Key: IGNITE-9488 > URL: https://issues.apache.org/jira/browse/IGNITE-9488 > Project: Ignite > Issue Type: Bug >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov >Priority: Minor > > GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9488) GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs
Mikhail Cherkasov created IGNITE-9488: - Summary: GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs Key: IGNITE-9488 URL: https://issues.apache.org/jira/browse/IGNITE-9488 Project: Ignite Issue Type: Bug Reporter: Mikhail Cherkasov GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9482) [ML] Refactor all trainers' settters to withFieldName format for meta-algorithms
[ https://issues.apache.org/jira/browse/IGNITE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605940#comment-16605940 ] ASF GitHub Bot commented on IGNITE-9482: GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4699 IGNITE-9482: added correct setters and getters for all main trainers You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9482 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4699.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 #4699 commit 4b928277e315634d4885a695b461e9d5a973797b Author: Zinoviev Alexey Date: 2018-09-06T15:31:34Z IGNITE-9482: added correct setters and getters for all main trainers > [ML] Refactor all trainers' settters to withFieldName format for > meta-algorithms > > > Key: IGNITE-9482 > URL: https://issues.apache.org/jira/browse/IGNITE-9482 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.7 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-9084) Trash in WAL after node stop may affect WAL rebalance
[
https://issues.apache.org/jira/browse/IGNITE-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh updated IGNITE-9084:
-
Comment: was deleted
(was: [~Jokser],
Thanks for contribution!
I've reviewed your PR, you can find my comments here:
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-760.)
> Trash in WAL after node stop may affect WAL rebalance
> -
>
> Key: IGNITE-9084
> URL: https://issues.apache.org/jira/browse/IGNITE-9084
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.7
>
>
> During iteration over WAL we can face with trash in WAL segment, which can
> remains after node restart. We should handle this situation in WAL rebalance
> iterator and gracefully stop iteration process.
> {noformat}
> [2018-07-25
> 17:18:21,152][ERROR][sys-#25385%persistence.IgnitePdsTxHistoricalRebalancingTest0%][GridCacheIoManager]
> Failed to process message [senderId=f0d35df7-ff93-4b6c-b699-45f3e7c3,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 19346739 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1033)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:948)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:917)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:842)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:348)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:370)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:365)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2752)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1516)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1485)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 19346739 size: 67108864
> at
>
[jira] [Commented] (IGNITE-9084) Trash in WAL after node stop may affect WAL rebalance
[
https://issues.apache.org/jira/browse/IGNITE-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605924#comment-16605924
]
Ilya Lantukh commented on IGNITE-9084:
--
[~Jokser],
Thanks for contribution!
I've reviewed your PR, you can find my comments here:
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-760.
> Trash in WAL after node stop may affect WAL rebalance
> -
>
> Key: IGNITE-9084
> URL: https://issues.apache.org/jira/browse/IGNITE-9084
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.7
>
>
> During iteration over WAL we can face with trash in WAL segment, which can
> remains after node restart. We should handle this situation in WAL rebalance
> iterator and gracefully stop iteration process.
> {noformat}
> [2018-07-25
> 17:18:21,152][ERROR][sys-#25385%persistence.IgnitePdsTxHistoricalRebalancingTest0%][GridCacheIoManager]
> Failed to process message [senderId=f0d35df7-ff93-4b6c-b699-45f3e7c3,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 19346739 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1033)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:948)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:917)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:842)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:348)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:370)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:365)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2752)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1516)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1485)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 19346739 size: 67108864
> at
>
[jira] [Commented] (IGNITE-9084) Trash in WAL after node stop may affect WAL rebalance
[
https://issues.apache.org/jira/browse/IGNITE-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605918#comment-16605918
]
ASF GitHub Bot commented on IGNITE-9084:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4437
> Trash in WAL after node stop may affect WAL rebalance
> -
>
> Key: IGNITE-9084
> URL: https://issues.apache.org/jira/browse/IGNITE-9084
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.7
>
>
> During iteration over WAL we can face with trash in WAL segment, which can
> remains after node restart. We should handle this situation in WAL rebalance
> iterator and gracefully stop iteration process.
> {noformat}
> [2018-07-25
> 17:18:21,152][ERROR][sys-#25385%persistence.IgnitePdsTxHistoricalRebalancingTest0%][GridCacheIoManager]
> Failed to process message [senderId=f0d35df7-ff93-4b6c-b699-45f3e7c3,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandMessage]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 19346739 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1033)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:948)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:917)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:842)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:348)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:370)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:365)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2752)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1516)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1485)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 19346739 size: 67108864
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:263)
> at
>
[jira] [Assigned] (IGNITE-9487) REST: getall can only output keys as scalars
[
https://issues.apache.org/jira/browse/IGNITE-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev reassigned IGNITE-9487:
---
Assignee: Ilya Kasnacheev
> REST: getall can only output keys as scalars
>
>
> Key: IGNITE-9487
> URL: https://issues.apache.org/jira/browse/IGNITE-9487
> Project: Ignite
> Issue Type: Improvement
> Components: rest
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> Regardless of what ConnectorMessageInterceptor does, `getall' command can
> only output key as string or number, and not as JSON object as values can.
> This is because output format is as follows:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":{"CustomType
> [idHash=1588995554, hash=34706515, key=111]":{"val":"111"},"CustomType
> [idHash=978025370, hash=30386820, key=222]":{"val":"222"}},"error":null}
> {code}
> The desired output format may look like:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":[{"key":{"key":111},"value":{"val":"111"}},{"key":{"key":222},"value":{"val":"222"}}],"error":null}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9487) REST: getall can only output keys as scalars
Ilya Kasnacheev created IGNITE-9487:
---
Summary: REST: getall can only output keys as scalars
Key: IGNITE-9487
URL: https://issues.apache.org/jira/browse/IGNITE-9487
Project: Ignite
Issue Type: Improvement
Components: rest
Reporter: Ilya Kasnacheev
Regardless of what ConnectorMessageInterceptor does, `getall' command can only
output key as string or number, and not as JSON object as values can.
This is because output format is as follows:
{code}
{"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":{"CustomType
[idHash=1588995554, hash=34706515, key=111]":{"val":"111"},"CustomType
[idHash=978025370, hash=30386820, key=222]":{"val":"222"}},"error":null}
{code}
The desired output format may look like:
{code}
{"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":[{"key":{"key":111},"value":{"val":"111"}},{"key":{"key":222},"value":{"val":"222"}}],"error":null}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9486) JobStealing doesn't work with affinityRun
Evgenii Zhuravlev created IGNITE-9486:
-
Summary: JobStealing doesn't work with affinityRun
Key: IGNITE-9486
URL: https://issues.apache.org/jira/browse/IGNITE-9486
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Evgenii Zhuravlev
It rebalances job to the node, that doesn't have needed partition, which lead
to the exception:
{code:java}
[2018-09-06 18:03:47,545][ERROR][pub-#61][GridJobWorker] Failed to lock
partitions [jobId=a29f86fa561-3e2c91e1-1f47-401c-80a2-ea2b452a3cb5,
ses=GridJobSessionImpl [ses=GridTaskSessionImpl
[taskName=o.a.i.examples.ExampleNodeStartup3$1, dep=GridDeployment
[ts=1536246214786, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
clsLdrId=606b86fa561-cffc6951-7eef-4a58-82e1-69511458d650, userVer=0, loc=true,
sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
pendingUndeploy=false, undeployed=false, usage=1],
taskClsName=o.a.i.examples.ExampleNodeStartup3$1,
sesId=929f86fa561-3e2c91e1-1f47-401c-80a2-ea2b452a3cb5,
startTime=1536246223300, endTime=9223372036854775807,
taskNodeId=3e2c91e1-1f47-401c-80a2-ea2b452a3cb5,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=false,
topPred=null, subjId=3e2c91e1-1f47-401c-80a2-ea2b452a3cb5, mapFut=IgniteFuture
[orig=GridFutureAdapter [ignoreInterrupts=false, state=INIT, res=null,
hash=30355072]], execName=null],
jobId=a29f86fa561-3e2c91e1-1f47-401c-80a2-ea2b452a3cb5]]
class org.apache.ignite.IgniteException: Failed partition reservation.
Partition is not primary on the node. [partition=1, cacheName=test,
nodeId=cffc6951-7eef-4a58-82e1-69511458d650, topology=AffinityTopologyVersion
[topVer=3, minorTopVer=0]]
at
org.apache.ignite.internal.processors.job.GridJobProcessor$PartitionsReservation.reserve(GridJobProcessor.java:1596)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:510)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8545) If queryParallelism in nodes' caches configurations differ, query may hang, assert or return incomplete results
[ https://issues.apache.org/jira/browse/IGNITE-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Pudov updated IGNITE-8545: Fix Version/s: 2.7 > If queryParallelism in nodes' caches configurations differ, query may hang, > assert or return incomplete results > --- > > Key: IGNITE-8545 > URL: https://issues.apache.org/jira/browse/IGNITE-8545 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.6 >Reporter: Ilya Kasnacheev >Assignee: Maxim Pudov >Priority: Critical > Fix For: 2.7 > > Attachments: IgniteSqlSplitterQueryParallelismTest.java > > > I imagine it should not. See the attached file. > It happens both with client nodes and with server nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9485) Update documentation for ScanQuery with setLocal flag
[ https://issues.apache.org/jira/browse/IGNITE-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9485: - Ignite Flags: (was: Docs Required) > Update documentation for ScanQuery with setLocal flag > - > > Key: IGNITE-9485 > URL: https://issues.apache.org/jira/browse/IGNITE-9485 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9485) Update documentation for ScanQuery with setLocal flag
[ https://issues.apache.org/jira/browse/IGNITE-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9485: - Fix Version/s: 2.7 > Update documentation for ScanQuery with setLocal flag > - > > Key: IGNITE-9485 > URL: https://issues.apache.org/jira/browse/IGNITE-9485 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9485) Update documentation for ScanQuery with setLocal flag
Alexey Goncharuk created IGNITE-9485: Summary: Update documentation for ScanQuery with setLocal flag Key: IGNITE-9485 URL: https://issues.apache.org/jira/browse/IGNITE-9485 Project: Ignite Issue Type: Task Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9485) Update documentation for ScanQuery with setLocal flag
[ https://issues.apache.org/jira/browse/IGNITE-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9485: - Component/s: documentation > Update documentation for ScanQuery with setLocal flag > - > > Key: IGNITE-9485 > URL: https://issues.apache.org/jira/browse/IGNITE-9485 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8286) ScanQuery ignore setLocal with non local partition
[ https://issues.apache.org/jira/browse/IGNITE-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-8286: - Ignite Flags: Docs Required > ScanQuery ignore setLocal with non local partition > -- > > Key: IGNITE-8286 > URL: https://issues.apache.org/jira/browse/IGNITE-8286 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Alexander Belyak >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > 1) Create partitioned cache on 2+ nodes cluster > 2) Select some partition N, local node should not be OWNER of partition N > 3) execute: cache.query(new ScanQuery<>().setLocal(true).setPartition(N)) > Expected result: > empty result (probaply with logging smth like "Trying to execute local query > with non local partition N") or even throw exception > Actual result: > executing (with ScanQueryFallbackClosableIterator) query on remote node. > Problem is that we execute local query on remote node. > Same behaviour can be achieved if we get empty node list from > GridCacheQueryAdapter.node() by any reasons, for example - if we run "local" > query from non data node from given cache (see > GridDiscoveryNamager.cacheAffinityNode(ClusterNode node, String cacheName) in > GridcacheQueryAdapter.executeScanQuery() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9419) Avoid saving cache configuration synchronously during PME
[ https://issues.apache.org/jira/browse/IGNITE-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605879#comment-16605879 ] Ilya Lantukh commented on IGNITE-9419: -- [~Jokser], Thanks for contribution! In my opinion, adding publicly-mutable GridDhtPartitionsExchangeFuture.registerCachesFuture breaks encapsulation. Is it possible to re-design your solution to make this field modifiable only by ExchangeFuture itself? Also, please add tests for this functionality. > Avoid saving cache configuration synchronously during PME > - > > Key: IGNITE-9419 > URL: https://issues.apache.org/jira/browse/IGNITE-9419 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > Currently, we save cache configuration during PME at the activation phase > here > org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.CachesInfo#updateCachesInfo > . We should avoid this, as it performs operations to a disk. We should save > it asynchronously or lazy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9341) Notify metastorage listeners right before start of discovery processor
[
https://issues.apache.org/jira/browse/IGNITE-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605878#comment-16605878
]
Maxim Muzafarov commented on IGNITE-9341:
-
Folks,
Do we really need to keep {{readMetastore(false);}} call at that place?
Generally, I think this is not fair `read-only` metastorage.
* {{readMetastorage}} method still changes class {{this.metaStorage}} variable,
but, suppose, we can make it local variable there.
* Inside {{readMetastore}} method we are stopping temporarily created
{{PageMemoryEx}}. Suppose, metastorage instance, for this reason, can be used
only once by interface subscribers (they can't save it as the local variable
for the purposes).
Should we also change this? What do you think?
> Notify metastorage listeners right before start of discovery processor
> --
>
> Key: IGNITE-9341
> URL: https://issues.apache.org/jira/browse/IGNITE-9341
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Ivan Rakov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
>
> onReadyForRead() is called only for inheritors of
> MetastorageLifecycleListener interface which are started prior to
> GridCacheProcessor. Listeners are notified at the moment of
> ReadOnlyMetastorage initialization, which in turn occur during
> GridCacheDatabaseSharedManager start.
> We can split ReadOnlyMetastorage initialization and notification of listeners
> - this will allow all components to subscribe for read-only metastorage ready
> event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6346) Distributed set does not work in REPLICATED mode
[
https://issues.apache.org/jira/browse/IGNITE-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605875#comment-16605875
]
Alexey Goncharuk commented on IGNITE-6346:
--
Folks,
Is this ticket "In progress" then? Can you change the status?
> Distributed set does not work in REPLICATED mode
>
>
> Key: IGNITE-6346
> URL: https://issues.apache.org/jira/browse/IGNITE-6346
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.1
>Reporter: Valentin Kulichenko
>Assignee: vk
>Priority: Major
> Attachments: Reproducer.java
>
>
> When {{IgniteSet}} is created with {{REPLICATED}} cache mode, any attempt to
> read it fails with exception:
> {noformat}
> Exception in thread "main" class org.apache.ignite.IgniteException: Cluster
> group is empty.
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:48)
> at ReplicatedSet.main(ReplicatedSet.java:36)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterGroupEmptyCheckedException: Cluster
> group is empty.
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.execute0(GridCacheQueryAdapter.java:481)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter.execute(GridCacheQueryAdapter.java:442)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSetImpl.iterator0(GridCacheSetImpl.java:420)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSetImpl.iterator(GridCacheSetImpl.java:375)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheSetProxy.iterator(GridCacheSetProxy.java:342)
> ... 6 more
> {noformat}
> To reproduce run the following code:
> {code}
> Ignition.start(new IgniteConfiguration().setIgniteInstanceName("server-1"));
> Ignition.start(new IgniteConfiguration().setIgniteInstanceName("server-2"));
> Ignition.setClientMode(true);
> Ignite ignite = Ignition.start();
> IgniteSet set = ignite.set("my-set", new
> CollectionConfiguration().setCacheMode(CacheMode.REPLICATED));
> for (String s : set) {
> System.out.println(s);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605868#comment-16605868 ] ASF GitHub Bot commented on IGNITE-9298: GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/4697 IGNITE-9298 control.sh does not support SSL Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite IGNITE-9298 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4697.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 #4697 commit a6f25a94aa0885b6fe7f63f638a4f0e67b4a4327 Author: a-polyakov Date: 2018-09-06T13:35:44Z IGNITE-9298 control.sh does not support SSL Signed-off-by: a-polyakov > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Alexand Polyakov >Priority: Minor > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexand Polyakov reassigned IGNITE-9298: Assignee: Alexand Polyakov (was: Paul Anderson) > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Alexand Polyakov >Priority: Minor > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9341) Notify metastorage listeners right before start of discovery processor
[ https://issues.apache.org/jira/browse/IGNITE-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605839#comment-16605839 ] Vyacheslav Koptilin edited comment on IGNITE-9341 at 9/6/18 2:46 PM: - Hello [~DmitriyGovorukhin] Could you please take a look at this? was (Author: slava.koptilin): Hello [~DmitriyGovorukhin] [~ivan.glukos] Could you please take a look at this? > Notify metastorage listeners right before start of discovery processor > -- > > Key: IGNITE-9341 > URL: https://issues.apache.org/jira/browse/IGNITE-9341 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ivan Rakov >Assignee: Vyacheslav Koptilin >Priority: Major > Fix For: 2.8 > > > onReadyForRead() is called only for inheritors of > MetastorageLifecycleListener interface which are started prior to > GridCacheProcessor. Listeners are notified at the moment of > ReadOnlyMetastorage initialization, which in turn occur during > GridCacheDatabaseSharedManager start. > We can split ReadOnlyMetastorage initialization and notification of listeners > - this will allow all components to subscribe for read-only metastorage ready > event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9483) JDBC/ODBC thin drivers protocol versions compatibility
[
https://issues.apache.org/jira/browse/IGNITE-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605857#comment-16605857
]
ASF GitHub Bot commented on IGNITE-9483:
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4696
IGNITE-9483 JDBC/ODBC thin drivers protocol versions compatibility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9483
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4696.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 #4696
commit eb755a0f264b69b9524bfadcfbb693441ab749be
Author: Igor Seliverstov
Date: 2018-09-06T14:40:43Z
fix compatibility
> JDBC/ODBC thin drivers protocol versions compatibility
> --
>
> Key: IGNITE-9483
> URL: https://issues.apache.org/jira/browse/IGNITE-9483
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> Initially MVCC feature was aimed to 2.5 version but cannot be released
> earlier than in scope of 2.7
> There are several protocol versions checks that do their stuff for 2.5.0
> version instead of 2.7.0 (for example:
> {{JdbcConnectionContext#initializeFromHandshake}})
> Need to identify such places and fix them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9212) Uncomment 18 test classes in various modules' sutes (see inside)
[
https://issues.apache.org/jira/browse/IGNITE-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev reassigned IGNITE-9212:
---
Assignee: Ilya Kasnacheev
> Uncomment 18 test classes in various modules' sutes (see inside)
>
>
> Key: IGNITE-9212
> URL: https://issues.apache.org/jira/browse/IGNITE-9212
> Project: Ignite
> Issue Type: Sub-task
> Components: clients, hadoop, hibernate, jdbc, spring, zookeeper
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> As per the following test suites:
> {code}
> 4
> modules/clients/src/test/java/org/apache/ignite/internal/client/suite/IgniteClientTestSuite.java
> 1
> modules/clients/src/test/java/org/apache/ignite/jdbc/suite/IgniteJdbcDriverTestSuite.java
> 4
> modules/hadoop/src/test/java/org/apache/ignite/testsuites/IgniteHadoopTestSuite.java
> 1
> modules/hadoop/src/test/java/org/apache/ignite/testsuites/IgniteIgfsLinuxAndMacOSTestSuite.java
> 1
> modules/hibernate-4.2/src/test/java/org/apache/ignite/testsuites/IgniteHibernateTestSuite.java
> 1
> modules/hibernate-5.1/src/test/java/org/apache/ignite/testsuites/IgniteHibernate5TestSuite.java
> 2
> modules/spring/src/test/java/org/apache/ignite/testsuites/IgniteSpringTestSuite.java
> 3
> modules/urideploy/src/test/java/org/apache/ignite/testsuites/IgniteUriDeploymentTestSuite.java
> 1
> modules/zookeeper/src/test/java/org/apache/ignite/spi/discovery/zk/ZookeeperDiscoverySpiTestSuite1.java
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9484) MVCC TX: Handling transactions from multiple threads in jdbc requests handler.
Roman Kondakov created IGNITE-9484:
--
Summary: MVCC TX: Handling transactions from multiple threads in
jdbc requests handler.
Key: IGNITE-9484
URL: https://issues.apache.org/jira/browse/IGNITE-9484
Project: Ignite
Issue Type: Task
Components: jdbc, mvcc
Reporter: Roman Kondakov
JDBC requests may be handled by the different threads of thread pool even if
they belong to the same transaction. As a workaround a dedicated worker thread
is created for each session, which is not the best solution.
it is much better to have an abiltity to drive {{Near}} transactions from
different threads in the cases when transaction actions are applied
sequentially.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9483) JDBC/ODBC thin drivers protocol versions compatibility
[
https://issues.apache.org/jira/browse/IGNITE-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov reassigned IGNITE-9483:
Assignee: Igor Seliverstov
> JDBC/ODBC thin drivers protocol versions compatibility
> --
>
> Key: IGNITE-9483
> URL: https://issues.apache.org/jira/browse/IGNITE-9483
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> Initially MVCC feature was aimed to 2.5 version but cannot be released
> earlier than in scope of 2.7
> There are several protocol versions checks that do their stuff for 2.5.0
> version instead of 2.7.0 (for example:
> {{JdbcConnectionContext#initializeFromHandshake}})
> Need to identify such places and fix them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9483) JDBC/ODBC thin drivers protocol versions compatibility
Igor Seliverstov created IGNITE-9483:
Summary: JDBC/ODBC thin drivers protocol versions compatibility
Key: IGNITE-9483
URL: https://issues.apache.org/jira/browse/IGNITE-9483
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Igor Seliverstov
Fix For: 2.7
Initially MVCC feature was aimed to 2.5 version but cannot be released earlier
than in scope of 2.7
There are several protocol versions checks that do their stuff for 2.5.0
version instead of 2.7.0 (for example:
{{JdbcConnectionContext#initializeFromHandshake}})
Need to identify such places and fix them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9341) Notify metastorage listeners right before start of discovery processor
[ https://issues.apache.org/jira/browse/IGNITE-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605839#comment-16605839 ] Vyacheslav Koptilin commented on IGNITE-9341: - Hello [~DmitriyGovorukhin] [~ivan.glukos] Could you please take a look at this? > Notify metastorage listeners right before start of discovery processor > -- > > Key: IGNITE-9341 > URL: https://issues.apache.org/jira/browse/IGNITE-9341 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ivan Rakov >Assignee: Vyacheslav Koptilin >Priority: Major > Fix For: 2.8 > > > onReadyForRead() is called only for inheritors of > MetastorageLifecycleListener interface which are started prior to > GridCacheProcessor. Listeners are notified at the moment of > ReadOnlyMetastorage initialization, which in turn occur during > GridCacheDatabaseSharedManager start. > We can split ReadOnlyMetastorage initialization and notification of listeners > - this will allow all components to subscribe for read-only metastorage ready > event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9482) [ML] Refactor all trainers' settters to withFieldName format for meta-algorithms
Aleksey Zinoviev created IGNITE-9482: Summary: [ML] Refactor all trainers' settters to withFieldName format for meta-algorithms Key: IGNITE-9482 URL: https://issues.apache.org/jira/browse/IGNITE-9482 Project: Ignite Issue Type: Sub-task Components: ml Affects Versions: 2.7 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9479) Spontaneous rebalance may be triggered after a cache start
[ https://issues.apache.org/jira/browse/IGNITE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605805#comment-16605805 ] ASF GitHub Bot commented on IGNITE-9479: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4691 > Spontaneous rebalance may be triggered after a cache start > -- > > Key: IGNITE-9479 > URL: https://issues.apache.org/jira/browse/IGNITE-9479 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.7 > > > As an optimization, we do not run two-phase exchange latch release and do not > validate partition counters during cache start. > This can lead to a situation, when rebalance is mistakenly triggered under > load after a cache start. > We should treat cache start event the same way as other exchange events that > need counters sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9478) SQL: throw reducer retry error
[
https://issues.apache.org/jira/browse/IGNITE-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Grimstad reassigned IGNITE-9478:
---
Assignee: Sergey Grimstad (was: Vladimir Ozerov)
> SQL: throw reducer retry error
> --
>
> Key: IGNITE-9478
> URL: https://issues.apache.org/jira/browse/IGNITE-9478
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Sergey Grimstad
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
>
> Currently we cannot pass correct error message from reducer retry condition
> to user exception. Need to fix that. See
> \{{GridReduceQueryExecutor.logRetry}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9376) Create table with critical failures
[
https://issues.apache.org/jira/browse/IGNITE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605739#comment-16605739
]
ASF GitHub Bot commented on IGNITE-9376:
SomeFire closed pull request #4: IGNITE-9376 Create table with critical failures
URL: https://github.com/apache/ignite-teamcity-bot/pull/4
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ignite-tc-helper-web/src/main/webapp/css/style-1.5.css
b/ignite-tc-helper-web/src/main/webapp/css/style-1.5.css
index a3262b4..04411da 100644
--- a/ignite-tc-helper-web/src/main/webapp/css/style-1.5.css
+++ b/ignite-tc-helper-web/src/main/webapp/css/style-1.5.css
@@ -24,6 +24,14 @@ table, tr, td {
border-spacing: 0px;
}
+.table-title
+{
+ border: solid black;
+ border-width: 1px 0;
+ font-size: 20px;
+ padding: 5px;
+}
+
.logMsg {
font-family: Arial;
font-size: 12px;
diff --git a/ignite-tc-helper-web/src/main/webapp/js/testfails-2.0.js
b/ignite-tc-helper-web/src/main/webapp/js/testfails-2.0.js
index 83d0200..e363882 100644
--- a/ignite-tc-helper-web/src/main/webapp/js/testfails-2.0.js
+++ b/ignite-tc-helper-web/src/main/webapp/js/testfails-2.0.js
@@ -143,9 +143,11 @@ function showChainCurrentStatusData(server, settings) {
res += "";
+res += addBlockersData(server, settings);
for (var i = 0; i < server.suites.length; i++) {
var suite = server.suites[i];
+
res += showSuiteData(suite, settings);
}
@@ -155,6 +157,65 @@ function showChainCurrentStatusData(server, settings) {
return res;
}
+/**
+ * Creates table with possible blockers.
+ *
+ * @param server - see ChainAtServerCurrentStatus Java class.
+ * @param settings - see Settings JavaScript class.
+ * @returns {string} Table rows with possible blockers and table headers.
+ * Or empty string if no blockers found.
+ */
+function addBlockersData(server, settings) {
+if (findGetParameter("action") != "Latest")
+return "";
+
+var blockers = "";
+
+for (var i = 0; i < server.suites.length; i++) {
+var suite = server.suites[i];
+
+suite = suiteWithCriticalFailuresOnly(suite);
+
+if (suite != null)
+blockers += showSuiteData(suite, settings);
+}
+
+if (blockers != "") {
+blockers = "Possible Blockers" +
+blockers +
+"Other failures";
+}
+
+return blockers;
+}
+
+/**
+ * Copy suite and remove flaky tests from the copy.
+ *
+ * @param suite - see SuiteCurrentStatus Java class.
+ * @returns Suite without flaky tests. Or null - if suite have only flaky
tests.
+ */
+function suiteWithCriticalFailuresOnly(suite) {
+var suite0 = Object.assign({}, suite);
+var j = 0;
+
+suite0.testFailures = suite0.testFailures.slice();
+
+while (j < suite0.testFailures.length) {
+var testFailure = suite0.testFailures[j];
+
+if (isNewFailedTest(testFailure) || testFailure.name.includes("(last
started)"))
+j++;
+else
+suite0.testFailures.splice(j, 1);
+}
+
+if (suite0.testFailures.length > 0 || suite0.result != "")
+return suite0;
+
+return null;
+}
+
function triggerBuild(serverId, suiteId, branchName, top) {
var queueAtTop = isDefinedAndFilled(top) && top;
$.ajax({
@@ -235,7 +296,13 @@ function triggerBuilds(serverId, suiteIdList, branchName,
top) {
});
}
-//@param suite - see SuiteCurrentStatus
+/**
+ * Create html string with table rows, containing suite data.
+ *
+ * @param suite - see SuiteCurrentStatus Java class.
+ * @param settings - see Settings JavaScript class.
+ * @returns {string} Table rows with suite data.
+ */
function showSuiteData(suite, settings) {
var moreInfoTxt = "";
@@ -364,7 +431,9 @@ function showSuiteData(suite, settings) {
res += " ";
for (var i = 0; i < suite.testFailures.length; i++) {
-res += showTestFailData(suite.testFailures[i], true, settings);
+var testFailure = suite.testFailures[i];
+
+res += showTestFailData(testFailure, true, settings);
}
if (isDefinedAndFilled(suite.webUrlThreadDump)) {
@@ -381,6 +450,16 @@ function showSuiteData(suite, settings) {
return res;
}
+/**
+ * Check that given test is new.
+ *
+ * @param testFailure - see TestFailure Java class.
+ * @returns {boolean} True - if test is new. False - otherwise.
+ */
+function isNewFailedTest(testFailure) {
+return Number.parseFloat(testFailure.failureRate) < 4.0 ||
testFailure.flakyComments == null;
+}
+
function failureRateToColor(failureRate) {
var redSaturation = 255;
var greenSaturation = 0;
[jira] [Closed] (IGNITE-9459) MVCC Cache.size corner cases
[
https://issues.apache.org/jira/browse/IGNITE-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin closed IGNITE-9459.
--
> MVCC Cache.size corner cases
>
>
> Key: IGNITE-9459
> URL: https://issues.apache.org/jira/browse/IGNITE-9459
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Priority: Major
>
> During implementation of Cache.size for MVCC some corner cases were found.
> Attention must be put on:
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccInitialValue}}
> {{mvccRemoveAll}} could erroneously decrement size when deleting version
> which was deleted (having {{newVersion}} committed).
> {{mvccInitialValue}} could increment value over already existing value from
> history during rebalance.
> It worth carefully reproduce both cases before making any fixes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9459) MVCC Cache.size corner cases
[
https://issues.apache.org/jira/browse/IGNITE-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin resolved IGNITE-9459.
Resolution: Invalid
Will be fixed in tickets related to affected features.
> MVCC Cache.size corner cases
>
>
> Key: IGNITE-9459
> URL: https://issues.apache.org/jira/browse/IGNITE-9459
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Priority: Major
>
> During implementation of Cache.size for MVCC some corner cases were found.
> Attention must be put on:
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccInitialValue}}
> {{mvccRemoveAll}} could erroneously decrement size when deleting version
> which was deleted (having {{newVersion}} committed).
> {{mvccInitialValue}} could increment value over already existing value from
> history during rebalance.
> It worth carefully reproduce both cases before making any fixes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9376) Create table with critical failures
[ https://issues.apache.org/jira/browse/IGNITE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605732#comment-16605732 ] Dmitriy Govorukhin commented on IGNITE-9376: [~SomeFire] Thanks for the contribution. Merged to master. > Create table with critical failures > --- > > Key: IGNITE-9376 > URL: https://issues.apache.org/jira/browse/IGNITE-9376 > Project: Ignite > Issue Type: Sub-task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Major > > Create separate table for critical failures (suite timouts, suite non-zero > exit codes, etc) and new tests (failure rate 0.0%) on the PR analysis page of > TCH. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8582) MVCC TX: Cache store read-through support
[
https://issues.apache.org/jira/browse/IGNITE-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-8582:
---
Description:
Add support for read-through cache store for mvcc caches.
Attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method (called during load from store) when all existing mvcc row versions are
aborted or last committed one is _remove_ version.}}
was:Add support for read-through cache store for mvcc caches.
> MVCC TX: Cache store read-through support
> -
>
> Key: IGNITE-8582
> URL: https://issues.apache.org/jira/browse/IGNITE-8582
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Sergey Kalashnikov
>Priority: Major
>
> Add support for read-through cache store for mvcc caches.
> Attention should be put on Cache.size method behavior. Cache.size addressed
> in https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
> improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
> method (called during load from store) when all existing mvcc row versions
> are aborted or last committed one is _remove_ version.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-9441:
---
Labels: MakeTeamcityGreenAgain (was: )
> Failed to read WAL record at position
> -
>
> Key: IGNITE-9441
> URL: https://issues.apache.org/jira/browse/IGNITE-9441
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Anton Kalashnikov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> {noformat}
> [2018-08-31
> 10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
> Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
> msg=GridDhtPartitionDemandMessage [rebalanceId=1,
> parts=IgniteDhtDemandedPartitionsMap
> [historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
> 2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
> 14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590),
> 31=(1560,1590), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1,
> workerId=-1, topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0],
> partCnt=12, super=GridCacheGroupIdMessage [grpId=94416770]]]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 23721849 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
>
[jira] [Updated] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-9441:
---
Fix Version/s: 2.7
> Failed to read WAL record at position
> -
>
> Key: IGNITE-9441
> URL: https://issues.apache.org/jira/browse/IGNITE-9441
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Anton Kalashnikov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> {noformat}
> [2018-08-31
> 10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
> Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
> msg=GridDhtPartitionDemandMessage [rebalanceId=1,
> parts=IgniteDhtDemandedPartitionsMap
> [historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
> 2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
> 14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590),
> 31=(1560,1590), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1,
> workerId=-1, topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0],
> partCnt=12, super=GridCacheGroupIdMessage [grpId=94416770]]]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 23721849 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
>
[jira] [Updated] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-9441:
---
Component/s: persistence
> Failed to read WAL record at position
> -
>
> Key: IGNITE-9441
> URL: https://issues.apache.org/jira/browse/IGNITE-9441
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Anton Kalashnikov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> {noformat}
> [2018-08-31
> 10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
> Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
> msg=GridDhtPartitionDemandMessage [rebalanceId=1,
> parts=IgniteDhtDemandedPartitionsMap
> [historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
> 2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
> 14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590),
> 31=(1560,1590), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1,
> workerId=-1, topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0],
> partCnt=12, super=GridCacheGroupIdMessage [grpId=94416770]]]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 23721849 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
>
[jira] [Updated] (IGNITE-9314) MVCC TX: Datastreamer operations
[
https://issues.apache.org/jira/browse/IGNITE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-9314:
---
Description:
Need to change DataStreamer semantics (make it transactional)
Currently clients can see DataStreamer partial writes and two subsequent
selects, which are run in scope of one transaction at load time, may return
different results.
Related thread:
[http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
Also there is a problem when {{DataStreamer}} with {{allowOverwrite == false}}
does not insert value when versions for entry exist but they all are aborted.
Proper transactional semantics should developed for such case. After that
attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method (called during streamer processing) when all existing mvcc row versions
are aborted or last committed one is _remove_ version.}}
was:
Need to change DataStreamer semantics (make it transactional)
Currently clients can see DataStreamer partial writes and two subsequent
selects, which are run in scope of one transaction at load time, may return
different results.
Related thread:
[http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
Attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method when all existing mvcc row versions are aborted or last committed one
is _remove_ version.}}
> MVCC TX: Datastreamer operations
>
>
> Key: IGNITE-9314
> URL: https://issues.apache.org/jira/browse/IGNITE-9314
> Project: Ignite
> Issue Type: Task
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> Need to change DataStreamer semantics (make it transactional)
> Currently clients can see DataStreamer partial writes and two subsequent
> selects, which are run in scope of one transaction at load time, may return
> different results.
> Related thread:
>
> [http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
> Also there is a problem when {{DataStreamer}} with {{allowOverwrite ==
> false}} does not insert value when versions for entry exist but they all are
> aborted. Proper transactional semantics should developed for such case. After
> that attention should be put on Cache.size method behavior. Cache.size
> addressed in https://issues.apache.org/jira/browse/IGNITE-8149 could be
> decremented improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
> method (called during streamer processing) when all existing mvcc row
> versions are aborted or last committed one is _remove_ version.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin reassigned IGNITE-9441:
--
Assignee: Ivan Bessonov (was: Dmitriy Govorukhin)
> Failed to read WAL record at position
> -
>
> Key: IGNITE-9441
> URL: https://issues.apache.org/jira/browse/IGNITE-9441
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Ivan Bessonov
>Priority: Major
>
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> {noformat}
> [2018-08-31
> 10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
> Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
> msg=GridDhtPartitionDemandMessage [rebalanceId=1,
> parts=IgniteDhtDemandedPartitionsMap
> [historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
> 2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
> 14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590),
> 31=(1560,1590), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1,
> workerId=-1, topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0],
> partCnt=12, super=GridCacheGroupIdMessage [grpId=94416770]]]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 23721849 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
[jira] [Assigned] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin reassigned IGNITE-9441:
--
Assignee: Dmitriy Govorukhin (was: Anton Kalashnikov)
> Failed to read WAL record at position
> -
>
> Key: IGNITE-9441
> URL: https://issues.apache.org/jira/browse/IGNITE-9441
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Dmitriy Govorukhin
>Priority: Major
>
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> {noformat}
> [2018-08-31
> 10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
> Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
> msg=GridDhtPartitionDemandMessage [rebalanceId=1,
> parts=IgniteDhtDemandedPartitionsMap
> [historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
> 2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
> 14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590),
> 31=(1560,1590), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1,
> workerId=-1, topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0],
> partCnt=12, super=GridCacheGroupIdMessage [grpId=94416770]]]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 23721849 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
[jira] [Commented] (IGNITE-9480) SQL: Introduce H2 LocalResult factory
[ https://issues.apache.org/jira/browse/IGNITE-9480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605701#comment-16605701 ] Taras Ledkov commented on IGNITE-9480: -- [~vozerov], please take a look at the suggested [H2 patch|https://github.com/h2database/h2database/pull/1424] . > SQL: Introduce H2 LocalResult factory > - > > Key: IGNITE-9480 > URL: https://issues.apache.org/jira/browse/IGNITE-9480 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.6 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.7 > > > H2 collects query result at the instance of `LocalResult` for queries results > that not be gathered lazy. This causes an OOME error on large result sets. > We have to introduce way to use our own implementation of the query result's > container. > Suggestion fix: > - H2 simple refactoring: make `LocalResult` interface and H2 default > implementation `LocalResultImpl` > - Add H2 configurable `LocalResultFactory` to setup custom implementation of > the `LocalResult. > - Create Ignite implementation of `LocalResultFactory` & `LocalResult` to > track allocated memory, swap results to external storage etc. > H2 issue: > [#1405|https://github.com/h2database/h2database/issues/1405#issuecomment-417631253] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9314) MVCC TX: Datastreamer operations
[
https://issues.apache.org/jira/browse/IGNITE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-9314:
---
Description:
Need to change DataStreamer semantics (make it transactional)
Currently clients can see DataStreamer partial writes and two subsequent
selects, which are run in scope of one transaction at load time, may return
different results.
Related thread:
[http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
Attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method when all existing mvcc row versions are aborted or last committed one
is _remove_ version.}}
was:
Need to change DataStreamer semantics (make it transactional)
Currently clients can see DataStreamer partial writes and two subsequent
selects, which are run in scope of one transaction at load time, may return
different results.
Related thread:
http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html
> MVCC TX: Datastreamer operations
>
>
> Key: IGNITE-9314
> URL: https://issues.apache.org/jira/browse/IGNITE-9314
> Project: Ignite
> Issue Type: Task
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> Need to change DataStreamer semantics (make it transactional)
> Currently clients can see DataStreamer partial writes and two subsequent
> selects, which are run in scope of one transaction at load time, may return
> different results.
> Related thread:
>
> [http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
> Attention should be put on Cache.size method behavior. Cache.size addressed
> in https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
> improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
> method when all existing mvcc row versions are aborted or last committed one
> is _remove_ version.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8149) MVCC TX: Size method should use tx snapshot
[
https://issues.apache.org/jira/browse/IGNITE-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16601999#comment-16601999
]
Ivan Pavlukhin edited comment on IGNITE-8149 at 9/6/18 12:09 PM:
-
Additionally some problems were found which needs to be fixed. Attention must
be put on:
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccInitialValue}}
But they are inapplicable in currently supported API. _clear_, _load from
store_ and _data streamer_ are affected. Cache.size behavior must be taken into
account while working on those features.
was (Author: pavlukhin):
Additionally some problems were found which needs to be fixed. Attention must
be put on:
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccInitialValue}}
Will be addressed in separate ticket IGNITE-9459
> MVCC TX: Size method should use tx snapshot
> ---
>
> Key: IGNITE-8149
> URL: https://issues.apache.org/jira/browse/IGNITE-8149
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
>Reporter: Igor Seliverstov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Currently cache.size() returns number of entries in cache trees while there
> can be several versions of one key-value pairs.
> We should use tx snapshot and count all passed mvcc filter entries instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7952) MVCC TX: cache clear routines for key-value API
[
https://issues.apache.org/jira/browse/IGNITE-7952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-7952:
---
Description:
We need to implement MVCC-compatible cache clear operations for Key-Value API.
Attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be calculated
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method when all existing mvcc row versions are aborted or last committed one
is _remove_ version.}}
was:
We need to implement MVCC-compatible cache clear operations for Key-Value API.
Attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be calculated
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method.}}
> MVCC TX: cache clear routines for key-value API
> ---
>
> Key: IGNITE-7952
> URL: https://issues.apache.org/jira/browse/IGNITE-7952
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
>Reporter: Alexander Paschenko
>Priority: Major
>
> We need to implement MVCC-compatible cache clear operations for Key-Value API.
> Attention should be put on Cache.size method behavior. Cache.size addressed
> in https://issues.apache.org/jira/browse/IGNITE-8149 could be calculated
> improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
> method when all existing mvcc row versions are aborted or last committed one
> is _remove_ version.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7952) MVCC TX: cache clear routines for key-value API
[
https://issues.apache.org/jira/browse/IGNITE-7952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-7952:
---
Description:
We need to implement MVCC-compatible cache clear operations for Key-Value API.
Attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be calculated
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
method.}}
was:We need to implement MVCC-compatible cache clear operations for Key-Value
API.
> MVCC TX: cache clear routines for key-value API
> ---
>
> Key: IGNITE-7952
> URL: https://issues.apache.org/jira/browse/IGNITE-7952
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
>Reporter: Alexander Paschenko
>Priority: Major
>
> We need to implement MVCC-compatible cache clear operations for Key-Value API.
> Attention should be put on Cache.size method behavior. Cache.size addressed
> in https://issues.apache.org/jira/browse/IGNITE-8149 could be calculated
> improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll
> method.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605690#comment-16605690 ] Sergey Grimstad commented on IGNITE-8552: - tests: [https://ci.ignite.apache.org/viewLog.html?buildId=1805803;] failed tests are flaky and non-reproducible locally > Unable to use date as primary key > - > > Key: IGNITE-8552 > URL: https://issues.apache.org/jira/browse/IGNITE-8552 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Assignee: Sergey Grimstad >Priority: Blocker > Fix For: 2.7 > > Attachments: IGNITE-8552_implemented.patch > > > It' is unable to create cache via ddl: > create table tab(id date primary key, date_field date); > Result: > ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to > rollback cache start routine. [cacheName=SQL_PUBLIC_T3] > class org.apache.ignite.IgniteCheckedException: Failed to find value class in > the node classpath (use default marshaller to enable binary objects) : > SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 > at > org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9161) CPP: Get rid of additional copy on Get
[
https://issues.apache.org/jira/browse/IGNITE-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605685#comment-16605685
]
Igor Sapego commented on IGNITE-9161:
-
[~tledkov-gridgain],
1. Unfortunately, there are no benchmarks for C++ but profiler on Windows and
Linux shows that this fix helps to get rid of additional object copy operation
and thus shows performance improvement on return of non-primitive objects (the
bigger an object the more visible the improvement).
2. [~vozerov], can you take a look?
> CPP: Get rid of additional copy on Get
> --
>
> Key: IGNITE-9161
> URL: https://issues.apache.org/jira/browse/IGNITE-9161
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.7
>
>
> Currently, helper classes from {{operations.h}} header file, e.g.
> {{Out1Operation}} contain additional value, that can't be optimized-out by
> the compiler on return, even though the operation itself is a temporary
> object.
> As a solution, such classes should accept and operate on a reference to a
> temporary object, so that [copy
> elision|https://en.wikipedia.org/wiki/Copy_elision] can be used by a compiler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8640) If first createCache fail - Ignite is freezing on next createCache
[
https://issues.apache.org/jira/browse/IGNITE-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605663#comment-16605663
]
Vyacheslav Koptilin commented on IGNITE-8640:
-
Hello [~SomeFire] [~garus.d.g]
Please take a look at the following tests:
* SqlIllegalSchemaSelfTest.testBadCacheNameDynamic
* SqlIllegalSchemaSelfTest.testBadSchemaLowerDynamic
* SqlIllegalSchemaSelfTest.testBadSchemaQuotedDynamic
* SqlIllegalSchemaSelfTest.testBadSchemaUpperDynamic
At least, checking the expected exception message should be improved/fixed.
> If first createCache fail - Ignite is freezing on next createCache
> --
>
> Key: IGNITE-8640
> URL: https://issues.apache.org/jira/browse/IGNITE-8640
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolay Izhikov
>Assignee: Denis Garus
>Priority: Critical
> Fix For: 2.7
>
>
> If first {{createCache}} operation fails on some condition inside
> {{GridCacheProcessor#validate}} then second {{createCache}} will freeze
> forever.
> Reproducer:
> {code:java}
> package org.apache.ignite.internal.processors.cache;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class CreateCacheFreezeTest extends GridCommonAbstractTest {
> public void testCreateEncryptedNotPersistedCacheFail() throws Exception {
> IgniteEx ignite = startGrid(0);
>
> GridTestUtils.assertThrowsWithCause(() -> {
> CacheConfiguration cc = new
> CacheConfiguration<>("failed");
> cc.setEvictionPolicy(new FifoEvictionPolicy());
> cc.setOnheapCacheEnabled(false);
> ignite.createCache(cc);
> return 0;
> }, IgniteCheckedException.class);
> IgniteCache cache = ignite.createCache(new
> CacheConfiguration<>("default"));
> assertNotNull(cache);
> }
> }
> {code}
> Log message:
> {noformat}
> [2018-05-29
> 16:38:11,958][ERROR][exchange-worker-#38%cache.CreateCacheFreezeTest0%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=DynamicCacheChangeBatch
> [id=67cce1ca361-993dd9c2-f4fe-443b-af43-27e06424e1b0,
> reqs=[DynamicCacheChangeRequest [cacheName=failed, hasCfg=true,
> nodeId=a525b74c-aec5-4c62-855a-ff96ef30, clientStartOnly=false,
> stop=false, destroy=false, disabledAfterStartfalse]],
> exchangeActions=ExchangeActions [startCaches=[failed], stopCaches=null,
> startGrps=[failed], stopGrps=[], resetParts=null, stateChangeRequest=null],
> startCaches=false], affTopVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=a525b74c-aec5-4c62-855a-ff96ef30, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1527601090538, loc=true, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=1, nodeId8=a525b74c, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1527601091938]], nodeId=a525b74c,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: stopping=false, groupName=null, caches=[]
> at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:375)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:197)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.getOrCreatePartition(GridDhtPartitionTopologyImpl.java:828)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.initPartitions(GridDhtPartitionTopologyImpl.java:369)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.beforeExchange(GridDhtPartitionTopologyImpl.java:544)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1190)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:722)
> at
>
[jira] [Created] (IGNITE-9481) Force checkpoint after CacheStore.loadCache is complete
Ilya Kasnacheev created IGNITE-9481: --- Summary: Force checkpoint after CacheStore.loadCache is complete Key: IGNITE-9481 URL: https://issues.apache.org/jira/browse/IGNITE-9481 Project: Ignite Issue Type: Improvement Components: cache, persistence Reporter: Ilya Kasnacheev Currently, entries loaded by loadCache() do not appear in WAL. They will be lost if node is stopped after loadCache() is complete but before checkpoint is finished. Ideally, after loadCache this cache should be checkpointed so that RAM and WAL are in sync once more. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods
[
https://issues.apache.org/jira/browse/IGNITE-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605634#comment-16605634
]
Nikolay Izhikov commented on IGNITE-9160:
-
Let's add tests for each equals method that was edited.
We need tests:
1. That fails without a patch.
2. That demonstrates that equals still works properly.
> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: newbie
> Fix For: 2.7
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> Or NPE
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
> The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
> return false;{code}
> + List of classes with similar problems: +
> * *GridTopic$T1-T8* - NPE
> * *GridCachePreloadLifecycleAbstractTest -* NPE
> * *GridDhtPartitionFullMap -* NPE and CCE
> * *GridDhtPartitionMap -* NPE and CCE
> * *OptimizedMarshallerSelfTest -* NPE and CCE
> * *GatewayProtectedCacheProxy -* NPE and CCE
> * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
> * *GridCacheDistributedQueryManager -* NPE and CCE
> * *GridServiceMethodReflectKey -* NPE and CCE
> * *GridListSetSelfTest -* NPE and CCE
> * *GridTestKey -* NPE and CCE
> * *GridCacheMvccCandidate -* CCE
> * *GridDhtPartitionExchangeId -* CCE
> * *GridTuple6 -* CCE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9452) Correct GridInternalTaskUnusedWalSegmentsTest after merging IGNITE-6552
[ https://issues.apache.org/jira/browse/IGNITE-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605614#comment-16605614 ] ASF GitHub Bot commented on IGNITE-9452: GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/4693 IGNITE-9452 Correct test after merging IGNITE-6552. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9452 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4693.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 #4693 commit a80ad4379028e33b1383ec5a51806a338a2fe948 Author: Ivan Daschinskiy Date: 2018-09-06T10:37:09Z IGNITE-9452 Correct test after merging IGNITE-6552. > Correct GridInternalTaskUnusedWalSegmentsTest after merging IGNITE-6552 > --- > > Key: IGNITE-9452 > URL: https://issues.apache.org/jira/browse/IGNITE-9452 > Project: Ignite > Issue Type: Test >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Minor > Fix For: 2.8 > > > After merging IGNITE-6552 need to correct > GridInternalTaskUnusedWalSegmentsTest a little bit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9093) IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on master
[ https://issues.apache.org/jira/browse/IGNITE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605585#comment-16605585 ] ASF GitHub Bot commented on IGNITE-9093: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4545 > IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on > master > > > Key: IGNITE-9093 > URL: https://issues.apache.org/jira/browse/IGNITE-9093 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Such as in > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1=pull%2F4420%2Fhead=buildTypeStatusDiv > Used to work every time in 2.6 release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9333) Adding page with simple statistic for last 50 runs.
[ https://issues.apache.org/jira/browse/IGNITE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605600#comment-16605600 ] Anton Kalashnikov commented on IGNITE-9333: --- Looks good for me. [~DmitriyGovorukhin] can you help with merge, please. > Adding page with simple statistic for last 50 runs. > --- > > Key: IGNITE-9333 > URL: https://issues.apache.org/jira/browse/IGNITE-9333 > Project: Ignite > Issue Type: Sub-task >Reporter: Eduard Shangareev >Assignee: Nikolai Kulagin >Priority: Major > > Ok, I am proposing to add a new page which would be named "Statistic". > It should show last 50 "Run All" for master, the columns: > ||Id||Total tests||Failed tests||Ignored tests|| Muted tests||Total issues > (count and the list of TC configurations with links) || Total run time || > Also, we need to calculate the statistic. > Totals (all unique tests with issues), average issues/fails per run, median, > max, min. > Total issues = Exit codes + JVM Crashes + OOMs + other issues which caused TC > configuration fail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8915) NPE during executing local SqlQuery from client node
[
https://issues.apache.org/jira/browse/IGNITE-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605594#comment-16605594
]
ASF GitHub Bot commented on IGNITE-8915:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4414
> NPE during executing local SqlQuery from client node
>
>
> Key: IGNITE-8915
> URL: https://issues.apache.org/jira/browse/IGNITE-8915
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Vyacheslav Daradur
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: IgniteCacheReplicatedClientLocalQuerySelfTest.java
>
>
> NPE when trying to execute {{SqlQuery}} with {{setLocal(true)}} from client
> node.
> [Reproducer|^IgniteCacheReplicatedClientLocalQuerySelfTest.java].
> UPD:
> Right behavior:
> Local query should be forbidden and a sensible exception should be thrown if
> it is executed on client node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9480) SQL: Introduce H2 LocalResult factory
Taras Ledkov created IGNITE-9480: Summary: SQL: Introduce H2 LocalResult factory Key: IGNITE-9480 URL: https://issues.apache.org/jira/browse/IGNITE-9480 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.6 Reporter: Taras Ledkov Assignee: Taras Ledkov Fix For: 2.7 H2 collects query result at the instance of `LocalResult` for queries results that not be gathered lazy. This causes an OOME error on large result sets. We have to introduce way to use our own implementation of the query result's container. Suggestion fix: - H2 simple refactoring: make `LocalResult` interface and H2 default implementation `LocalResultImpl` - Add H2 configurable `LocalResultFactory` to setup custom implementation of the `LocalResult. - Create Ignite implementation of `LocalResultFactory` & `LocalResult` to track allocated memory, swap results to external storage etc. H2 issue: [#1405|https://github.com/h2database/h2database/issues/1405#issuecomment-417631253] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9093) IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on master
[ https://issues.apache.org/jira/browse/IGNITE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9093: - Fix Version/s: 2.7 > IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on > master > > > Key: IGNITE-9093 > URL: https://issues.apache.org/jira/browse/IGNITE-9093 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Such as in > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1=pull%2F4420%2Fhead=buildTypeStatusDiv > Used to work every time in 2.6 release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9093) IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on master
[ https://issues.apache.org/jira/browse/IGNITE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9093: - Ignite Flags: (was: Docs Required) > IgniteDbPutGetWithCacheStoreTest.testReadThrough fails every time when run on > master > > > Key: IGNITE-9093 > URL: https://issues.apache.org/jira/browse/IGNITE-9093 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Such as in > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1=pull%2F4420%2Fhead=buildTypeStatusDiv > Used to work every time in 2.6 release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605571#comment-16605571
]
ASF GitHub Bot commented on IGNITE-9422:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4681
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.7
>
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9422:
-
Fix Version/s: (was: 2.8)
2.7
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.7
>
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605566#comment-16605566 ] ASF GitHub Bot commented on IGNITE-8552: GitHub user SGrimstad opened a pull request: https://github.com/apache/ignite/pull/4692 IGNITE-8552 implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-8552 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4692.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 #4692 commit 15261b5f56a9e3a2ddd4dcf6c0573cdea2c66541 Author: SGrimstad Date: 2018-09-06T09:41:56Z IGNITE-8552 implemented > Unable to use date as primary key > - > > Key: IGNITE-8552 > URL: https://issues.apache.org/jira/browse/IGNITE-8552 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Assignee: Sergey Grimstad >Priority: Blocker > Fix For: 2.7 > > Attachments: IGNITE-8552_implemented.patch > > > It' is unable to create cache via ddl: > create table tab(id date primary key, date_field date); > Result: > ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to > rollback cache start routine. [cacheName=SQL_PUBLIC_T3] > class org.apache.ignite.IgniteCheckedException: Failed to find value class in > the node classpath (use default marshaller to enable binary objects) : > SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 > at > org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8936) Remove AffinityAssignment#clientEventChange as not used
[ https://issues.apache.org/jira/browse/IGNITE-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605567#comment-16605567 ] ASF GitHub Bot commented on IGNITE-8936: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4448 > Remove AffinityAssignment#clientEventChange as not used > --- > > Key: IGNITE-8936 > URL: https://issues.apache.org/jira/browse/IGNITE-8936 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Minor > Labels: newbie > Attachments: ClientEventChange (1).png > > > We should try to keep Ignite project code as simple as possible. > Motivation: > http://apache-ignite-developers.2346864.n4.nabble.com/Cases-of-using-AffinityAssignment-clientEventChange-method-td32068.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9161) CPP: Get rid of additional copy on Get
[
https://issues.apache.org/jira/browse/IGNITE-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605553#comment-16605553
]
Taras Ledkov commented on IGNITE-9161:
--
[~isapego], the review summary:
| Code style | OK |
| API compatibility | OK |
| Product behavior | defaults not changed |
| Documentation | not required |
| Binary compatibility | OK |
| Tests | OK |
| Comments | # The patch fixes performance issue but I've not seen any
benchmarks' results or performance analyze.
# My experience with cpp is not relevant, contact another engineer for in-depth
technical review. |
> CPP: Get rid of additional copy on Get
> --
>
> Key: IGNITE-9161
> URL: https://issues.apache.org/jira/browse/IGNITE-9161
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.7
>
>
> Currently, helper classes from {{operations.h}} header file, e.g.
> {{Out1Operation}} contain additional value, that can't be optimized-out by
> the compiler on return, even though the operation itself is a temporary
> object.
> As a solution, such classes should accept and operate on a reference to a
> temporary object, so that [copy
> elision|https://en.wikipedia.org/wiki/Copy_elision] can be used by a compiler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grimstad reassigned IGNITE-8552: --- Assignee: Sergey Grimstad > Unable to use date as primary key > - > > Key: IGNITE-8552 > URL: https://issues.apache.org/jira/browse/IGNITE-8552 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Assignee: Sergey Grimstad >Priority: Blocker > Fix For: 2.7 > > > It' is unable to create cache via ddl: > create table tab(id date primary key, date_field date); > Result: > ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to > rollback cache start routine. [cacheName=SQL_PUBLIC_T3] > class org.apache.ignite.IgniteCheckedException: Failed to find value class in > the node classpath (use default marshaller to enable binary objects) : > SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 > at > org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8915) NPE during executing local SqlQuery from client node
[
https://issues.apache.org/jira/browse/IGNITE-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605545#comment-16605545
]
Vladimir Ozerov commented on IGNITE-8915:
-
[~NIzhikov],
Looks good to me.
> NPE during executing local SqlQuery from client node
>
>
> Key: IGNITE-8915
> URL: https://issues.apache.org/jira/browse/IGNITE-8915
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Vyacheslav Daradur
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: IgniteCacheReplicatedClientLocalQuerySelfTest.java
>
>
> NPE when trying to execute {{SqlQuery}} with {{setLocal(true)}} from client
> node.
> [Reproducer|^IgniteCacheReplicatedClientLocalQuerySelfTest.java].
> UPD:
> Right behavior:
> Local query should be forbidden and a sensible exception should be thrown if
> it is executed on client node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9479) Spontaneous rebalance may be triggered after a cache start
[ https://issues.apache.org/jira/browse/IGNITE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605531#comment-16605531 ] ASF GitHub Bot commented on IGNITE-9479: GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4691 IGNITE-9479 Fixed spontaneous rebalance during cache start …ed logging level You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9479 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4691.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 #4691 commit 554e787133991c8f4993b1df5cae9d9e870c4957 Author: Alexey Goncharuk Date: 2018-09-06T09:29:12Z IGNITE-9479 Fixed spontaneous rebalance during cache start and improved logging level > Spontaneous rebalance may be triggered after a cache start > -- > > Key: IGNITE-9479 > URL: https://issues.apache.org/jira/browse/IGNITE-9479 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.7 > > > As an optimization, we do not run two-phase exchange latch release and do not > validate partition counters during cache start. > This can lead to a situation, when rebalance is mistakenly triggered under > load after a cache start. > We should treat cache start event the same way as other exchange events that > need counters sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7113) "Key is missing from query" when creating table with key_type=java.lang.String
[
https://issues.apache.org/jira/browse/IGNITE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605532#comment-16605532
]
Vladimir Ozerov commented on IGNITE-7113:
-
Remerged with master, new test run:
https://ci.ignite.apache.org/viewLog.html?buildId=1805647=buildResultsDiv=IgniteTests24Java8_RunAllSql
> "Key is missing from query" when creating table with key_type=java.lang.String
> --
>
> Key: IGNITE-7113
> URL: https://issues.apache.org/jira/browse/IGNITE-7113
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Priority: Major
> Labels: sql-stability
> Attachments: IgniteStringKeyTest.java
>
>
> When creating a table of
> {code}
> CREATE TABLE IF NOT EXISTS TableWithStringKey (
> ID VARCHAR PRIMARY KEY,
> DataNodeId VARCHAR
> ) WITH "backups=1, cache_name=TableWithStringKey, atomicity=transactional,
> key_type=java.lang.String, value_type=TableWithStringKey"
> {code}
> and attempting an insert later
> {code}
> INSERT INTO TableWithStringKey (ID, DataNodeId) VALUES ('ref2', 'src2')
> {code}
> There's suddently an exception
> {code}
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> execute DML statement [stmt=INSERT INTO TableWithStringKey (ID, DataNodeId)
> VALUES ('ref2', 'src2'), params=null]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:597)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:560)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:382)
> at
> com.gridgain.reproducer.IgniteStringKeyTest.insertTest(IgniteStringKeyTest.java:34)
> ... 24 more
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> execute DML statement [stmt=INSERT INTO TableWithStringKey (ID, DataNodeId)
> VALUES ('ref2', 'src2'), params=null]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1459)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1909)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1907)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2445)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> ... 27 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Key is missing
> from query
> at
> org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.createSupplier(UpdatePlanBuilder.java:369)
> at
> org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.planForInsert(UpdatePlanBuilder.java:211)
> at
> org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.planForStatement(UpdatePlanBuilder.java:98)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.getPlanForStatement(DmlStatementsProcessor.java:473)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:170)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:229)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1453)
> ... 33 more
> {code}
> that goes away if you remove "key_type=java.lang.String"
> I'm attaching a reproducer class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9479) Spontaneous rebalance may be triggered after a cache start
[ https://issues.apache.org/jira/browse/IGNITE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605524#comment-16605524 ] Alexey Goncharuk commented on IGNITE-9479: -- Also found out that we log each key during rebalancing at DEBUG level. This should be changed to TRACE. > Spontaneous rebalance may be triggered after a cache start > -- > > Key: IGNITE-9479 > URL: https://issues.apache.org/jira/browse/IGNITE-9479 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.7 > > > As an optimization, we do not run two-phase exchange latch release and do not > validate partition counters during cache start. > This can lead to a situation, when rebalance is mistakenly triggered under > load after a cache start. > We should treat cache start event the same way as other exchange events that > need counters sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9479) Spontaneous rebalance may be triggered after a cache start
[ https://issues.apache.org/jira/browse/IGNITE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9479: - Ignite Flags: (was: Docs Required) > Spontaneous rebalance may be triggered after a cache start > -- > > Key: IGNITE-9479 > URL: https://issues.apache.org/jira/browse/IGNITE-9479 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.7 > > > As an optimization, we do not run two-phase exchange latch release and do not > validate partition counters during cache start. > This can lead to a situation, when rebalance is mistakenly triggered under > load after a cache start. > We should treat cache start event the same way as other exchange events that > need counters sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9479) Spontaneous rebalance may be triggered after a cache start
Alexey Goncharuk created IGNITE-9479: Summary: Spontaneous rebalance may be triggered after a cache start Key: IGNITE-9479 URL: https://issues.apache.org/jira/browse/IGNITE-9479 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Alexey Goncharuk Assignee: Alexey Goncharuk Fix For: 2.7 As an optimization, we do not run two-phase exchange latch release and do not validate partition counters during cache start. This can lead to a situation, when rebalance is mistakenly triggered under load after a cache start. We should treat cache start event the same way as other exchange events that need counters sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8927) Hangs when executing an SQL query when there are LOST partitions
[ https://issues.apache.org/jira/browse/IGNITE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605514#comment-16605514 ] Vladimir Ozerov commented on IGNITE-8927: - Added reservation for LOST partitions. New run: https://ci.ignite.apache.org/viewQueued.html?itemId=1805634 > Hangs when executing an SQL query when there are LOST partitions > > > Key: IGNITE-8927 > URL: https://issues.apache.org/jira/browse/IGNITE-8927 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Dmitriy Gladkikh >Assignee: Vladimir Ozerov >Priority: Major > Labels: sql-stability > Fix For: 2.7 > > > If there are partitions in the LOST state, SQL query hang. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9161) CPP: Get rid of additional copy on Get
[
https://issues.apache.org/jira/browse/IGNITE-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605507#comment-16605507
]
Igor Sapego commented on IGNITE-9161:
-
TeamCity link:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4476%2Fhead
> CPP: Get rid of additional copy on Get
> --
>
> Key: IGNITE-9161
> URL: https://issues.apache.org/jira/browse/IGNITE-9161
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.7
>
>
> Currently, helper classes from {{operations.h}} header file, e.g.
> {{Out1Operation}} contain additional value, that can't be optimized-out by
> the compiler on return, even though the operation itself is a temporary
> object.
> As a solution, such classes should accept and operate on a reference to a
> temporary object, so that [copy
> elision|https://en.wikipedia.org/wiki/Copy_elision] can be used by a compiler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9412) [ML] GDB convergence by error support.
[ https://issues.apache.org/jira/browse/IGNITE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605504#comment-16605504 ] ASF GitHub Bot commented on IGNITE-9412: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4670 > [ML] GDB convergence by error support. > -- > > Key: IGNITE-9412 > URL: https://issues.apache.org/jira/browse/IGNITE-9412 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > Fix For: 2.7 > > > We need to support early training interruption when GDB has small error rate > on learning sample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9333) Adding page with simple statistic for last 50 runs.
[
https://issues.apache.org/jira/browse/IGNITE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605502#comment-16605502
]
ASF GitHub Bot commented on IGNITE-9333:
zzzadruga commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r215550903
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/issues/IssueRef.java
##
@@ -0,0 +1,38 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.result.issues;
+
+import javax.xml.bind.annotation.XmlAttribute;
+
+/**
+ * Issue short version from list of build's related issues.
+ *
+ * See example of XML, e.g. here
+ * https://ci.ignite.apache.org/app/rest/latest/builds/id:1694977/relatedIssues
+ */
+public class IssueRef {
Review comment:
In the code of a field of this class named as "problemRef". Therefore, I
renamed the class to "ProblemRef"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Adding page with simple statistic for last 50 runs.
> ---
>
> Key: IGNITE-9333
> URL: https://issues.apache.org/jira/browse/IGNITE-9333
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Eduard Shangareev
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Ok, I am proposing to add a new page which would be named "Statistic".
> It should show last 50 "Run All" for master, the columns:
> ||Id||Total tests||Failed tests||Ignored tests|| Muted tests||Total issues
> (count and the list of TC configurations with links) || Total run time ||
> Also, we need to calculate the statistic.
> Totals (all unique tests with issues), average issues/fails per run, median,
> max, min.
> Total issues = Exit codes + JVM Crashes + OOMs + other issues which caused TC
> configuration fail
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9388) mesos IgniteProvider tries to access obolete ignite.run or download from slow archive
[ https://issues.apache.org/jira/browse/IGNITE-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605495#comment-16605495 ] Roman Shtykh commented on IGNITE-9388: -- [~ilyak] Thanks again. Please see my comments. > mesos IgniteProvider tries to access obolete ignite.run or download from slow > archive > - > > Key: IGNITE-9388 > URL: https://issues.apache.org/jira/browse/IGNITE-9388 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > Although it downloads from the archive, for Japan, for instance, it takes 2-3 > hours. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9478) SQL: throw reducer retry error
Vladimir Ozerov created IGNITE-9478:
---
Summary: SQL: throw reducer retry error
Key: IGNITE-9478
URL: https://issues.apache.org/jira/browse/IGNITE-9478
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Fix For: 2.7
Currently we cannot pass correct error message from reducer retry condition to
user exception. Need to fix that. See \{{GridReduceQueryExecutor.logRetry}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9478) SQL: throw reducer retry error
[
https://issues.apache.org/jira/browse/IGNITE-9478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9478:
Labels: sql-stability (was: )
> SQL: throw reducer retry error
> --
>
> Key: IGNITE-9478
> URL: https://issues.apache.org/jira/browse/IGNITE-9478
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
>
> Currently we cannot pass correct error message from reducer retry condition
> to user exception. Need to fix that. See
> \{{GridReduceQueryExecutor.logRetry}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9333) Adding page with simple statistic for last 50 runs.
[
https://issues.apache.org/jira/browse/IGNITE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605488#comment-16605488
]
ASF GitHub Bot commented on IGNITE-9333:
zzzadruga commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r215547228
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -290,14 +298,16 @@ private IgnitePersistentTeamcity(Ignite ignite,
IgniteTeamcityHelper teamcity) {
return mergeByIdToHistoricalOrder(persistedValue, builds);
});
+
+return buildRefs.stream().skip(cnt < buildRefs.size() ?
buildRefs.size() - cnt : 0).collect(Collectors.toList());
Review comment:
If the cache contains more records than requested, then skip the
unnecessary.
For example, there are 100 entries in the cache and our request requires 10
entries. In the final collection will be placed 100 entries from the cache, 10
entries from the apache server (the most likely will be overwrite of the cache
entries), the collection will be placed in the cache (~ 100-103 records) and
will be returned. But we only need 10 records, so 90 entries will be skipped.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Adding page with simple statistic for last 50 runs.
> ---
>
> Key: IGNITE-9333
> URL: https://issues.apache.org/jira/browse/IGNITE-9333
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Eduard Shangareev
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Ok, I am proposing to add a new page which would be named "Statistic".
> It should show last 50 "Run All" for master, the columns:
> ||Id||Total tests||Failed tests||Ignored tests|| Muted tests||Total issues
> (count and the list of TC configurations with links) || Total run time ||
> Also, we need to calculate the statistic.
> Totals (all unique tests with issues), average issues/fails per run, median,
> max, min.
> Total issues = Exit codes + JVM Crashes + OOMs + other issues which caused TC
> configuration fail
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9388) mesos IgniteProvider tries to access obolete ignite.run or download from slow archive
[ https://issues.apache.org/jira/browse/IGNITE-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605476#comment-16605476 ] Ilya Kasnacheev commented on IGNITE-9388: - [~roman_s] I've commented the changes! > mesos IgniteProvider tries to access obolete ignite.run or download from slow > archive > - > > Key: IGNITE-9388 > URL: https://issues.apache.org/jira/browse/IGNITE-9388 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > Although it downloads from the archive, for Japan, for instance, it takes 2-3 > hours. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9472) REST API has no permission checks for cluster activation/deactivation
[ https://issues.apache.org/jira/browse/IGNITE-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604399#comment-16604399 ] Ivan Bessonov edited comment on IGNITE-9472 at 9/6/18 8:08 AM: --- [~ilantukh], thank you! I started tests on Ignite TeamCity, results are not available yet. Considering test for the functionality - test isn't written because "ctx.security().authorize(...)" does nothing by default in Ignite and making dummy test didn't make sense to me. was (Author: ibessonov): [~ilantukh], thank you! I started tests on Ignite TeamCity, results are not available yet. Considering test for the functionality - complex test with GridClient will be available in corresponding GridGain branch, it's already written and waits for this ticket to be resolved. It can't be done here because "ctx.security().authorize(...)" does nothing by default in Ignite. > REST API has no permission checks for cluster activation/deactivation > - > > Key: IGNITE-9472 > URL: https://issues.apache.org/jira/browse/IGNITE-9472 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.7 > > > ADMIN_OPS permission should be required for CLUSTER_ACTIVE / CLUSTER_INACTIVE > commands. This has to be done in GridRestProcessor.authorize method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9472) REST API has no permission checks for cluster activation/deactivation
[ https://issues.apache.org/jira/browse/IGNITE-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-9472: --- Fix Version/s: 2.7 > REST API has no permission checks for cluster activation/deactivation > - > > Key: IGNITE-9472 > URL: https://issues.apache.org/jira/browse/IGNITE-9472 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.7 > > > ADMIN_OPS permission should be required for CLUSTER_ACTIVE / CLUSTER_INACTIVE > commands. This has to be done in GridRestProcessor.authorize method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9477) Enhance dropdown with facilty to behave in "no options" case
Alexander Kalinin created IGNITE-9477: - Summary: Enhance dropdown with facilty to behave in "no options" case Key: IGNITE-9477 URL: https://issues.apache.org/jira/browse/IGNITE-9477 Project: Ignite Issue Type: Improvement Components: UI Reporter: Alexander Kalinin Assignee: Alexander Kalinin Attachments: image-2018-09-06-14-05-24-156.png Currently when no options is available for dropdown it doesn't show list options but neither is disable, and behaves like active. We should add a hint with possiblilty for creating options for this dropdown. Like this: !image-2018-09-06-14-05-24-156.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9372) Web console: Failed to execute query with limited page count
[ https://issues.apache.org/jira/browse/IGNITE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-9372: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) Implemented check on query execution when result page count is limited and query contains *;* symbol. > Web console: Failed to execute query with limited page count > > > Key: IGNITE-9372 > URL: https://issues.apache.org/jira/browse/IGNITE-9372 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > # Open Queries page an input some executable query. > # Change Max pages value from Unlimited. > # Try to execute query or explane query. > Query does not executed with syntax error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9372) Web console: Failed to execute query with limited page count
[ https://issues.apache.org/jira/browse/IGNITE-9372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-9372: - Assignee: Vasiliy Sisko > Web console: Failed to execute query with limited page count > > > Key: IGNITE-9372 > URL: https://issues.apache.org/jira/browse/IGNITE-9372 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > # Open Queries page an input some executable query. > # Change Max pages value from Unlimited. > # Try to execute query or explane query. > Query does not executed with syntax error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
