[jira] [Updated] (IGNITE-11419) Memory leak after multiple restarts of server node within the same thread
[ https://issues.apache.org/jira/browse/IGNITE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov updated IGNITE-11419: - Affects Version/s: 2.7 > Memory leak after multiple restarts of server node within the same thread > - > > Key: IGNITE-11419 > URL: https://issues.apache.org/jira/browse/IGNITE-11419 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Pavel Vinokurov >Priority: Minor > > Multiple restarts of a server node with enabled persistence and 20 caches > lead to OutOfMemory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11419) Memory leak after multiple restarts of server node within the same thread
[ https://issues.apache.org/jira/browse/IGNITE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov updated IGNITE-11419: - Component/s: sql > Memory leak after multiple restarts of server node within the same thread > - > > Key: IGNITE-11419 > URL: https://issues.apache.org/jira/browse/IGNITE-11419 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7 >Reporter: Pavel Vinokurov >Priority: Minor > > Multiple restarts of a server node with enabled persistence and 20 caches > lead to OutOfMemory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11419) Memory leak after multiple restarts of server node within the same thread
[ https://issues.apache.org/jira/browse/IGNITE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov updated IGNITE-11419: - Ignite Flags: (was: Docs Required) > Memory leak after multiple restarts of server node within the same thread > - > > Key: IGNITE-11419 > URL: https://issues.apache.org/jira/browse/IGNITE-11419 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7 >Reporter: Pavel Vinokurov >Priority: Minor > > Multiple restarts of a server node with enabled persistence and 20 caches > lead to OutOfMemory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5250) Unhelpful exception when value of wrong type is passed to H2
[
https://issues.apache.org/jira/browse/IGNITE-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5250:
Fix Version/s: 2.8
> Unhelpful exception when value of wrong type is passed to H2
>
>
> Key: IGNITE-5250
> URL: https://issues.apache.org/jira/browse/IGNITE-5250
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Major
> Labels: usability
> Fix For: 2.8
>
> Attachments: ExampleNodeStartup.java
>
>
> For instance, if an SQL schema defined this way:
> {code}
> cfg.setIndexedTypes(AffinityKey.class, Person.class);
> {code}
> and then, by some reason, the users confuses the type of the key passing
> {{int}} instead of {{AffinityKey}}
> {code}
> SqlFieldsQuery query = new SqlFieldsQuery("INSERT INTO Person (_key,
> id, name, country ) " +
> "VALUES ( ? , ? , ? , ?)");
> // Setting the key of a wrong type (AffinityKey instance must be used
> instead).
> query.setArgs(100, 1000, "John", "Canada");
> // Getting not user friendly exception.
> cache.query(query).getAll();
> {code}
> he will get an exception that doesn't point out to the exact root cause:
> {noformat}
> Caused by: class org.apache.ignite.IgniteException: Failed to execute SQL
> query.
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:365)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:94)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:836)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:378)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:173)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:207)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1657)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1701)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1699)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2129)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1706)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:783)
> ... 6 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute
> SQL query.
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:1224)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1276)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.access$1300(IgniteH2Indexing.java:239)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1079)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1067)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$3.iterator(DmlStatementsProcessor.java:362)
> ... 18 more
> Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number
> of characters: "100"; SQL statement:
> SELECT
> TABLE._KEY,
> TABLE.ID,
> TABLE.NAME,
> TABLE.COUNTRY
> FROM TABLE(_KEY OTHER=(?1,), ID BIGINT=(?2,), NAME VARCHAR=(?3,), COUNTRY
> VARCHAR=(?4,)) [90003-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930)
> at org.h2.value.Value.convertTo(Value.java:957)
> at org.h2.table.Column.convert(Column.java:167)
> at org.h2.expression.TableFunction.getTable(TableFunction.java:118)
> at org.h2.expression.TableFunction.getValue(TableFunction.java:41)
> at org.h2.table.FunctionTable.getValueResultSet(FunctionTable.java:218)
> at org.h2.table.Fun
[jira] [Commented] (IGNITE-11419) Memory leak after multiple restarts of server node within the same jvm
[
https://issues.apache.org/jira/browse/IGNITE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784180#comment-16784180
]
Pavel Vinokurov commented on IGNITE-11419:
--
ConnectionManager declares the thread local variable initialized by the
instance of anonymous class.Thus the thread local variably linked with the
ConnectionManager. It leads to memory leak.
{code:java}
/** Connection cache. */
private final
ThreadLocal.Reusable> threadConn =
new ThreadLocal.Reusable>() {
@Override public ThreadLocalObjectPool.Reusable
get() {
ThreadLocalObjectPool.Reusable reusable =
super.get();
{code}
> Memory leak after multiple restarts of server node within the same jvm
> --
>
> Key: IGNITE-11419
> URL: https://issues.apache.org/jira/browse/IGNITE-11419
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Vinokurov
>Priority: Minor
>
> Multiple restarts of a server node with enabled persistence and 20 caches
> lead to OutOfMemory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11419) Memory leak after multiple restarts of server node within the same thread
[ https://issues.apache.org/jira/browse/IGNITE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov updated IGNITE-11419: - Summary: Memory leak after multiple restarts of server node within the same thread (was: Memory leak after multiple restarts of server node within the same jvm) > Memory leak after multiple restarts of server node within the same thread > - > > Key: IGNITE-11419 > URL: https://issues.apache.org/jira/browse/IGNITE-11419 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Vinokurov >Priority: Minor > > Multiple restarts of a server node with enabled persistence and 20 caches > lead to OutOfMemory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11446) Common prefix for local node system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11446: - Ignite Flags: (was: Docs Required) > Common prefix for local node system SQL view > > > Key: IGNITE-11446 > URL: https://issues.apache.org/jira/browse/IGNITE-11446 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > All local views should have common prefix. Agreed on "LOCAL_". Now it affects > view CACHE_GROUPS_IO only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10161) Be able to cancel any query by query id
[
https://issues.apache.org/jira/browse/IGNITE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784171#comment-16784171
]
Ray Liu commented on IGNITE-10161:
--
[~jooger]
Just want to confirm, does this ticket supports cancel time consuming DDL like
create/drop index?
Or does it supports DML only?
> Be able to cancel any query by query id
> ---
>
> Key: IGNITE-10161
> URL: https://issues.apache.org/jira/browse/IGNITE-10161
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User should be able to cancel any query by query id through SQL command.
> SQL syntax: *KILL QUERY '<_query_id>' \{ASYNC}_*
> _ASYNC_ is optional parameter which return control immediately without
> waiting real cancellation will be done.
> By default, without ASYNC parameter, the request is blocking untill
> cancellation is not done.
> Query should be canceled together with its parts on all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11446) Common prefix for local node system SQL view
[
https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784142#comment-16784142
]
Ignite TC Bot commented on IGNITE-11446:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3231904&buildTypeId=IgniteTests24Java8_RunAll]
> Common prefix for local node system SQL view
>
>
> Key: IGNITE-11446
> URL: https://issues.apache.org/jira/browse/IGNITE-11446
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> All local views should have common prefix. Agreed on "LOCAL_". Now it affects
> view CACHE_GROUPS_IO only.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11384) Introduce an ability of services hot redeployment via DeploymentSpi
[
https://issues.apache.org/jira/browse/IGNITE-11384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784128#comment-16784128
]
Ignite TC Bot commented on IGNITE-11384:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3235471&buildTypeId=IgniteTests24Java8_RunAll]
> Introduce an ability of services hot redeployment via DeploymentSpi
> ---
>
> Key: IGNITE-11384
> URL: https://issues.apache.org/jira/browse/IGNITE-11384
> Project: Ignite
> Issue Type: Sub-task
> Components: managed services
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Labels: iep-17
> Fix For: 2.8
>
>
> We can integrate service processor with DeploymentSpi to introduce an
> opportunity of services hot redeployment. For this change, the service
> processor should try to get and use registered classloader registered for the
> service's class in DeploymentSpi.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8420) "Unignore" Web console unit tests
[ https://issues.apache.org/jira/browse/IGNITE-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784077#comment-16784077 ] Ilya Borisov commented on IGNITE-8420: -- [~alexdel] looks OK, [~kuaw26] please merge. > "Unignore" Web console unit tests > - > > Key: IGNITE-8420 > URL: https://issues.apache.org/jira/browse/IGNITE-8420 > Project: Ignite > Issue Type: Test > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > Original Estimate: 32h > Time Spent: 10h 10m > Remaining Estimate: 21h 50m > > Currently he have about 40 muted tests in web console front-end. They should > revised, and updated an or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8420) "Unignore" Web console unit tests
[ https://issues.apache.org/jira/browse/IGNITE-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-8420: Assignee: Alexey Kuznetsov (was: Ilya Borisov) > "Unignore" Web console unit tests > - > > Key: IGNITE-8420 > URL: https://issues.apache.org/jira/browse/IGNITE-8420 > Project: Ignite > Issue Type: Test > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > Original Estimate: 32h > Time Spent: 10h 10m > Remaining Estimate: 21h 50m > > Currently he have about 40 muted tests in web console front-end. They should > revised, and updated an or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8420) "Unignore" Web console unit tests
[ https://issues.apache.org/jira/browse/IGNITE-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-8420: - Assignee: Ilya Borisov (was: Alexander Kalinin) > "Unignore" Web console unit tests > - > > Key: IGNITE-8420 > URL: https://issues.apache.org/jira/browse/IGNITE-8420 > Project: Ignite > Issue Type: Test > Components: wizards >Reporter: Alexander Kalinin >Assignee: Ilya Borisov >Priority: Major > Original Estimate: 32h > Time Spent: 10h 10m > Remaining Estimate: 21h 50m > > Currently he have about 40 muted tests in web console front-end. They should > revised, and updated an or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8420) "Unignore" Web console unit tests
[ https://issues.apache.org/jira/browse/IGNITE-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784060#comment-16784060 ] Alexander Kalinin commented on IGNITE-8420: --- [@Klaster1|https://github.com/Klaster1] I've managed to repairt some unit tests. Tests I didn't manage to repair were deleted. Please review my PR - https://github.com/apache/ignite/pull/6229 > "Unignore" Web console unit tests > - > > Key: IGNITE-8420 > URL: https://issues.apache.org/jira/browse/IGNITE-8420 > Project: Ignite > Issue Type: Test > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Original Estimate: 32h > Time Spent: 10h 10m > Remaining Estimate: 21h 50m > > Currently he have about 40 muted tests in web console front-end. They should > revised, and updated an or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11423) Multiple configurations to SpringCacheManager
[ https://issues.apache.org/jira/browse/IGNITE-11423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinil Lee updated IGNITE-11423: --- Ignite Flags: (was: Docs Required) Labels: newbie pull-request-available (was: newbie) Component/s: spring > Multiple configurations to SpringCacheManager > - > > Key: IGNITE-11423 > URL: https://issues.apache.org/jira/browse/IGNITE-11423 > Project: Ignite > Issue Type: Improvement > Components: cache, spring >Reporter: Jinil Lee >Priority: Minor > Labels: newbie, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > I'm using SpringCacheManager for my project. > I want to apply each cache-specific configuration (eg expiry policy), > but only one configuration applies when I create the cachemanager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11273) IgniteCassandraStoreTestSuite failed under Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783735#comment-16783735
]
Pankaj Kumar commented on IGNITE-11273:
---
Hello [~dpavlov], I'm not able to reproduce this using maven and also running
stand alone test case in Intellij Idea.
Here is what I have done -
* Compiled source code using Java 8.
* set MAVEN_OPTS as (to make it same as TeamCity)
{noformat}
set MAVEN_OPTS=-ea -server -Xmx2g -Xms2g -XX:+HeapDumpOnOutOfMemoryError
-XX:+AggressiveOpts -DIGNITE_UPDATE_NOTIFIER=false -DIGNITE_NO_DISCO_ORDER=true
-DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true -DIGNITE_QUIET=false
-Djava.net.preferIPv4Stack=true -DTEST_SCALE_FACTOR=0.1 --illegal-access=permit
--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
--add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED
-Djdk.tls.client.protocols=TLSv1.2{noformat}
* Run mvn test -Dtest=IgniteCassandraStoreTestSuite with maven version 3.6.0
and JDK (open JDK 11.02)
* I never get error 'java.lang.ExceptionInInitializerError' and also few of
the test cases passes.
* I get different error for few of test cases 'Caused by:
org.apache.cassandra.io.FSWriteError: java.nio.file.AccessDeniedException:
.\data\commitlog\CommitLog-6-1551728511594.log'
Another approach which I tried was running JUnit test case in IntellijIdea by
setting VM option same as above MAVEN_OPTS.
BTW, I was not able to run test cases using maven profile java-9+ as I was
getting invalid source/target 11 error.
I am running test cases on windows machine. I suspect it could be because of OS
(linux) or Open JDK version.
Could you please confirm if same error comes on windows machine and what is the
Open JDK version used in TeamCity ?
> IgniteCassandraStoreTestSuite failed under Java 11
> --
>
> Key: IGNITE-11273
> URL: https://issues.apache.org/jira/browse/IGNITE-11273
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=3027678&buildTypeId=IgniteTests24Java8_CassandraStore
> store.IgniteCassandraStoreTestSuite
> {noformat}
> java.lang.RuntimeException: Failed to start embedded Cassandra instance
> at
> org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:59)
> Caused by: java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
> Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length
> 5
> at
> org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts
[
https://issues.apache.org/jira/browse/IGNITE-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783615#comment-16783615
]
Ignite TC Bot commented on IGNITE-11464:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=3233966]]
* IgniteCacheWithIndexingAndPersistenceTestSuite:
GridCommandHandlerIndexingTest.testValidateIndexesNoErrors - 0,0% fails in last
449 master runs.
* IgniteCacheWithIndexingAndPersistenceTestSuite:
GridCommandHandlerIndexingTest.testBrokenCacheDataTreeShouldFailValidation -
0,0% fails in last 449 master runs.
* IgniteCacheWithIndexingAndPersistenceTestSuite:
GridCommandHandlerIndexingTest.testBrokenSqlIndexShouldFailValidation - 0,0%
fails in last 449 master runs.
* IgniteCacheWithIndexingAndPersistenceTestSuite:
GridCommandHandlerIndexingTest.testCorruptedIndexPartitionShouldFailValidation
- 0,0% fails in last 449 master runs.
{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3233967]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3232869&buildTypeId=IgniteTests24Java8_RunAll]
> Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix
> queries and visor package conflicts
>
>
> Key: IGNITE-11464
> URL: https://issues.apache.org/jira/browse/IGNITE-11464
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> error: the unnamed module reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: the unnamed module reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: the unnamed module reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module ignite.indexing reads package org.apache.lucene.search from
> both lucene.sandbox and lucene.core
> error: module ignite.indexing reads package org.apache.lucene.document from
> both lucene.sandbox and lucene.core
> error: module ignite.indexing reads package
> org.apache.lucene.analysis.standard from both lucene.core and
> lucene.analyzers.common
> error: module ignite.indexing reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module ignite.indexing reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module cache.api reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module cache.api reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module cache.api reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module cache.api reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module cache.api reads package org.apache.ignite.internal.visor.verify
> from both ignite.indexing and ignite.core
> error: module annotations reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module annotations reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module annotations reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module annotations reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module annotations reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module ignite.shmem reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module ignite.shmem reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module ignite.shmem reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module ignite.shmem reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module ignite.shmem reads package
> org.apache.ignite.internal.visor
[jira] [Commented] (IGNITE-10561) MVCC: Fix MVCC cache rebalance.
[
https://issues.apache.org/jira/browse/IGNITE-10561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783613#comment-16783613
]
Roman Kondakov commented on IGNITE-10561:
-
[~amashenkov], patch looks very good for me. You've fixed a lot of stuff. But
there are several unclear points for me:
# {{GridCacheMvccEntryInfo}} - looks like the estimate of the entry size is
wrong:
{{SIZE_OVERHEAD = 4 * 8 /* long */ + 2 /* int */;}}
Shouldn't it be
{{SIZE_OVERHEAD = 4 * 8 /* long */ + 2 * 4* /* int */;}} ?
# I've noticed that we set missed hints to {{opCntr}} in the three places:
## {{GridDhtPartitionSupplier#extractEntryInfo}}
## {{MvccDataRow#readHeader}}
## {{GridDhtTxAbstractEnlistFuture#fetchHistoryInfo}}
What if instead of duplicating such a messy and low-level code in several
places we would left it only within {{MvccDataRow#readHeader}}?
# A bit weird naming of the {{added}} variable in
{{GridCacheMapEntry.java:6735}}. Looks like the real meaning of this variable
is opposite. Would it be better to remove negation and then do {{if (!added)
break;}}?
# Why do we need additional WAL entry for the latest entry ({{entries[0]}}) in
the case of delete operation at {{GridCacheMapEntry.java:6765}}?
# Is it possible to use {{BPlusTree#find(Max, Min, RowData.LINK_ONLY)}} and
then check for {{GridCursor#next}} to find out if there is any history of row
exists in the tree, Instead of using {{CheckHistoryExistsClosure}} in
{{IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#mvccApplyHistoryIfAbsent}}?
# Why do we need 400 GB region size in mvcc case? See
{{GridCTextacheRebalancingSyncSelfTest.java:111}}
> MVCC: Fix MVCC cache rebalance.
> ---
>
> Key: IGNITE-10561
> URL: https://issues.apache.org/jira/browse/IGNITE-10561
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Critical
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unexpected transaction state may be observed on some nodes after rebalance.
> Reproducer: {{GridCacheRebalancingSyncSelfTest#testComplexRebalancing}}
> Stacktrace:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccSnapshotSearchRow [res=null,
> snapshot=MvccSnapshotResponse [futId=149236, crdVer=1544033736224,
> cntr=800063, opCntr=1073741823, txs=null, cleanupVer=0, tracking=0]],
> upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:931)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:640)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingSyncSelfTest.checkData(GridCacheRebalancingSyncSelfTest.java:251)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingSyncSelfTest.checkData(GridCacheRebalancingSyncSelfTest.java:213)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingSyncSelfTest.testComplexRebalancing(GridCacheRebalancingSyncSelfTest.java:588)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccSnapshotSearchRow [res=null, snapshot=MvccSnapshotResponse
> [futId=149236, crdVer=1544033736224, cntr=800063, opCntr=1073741823,
> txs=null, cleanupVer=0, tracking=0]], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.iterate(BPlusTree.java:1035)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOff
[jira] [Comment Edited] (IGNITE-11471) JDBC: Thin driver should start with a random server to connect
[ https://issues.apache.org/jira/browse/IGNITE-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783581#comment-16783581 ] Stanislav Lukyanov edited comment on IGNITE-11471 at 3/4/19 5:29 PM: - Choice of the server was random initially, but it was changed to a JVM-local round-robin in IGNITE-9704. Need to keep the `AtomicLong` for local round-robin, but initialize it with a random value instead of zero. was (Author: slukyanov): Choice of the server was random initially, but it was changed to a JVM-local round-robin in IGNITE-9704. Need to use keep the `AtomicLong` for local round-robin, but initialize it with a random value instead of zero. > JDBC: Thin driver should start with a random server to connect > -- > > Key: IGNITE-11471 > URL: https://issues.apache.org/jira/browse/IGNITE-11471 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Priority: Major > Labels: newbie > > Thin JDBC driver uses a list of server addresses to connect to. Connections > created in a single JVM will use round-robin to choose the server to connect, > yielding a uniform distribution. However, the round-robin always starts from > the first server in the list. It means that multiple JVMs with the same JDBC > connection URL and one connection each will all connect to the same server. > Need to choose the first server randomly to have a better distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6609) H2PkHashIndex.H2Cursor doesn't take in count expiration
[
https://issues.apache.org/jira/browse/IGNITE-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783576#comment-16783576
]
Ignite TC Bot commented on IGNITE-6609:
---
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Cache 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3175720]]
{color:#d04437}Cache (Full API){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3175676]]
* IgniteCacheFullApiSelfTestSuite:
GridCacheReplicatedNearOnlyMultiNodeFullApiSelfTest.testTtlTx - 0,0% fails in
last 599 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3175732&buildTypeId=IgniteTests24Java8_RunAll]
> H2PkHashIndex.H2Cursor doesn't take in count expiration
> ---
>
> Key: IGNITE-6609
> URL: https://issues.apache.org/jira/browse/IGNITE-6609
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Correct: {{H2Cursor#next}} - expire time is checked;
> Incorrect: {{H2PkHashIndex.H2Cursor#next}} - expired time is ignored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11471) JDBC: Thin driver should start with a random server to connect
[ https://issues.apache.org/jira/browse/IGNITE-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783581#comment-16783581 ] Stanislav Lukyanov commented on IGNITE-11471: - Choice of the server was random initially, but it was changed to a JVM-local round-robin in IGNITE-9704. Need to use keep the `AtomicLong` for local round-robin, but initialize it with a random value instead of zero. > JDBC: Thin driver should start with a random server to connect > -- > > Key: IGNITE-11471 > URL: https://issues.apache.org/jira/browse/IGNITE-11471 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Priority: Major > Labels: newbie > > Thin JDBC driver uses a list of server addresses to connect to. Connections > created in a single JVM will use round-robin to choose the server to connect, > yielding a uniform distribution. However, the round-robin always starts from > the first server in the list. It means that multiple JVMs with the same JDBC > connection URL and one connection each will all connect to the same server. > Need to choose the first server randomly to have a better distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11282) NullPointerException if transaction enabled and using byte[] for key/value
[
https://issues.apache.org/jira/browse/IGNITE-11282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783578#comment-16783578
]
Ignite TC Bot commented on IGNITE-11282:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI (URI Deploy){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3227003]]
* IgniteUriDeploymentTestSuite:
GridHttpDeploymentSelfTest.testDeployUndeploy2Files - 0,0% fails in last 76
master runs.
* IgniteUriDeploymentTestSuite: GridHttpDeploymentSelfTest.testSameContantFiles
- 0,0% fails in last 76 master runs.
{color:#d04437}MVCC Queries{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3227005]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay
- 0,0% fails in last 273 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 0 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccReplicatedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 0 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3218619&buildTypeId=IgniteTests24Java8_RunAll]
> NullPointerException if transaction enabled and using byte[] for key/value
> --
>
> Key: IGNITE-11282
> URL: https://issues.apache.org/jira/browse/IGNITE-11282
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Courtney
>Assignee: Igor Akkuratov
>Priority: Blocker
> Attachments: Screen Shot 2019-02-10 at 15.02.19.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I have debugged this and found the problem is because of hashCode comparison
> failure. You can see in the screenshot below.
> {code:java}
> txMap == null ? null : txMap.get(key)
> {code}
> this will fail to get the entry but they the key is in fact in the map, it's
> the only entry and if a proper array comparison is done e.g. using
> `Arrays.equals` as shown in the eval window then the key would match. !Screen
> Shot 2019-02-10 at 15.02.19.png!
> If running without `-ea` then the exception is
> {code:java}
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> io.hypi.arc.ignite.ArcIgniteUtils.lambda$asFuture$f0cf812f$1(ArcIgniteUtils.java:21)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
[jira] [Commented] (IGNITE-10937) Support data page scan for JDBC
[
https://issues.apache.org/jira/browse/IGNITE-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783577#comment-16783577
]
Ignite TC Bot commented on IGNITE-10937:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185276]]
{color:#d04437}SPI (URI Deploy){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185270]]
{color:#d04437}Start Nodes{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185268]]
{color:#d04437}Cache (Expiry Policy){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185292]]
{color:#d04437}MVCC Cache 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185341]]
{color:#d04437}MVCC Queries{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185287]]
{color:#d04437}SPI{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185269]]
{color:#d04437}PDS (Compatibility){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185316]]
{color:#d04437}MVCC PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185350]]
{color:#d04437}MVCC Cache{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185285]]
{color:#d04437}Service Grid (legacy mode){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185339]]
{color:#d04437}MVCC Cache 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185342]]
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185277]]
{color:#d04437}Client Nodes{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185244]]
{color:#d04437}Queries 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185330]]
{color:#d04437}Cache 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185304]]
{color:#d04437}Cache (Restarts) 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185300]]
{color:#d04437}Cache 8{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185309]]
{color:#d04437}Cache 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185302]]
{color:#d04437}MVCC Cache 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185345]]
{color:#d04437}Cache (Restarts) 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185299]]
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185335]]
{color:#d04437}Cache 6{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185307]]
{color:#d04437}PDS (Indexing){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185318]]
{color:#d04437}MVCC PDS 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185349]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185334]]
{color:#d04437}MVCC PDS 4{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185352]]
{color:#d04437}Spring{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185265]]
{color:#d04437}Java Client{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185257]]
{color:#d04437}Cache 7{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185308]]
{color:#d04437}Basic 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185281]]
{color:#d04437}Continuous Query 3{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185312]]
{color:#d04437}Cache (Deadlock Detection){color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185291]]
{color:#d04437}Service Grid{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185338]]
{color:#d04437}Queries 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185264]]
{color:#d04437}PDS 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185321]]
{color:#d04437}Cache 5{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185306]]
{color:#d04437}MVCC Cache 1{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185340]]
{color:#d04437}Cache 2{color} [[tests 0
CANCELLED|https://ci.ignite.apache.org/viewLog.html?buildId=3185303]]
{color:#d04437}Platform C++ (Win x6
[jira] [Commented] (IGNITE-11059) Print information about pending locks queue in case of dht local tx timeout.
[
https://issues.apache.org/jira/browse/IGNITE-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783575#comment-16783575
]
Ignite TC Bot commented on IGNITE-11059:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI (URI Deploy){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3199607]]
* IgniteUriDeploymentTestSuite:
GridHttpDeploymentSelfTest.testDeployUndeploy2Files - 0,0% fails in last 76
master runs.
* IgniteUriDeploymentTestSuite: GridHttpDeploymentSelfTest.testSameContantFiles
- 0,0% fails in last 76 master runs.
{color:#d04437}MVCC Queries{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=3199609]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay
- 0,0% fails in last 273 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 0 master runs.
* IgniteCacheMvccSqlTestSuite:
CacheMvccReplicatedSqlCoordinatorFailoverTest.testAccountsTxSql_SingleNode_CoordinatorFails_Persistence
- 0,0% fails in last 0 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3195514&buildTypeId=IgniteTests24Java8_RunAll]
> Print information about pending locks queue in case of dht local tx timeout.
>
>
> Key: IGNITE-11059
> URL: https://issues.apache.org/jira/browse/IGNITE-11059
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Ivan Daschinskiy
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently in case of dht local tx timeout it's hard to understand which keys
> was not locked.
> Addtional information should be printed in log on timeout containing
> information about pending keys:
> key, tx info holding a lock (xid, label if present)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11471) JDBC: Thin driver should start with a random server to connect
Stanislav Lukyanov created IGNITE-11471: --- Summary: JDBC: Thin driver should start with a random server to connect Key: IGNITE-11471 URL: https://issues.apache.org/jira/browse/IGNITE-11471 Project: Ignite Issue Type: Improvement Components: jdbc Reporter: Stanislav Lukyanov Thin JDBC driver uses a list of server addresses to connect to. Connections created in a single JVM will use round-robin to choose the server to connect, yielding a uniform distribution. However, the round-robin always starts from the first server in the list. It means that multiple JVMs with the same JDBC connection URL and one connection each will all connect to the same server. Need to choose the first server randomly to have a better distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io This type of failure is named package inference, but it is strictly prohibited http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Following table contains currenly investigated Ignite modules if this applicability as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is required from our pom.xml or by user | |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| |ignite-rest-http | (x) IGNITE-11469 | (/) | was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io This type of failure is named package inference, but it is strictly prohibited http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Following table contains currenly investigated Ignite modules if this applicability as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is required from our pom.xml or by user | |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > This type of failure is named package inference, but it is strictly > prohibited > http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Following table contains currenly investigated Ignite modules if this > applicability as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is > required from our pom.xml or by user | > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected| > |ignite-ml |(x) blocked by indexing | | > |ignite-log4j|(/)|(/) - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > |ignite-slf4j | (/)|(/)| > |ignite-rest-http | (x) IGNITE-11469 | (/) | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10161) Be able to cancel any query by query id
[
https://issues.apache.org/jira/browse/IGNITE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783535#comment-16783535
]
Ignite TC Bot commented on IGNITE-10161:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3231522&buildTypeId=IgniteTests24Java8_RunAll]
> Be able to cancel any query by query id
> ---
>
> Key: IGNITE-10161
> URL: https://issues.apache.org/jira/browse/IGNITE-10161
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User should be able to cancel any query by query id through SQL command.
> SQL syntax: *KILL QUERY '<_query_id>' \{ASYNC}_*
> _ASYNC_ is optional parameter which return control immediately without
> waiting real cancellation will be done.
> By default, without ASYNC parameter, the request is blocking untill
> cancellation is not done.
> Query should be canceled together with its parts on all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11469) Support Automatic modules for ignite-rest-http: resolve package inference between Jetty & Tomcat
[
https://issues.apache.org/jira/browse/IGNITE-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-11469:
---
Assignee: Dmitriy Pavlov
> Support Automatic modules for ignite-rest-http: resolve package inference
> between Jetty & Tomcat
>
>
> Key: IGNITE-11469
> URL: https://issues.apache.org/jira/browse/IGNITE-11469
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> {noformat}
> error: the unnamed module reads package javax.servlet.http from both
> javax.servlet.api and tomcat.servlet.api
> error: the unnamed module reads package javax.servlet.descriptor from both
> javax.servlet.api and tomcat.servlet.api
> error: the unnamed module reads package javax.servlet.annotation from both
> javax.servlet.api and tomcat.servlet.api
> error: the unnamed module reads package javax.servlet from both
> javax.servlet.api and tomcat.servlet.api
> {noformat}
> Exclude of tomcat dependency solves the problem
> {code}
> compile(group: 'org.apache.ignite', name: 'ignite-rest-http', version:
> ignVer) {
> exclude group: 'org.apache.tomcat'
> // to remove "javax.servlet.http, javax.servlet.descriptor,
> javax.servlet.annotation, javax.servlet" package conflicts.
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11470) Views don't show in Dbeaver
Yury Gerzhedovich created IGNITE-11470: -- Summary: Views don't show in Dbeaver Key: IGNITE-11470 URL: https://issues.apache.org/jira/browse/IGNITE-11470 Project: Ignite Issue Type: Task Components: sql Reporter: Yury Gerzhedovich Assignee: Yury Gerzhedovich Fix For: 2.8 At Database navigator tab we can see no a views. As of now we should see at least SQL system views. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7664) SQL: throw sane exception on unsupported SQL statements
[
https://issues.apache.org/jira/browse/IGNITE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783518#comment-16783518
]
Taras Ledkov commented on IGNITE-7664:
--
- The trivial short patches for IGNITE-11450 (HELP / SHOW) and IGNITE-11453
(GRANT / REVOKE) are included into the patch for this issue.
- Adds check for unsupported types: {{TIMESTAMP WITH ZONE}} and {{ENUM}}.
> SQL: throw sane exception on unsupported SQL statements
> ---
>
> Key: IGNITE-7664
> URL: https://issues.apache.org/jira/browse/IGNITE-7664
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Paschenko
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Inspired by this SO issue:
> [https://stackoverflow.com/questions/48708238/ignite-database-create-schema-assertionerror]
> We should handle unsupported stuff more gracefully both in core code and
> drivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10663) Cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--
Description:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
{{cache.withConsistencyCheck().get(key)}} should guarantee values will be
checked across the topology and fixed if necessary.
LWW (Last Write Wins) strategy should be used for validation.
Since LWW and any other strategy do not guarantee that the correct value will
be chosen.
We have to record the event contains all values and the chosen one.
The event will allow to
- got we have an inconsistent state situation
- investigate which value is correct manually and refix if necessary
was:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
{{Cache.withConsistencyCheck()}} should guarantee values will be checked across
the topology and fixed if necessary.
LWW (Last Write Wins) strategy should be used for validation.
Since LWW and any other strategy do not guarantee that the correct value will
be chosen.
We have to record the event contains all values and the chosen one.
The event will allow to
- got we have an inconsistent state situation
- investigate which value is correct manually and refix if necessary
> Cache mode allows reads with consistency check and fix
> --
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> {{cache.withConsistencyCheck().get(key)}} should guarantee values will be
> checked across the topology and fixed if necessary.
> LWW (Last Write Wins) strategy should be used for validation.
> Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
> The event will allow to
> - got we have an inconsistent state situation
> - investigate which value is correct manually and refix if necessary
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10663) Cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--
Description:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
{{Cache.withConsistencyCheck()}} should guarantee values will be checked across
the topology and fixed if necessary.
LWW (Last Write Wins) strategy should be used for validation.
Since LWW and any other strategy do not guarantee that the correct value will
be chosen.
We have to record the event contains all values and the chosen one.
The event will allow to
- got we have an inconsistent state situation
- investigate which value is correct manually and refix if necessary
was:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
{{Cache.withConsistencyCheck()}} should guarantee values will be checked across
the topology and fixed if necessary.
> Cache mode allows reads with consistency check and fix
> --
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> {{Cache.withConsistencyCheck()}} should guarantee values will be checked
> across the topology and fixed if necessary.
> LWW (Last Write Wins) strategy should be used for validation.
> Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
> The event will allow to
> - got we have an inconsistent state situation
> - investigate which value is correct manually and refix if necessary
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10663) Cache mode allows reads with consistency check and fix
[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--
Description:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
{{Cache.withConsistencyCheck()}} should guarantee values will be checked across
the topology and fixed if necessary.
was:Need to provide API to make sure that all data nodes contain the same
value per key.
> Cache mode allows reads with consistency check and fix
> --
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> {{Cache.withConsistencyCheck()}} should guarantee values will be checked
> across the topology and fixed if necessary.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11469) Support Automatic modules for ignite-rest-http: resolve package inference between Jetty & Tomcat
Dmitriy Pavlov created IGNITE-11469:
---
Summary: Support Automatic modules for ignite-rest-http: resolve
package inference between Jetty & Tomcat
Key: IGNITE-11469
URL: https://issues.apache.org/jira/browse/IGNITE-11469
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
{noformat}
error: the unnamed module reads package javax.servlet.http from both
javax.servlet.api and tomcat.servlet.api
error: the unnamed module reads package javax.servlet.descriptor from both
javax.servlet.api and tomcat.servlet.api
error: the unnamed module reads package javax.servlet.annotation from both
javax.servlet.api and tomcat.servlet.api
error: the unnamed module reads package javax.servlet from both
javax.servlet.api and tomcat.servlet.api
{noformat}
Exclude of tomcat dependency solves the problem
{code}
compile(group: 'org.apache.ignite', name: 'ignite-rest-http', version: ignVer)
{
exclude group: 'org.apache.tomcat'
// to remove "javax.servlet.http, javax.servlet.descriptor,
javax.servlet.annotation, javax.servlet" package conflicts.
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10663) Cache mode allows reads with consistency check and fix
[ https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-10663: -- Summary: Cache mode allows reads with consistency check and fix (was: Consistency check) > Cache mode allows reads with consistency check and fix > -- > > Key: IGNITE-10663 > URL: https://issues.apache.org/jira/browse/IGNITE-10663 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-31 > Fix For: 2.8 > > > Need to provide API to make sure that all data nodes contain the same value > per key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8178) ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
[
https://issues.apache.org/jira/browse/IGNITE-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8178:
---
Fix Version/s: 2.8
> ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
> ---
>
> Key: IGNITE-8178
> URL: https://issues.apache.org/jira/browse/IGNITE-8178
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following stack trace appears in logs:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGridsMultiThreaded(GridAbstractTest.java:710)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:497)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectServersRestart(ZookeeperDiscoverySpiTest.java:3513)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testReconnectServersRestart_1(ZookeeperDiscoverySpiTest.java:3498)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:46237,127.0.0.1:38364,127.0.0.1:45674,
> joinTimeout=0, sesTimeout=1, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 24 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> ... 26 more
> C
[jira] [Updated] (IGNITE-10663) Consistency check
[ https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-10663: -- Labels: iep-31 (was: ) > Consistency check > - > > Key: IGNITE-10663 > URL: https://issues.apache.org/jira/browse/IGNITE-10663 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-31 > Fix For: 2.8 > > > Need to provide API to make sure that all data nodes contain the same value > per key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io This type of failure is named package inference, but it is strictly prohibited http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Following table contains currenly investigated Ignite modules if this applicability as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is required from our pom.xml or by user | |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| |ignite-slf4j | (/)|(/)| was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | ignite-slf4j | (/)|(/)| > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > This type of failure is named package inference, but it is strictly > prohibited > http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Following table contains currenly investigated Ignite modules if this > applicability as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/) (!) Lucene artifacts exclusion is > required from our pom.xml or by user | > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected| > |ignite-ml |(x) blocked by indexing | | > |ignite-log4j|(/)|(/) - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > |ignite-slf4j | (/)|(/)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783435#comment-16783435 ] Dmitriy Pavlov commented on IGNITE-11461: - [~qvad], could you please take a look at the new standalone project for testing Ignite as being runnable in java 9+ modular system? > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected| > |ignite-ml |(x) blocked by indexing | | > |ignite-log4j|(/)|(/) - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > | ignite-slf4j | (/)|(/)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7679) Move all test plugins to a separate module
[ https://issues.apache.org/jira/browse/IGNITE-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-7679: Labels: (was: newbie) > Move all test plugins to a separate module > -- > > Key: IGNITE-7679 > URL: https://issues.apache.org/jira/browse/IGNITE-7679 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Govorukhin >Priority: Major > Fix For: 2.8 > > > Curretly all test run with plugins (TestReconnectPlugin > 1.0,StanByClusterTestProvider 1.0, because it is in classpath), this makes > the tests not clean. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | |ignite-log4j|(/)|(/) - EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | |ignite-log4j2|(/)|(/)| | ignite-slf4j | (/)|(/)| was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected| > |ignite-ml |(x) blocked by indexing | | > |ignite-log4j|(/)|(/) - EOL > https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 | > |ignite-log4j2|(/)|(/)| > | ignite-slf4j | (/)|(/)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11468) System caches should not survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11468: -- Ignite Flags: (was: Docs Required) > System caches should not survive client reconnect > - > > Key: IGNITE-11468 > URL: https://issues.apache.org/jira/browse/IGNITE-11468 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > > After IGNITE-10898 it became clear that system caches surviving client > reconnect lead are error-prone: there are too many specific code paths > leading to logic duplication and exclusions. At the same time, the benefit of > system caches survival is not tangible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11468) System caches should not survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11468: - Assignee: Alexey Goncharuk > System caches should not survive client reconnect > - > > Key: IGNITE-11468 > URL: https://issues.apache.org/jira/browse/IGNITE-11468 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > > After IGNITE-10898 it became clear that system caches surviving client > reconnect lead are error-prone: there are too many specific code paths > leading to logic duplication and exclusions. At the same time, the benefit of > system caches survival is not tangible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11468) System caches should not survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11468: -- Fix Version/s: 2.8 > System caches should not survive client reconnect > - > > Key: IGNITE-11468 > URL: https://issues.apache.org/jira/browse/IGNITE-11468 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > > After IGNITE-10898 it became clear that system caches surviving client > reconnect lead are error-prone: there are too many specific code paths > leading to logic duplication and exclusions. At the same time, the benefit of > system caches survival is not tangible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11468) System caches should not survive client reconnect
Alexey Goncharuk created IGNITE-11468: - Summary: System caches should not survive client reconnect Key: IGNITE-11468 URL: https://issues.apache.org/jira/browse/IGNITE-11468 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk After IGNITE-10898 it became clear that system caches surviving client reconnect lead are error-prone: there are too many specific code paths leading to logic duplication and exclusions. At the same time, the benefit of system caches survival is not tangible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7679) Move all test plugins to a separate module
[
https://issues.apache.org/jira/browse/IGNITE-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783402#comment-16783402
]
Maxim Muzafarov commented on IGNITE-7679:
-
It seems to me that the list of plugins a bit grow up:
{code}
TestReconnectPlugin 1.0
StanByClusterTestProvider 1.0
PageMemory tracker plugin 1.0
TestDistibutedConfigurationPlugin 1.0
NodeValidationPluginProvider 1.0
{code}
Probably, we should remove them too.
> Move all test plugins to a separate module
> --
>
> Key: IGNITE-7679
> URL: https://issues.apache.org/jira/browse/IGNITE-7679
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
>
> Curretly all test run with plugins (TestReconnectPlugin
> 1.0,StanByClusterTestProvider 1.0, because it is in classpath), this makes
> the tests not clean.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affercted| |ignite-ml |(x) blocked by indexing | | was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | |ignite-ml |(x) blocked by indexing | > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affercted| > |ignite-ml |(x) blocked by indexing | | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affected| |ignite-ml |(x) blocked by indexing | | was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment||Changeable using private API only || |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] |(/)| |ignite-direct-io|(x) blocked by indexing | | |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) org.apache.ignite.IgniteSpringBean affercted| |ignite-ml |(x) blocked by indexing | | > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment||Changeable using private API only || > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] |(/)| > |ignite-direct-io|(x) blocked by indexing | | > |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) > org.apache.ignite.IgniteSpringBean affected| > |ignite-ml |(x) blocked by indexing | | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Singh reassigned IGNITE-11312: Assignee: Suraj Singh > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11467) Support Automatic modules for ignite-spring: Move of classes to a separate package or jar
Dmitriy Pavlov created IGNITE-11467:
---
Summary: Support Automatic modules for ignite-spring: Move of
classes to a separate package or jar
Key: IGNITE-11467
URL: https://issues.apache.org/jira/browse/IGNITE-11467
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
Provided that [IGNITE-11464] is fixed and lucene is excluded from dependencies,
we still need refactor following packages to avoid packages conflicts:
{noformat}
error: the unnamed module reads package org.apache.ignite from both
ignite.spring and ignite.core
error: the unnamed module reads package org.apache.ignite.internal.util.spring
from both ignite.spring and ignite.core
error: the unnamed module reads package
org.apache.ignite.internal.processors.resource from both ignite.spring and
ignite.core
{noformat}
One from class in conflicting packages is org.apache.ignite.IgniteSpringBean,
which may be referenced outside of Ignite.
It mentioned at least here
http://qaru.site/questions/14880736/how-to-connect-apache-ignite-node-by-static-ip-address
with full class name:
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10583) MVCC: Assertion on txLog state update when recovering from WAL.
[
https://issues.apache.org/jira/browse/IGNITE-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov resolved IGNITE-10583.
---
Resolution: Duplicate
> MVCC: Assertion on txLog state update when recovering from WAL.
> ---
>
> Key: IGNITE-10583
> URL: https://issues.apache.org/jira/browse/IGNITE-10583
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: WAL, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Assertion in txLog state update occurs sporadically during recovery from WAL.
> Reproducer:
> {{IgnitePdsContinuousRestartTest#testRebalancingDuringLoad_10_10_1_1}} with
> enabled MVCC.
> Stacktrace:
> {noformat}
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on search row: TxKey [major=1544121790766, minor=10468]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1812)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.put(TxLog.java:245)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.updateState(MvccProcessorImpl.java:609)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLogicalUpdates(GridCacheDatabaseSharedManager.java:2456)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1934)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1050)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:961)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:902)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:890)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:856)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.checkRebalancingDuringLoad(IgnitePdsContinuousRestartTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_10_10_1_1(IgnitePdsContinuousRestartTest.java:221)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unexpected new transaction state.
> [currState=2, newState=3, cntr=10468]
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.invalid(TxLog.java:581)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.checkAborted(TxLog.java:562)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:451)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:393)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3755)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$5900(BPlusTree.java:3649)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1901)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1779)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10583) MVCC: Assertion on txLog state update when recovering from WAL.
[
https://issues.apache.org/jira/browse/IGNITE-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783372#comment-16783372
]
Andrew Mashenkov commented on IGNITE-10583:
---
Looks like issue has gone. I see no such failures on TC during last month.
> MVCC: Assertion on txLog state update when recovering from WAL.
> ---
>
> Key: IGNITE-10583
> URL: https://issues.apache.org/jira/browse/IGNITE-10583
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: WAL, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Assertion in txLog state update occurs sporadically during recovery from WAL.
> Reproducer:
> {{IgnitePdsContinuousRestartTest#testRebalancingDuringLoad_10_10_1_1}} with
> enabled MVCC.
> Stacktrace:
> {noformat}
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on search row: TxKey [major=1544121790766, minor=10468]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1812)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.put(TxLog.java:245)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.updateState(MvccProcessorImpl.java:609)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLogicalUpdates(GridCacheDatabaseSharedManager.java:2456)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1934)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1050)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:961)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:902)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:890)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:856)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.checkRebalancingDuringLoad(IgnitePdsContinuousRestartTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_10_10_1_1(IgnitePdsContinuousRestartTest.java:221)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unexpected new transaction state.
> [currState=2, newState=3, cntr=10468]
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.invalid(TxLog.java:581)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.checkAborted(TxLog.java:562)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:451)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:393)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3755)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$5900(BPlusTree.java:3649)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1901)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:17
[jira] [Created] (IGNITE-11466) MVCC: Remove irrelevant tests from mvcc suites.
Andrew Mashenkov created IGNITE-11466: - Summary: MVCC: Remove irrelevant tests from mvcc suites. Key: IGNITE-11466 URL: https://issues.apache.org/jira/browse/IGNITE-11466 Project: Ignite Issue Type: Test Components: mvcc Reporter: Andrew Mashenkov Fix For: 2.8 For now we have 300+ muted tests related to Mvcc support for LOCAL caches. As IGNITE-9530 has been closed with "wont fix" we have to # Cleanup code and remove test clones like IgniteCacheGroupsTest.testCacheIteratorMvccTxLocal # Add LOCAL cache test classes to ignore list in Mvcc suites. # Other tests should be disabled in Mvcc mode with Assumption and meaningful message. # All these tests should be unmuted on TC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8376) Add cluster (de)activation events
[
https://issues.apache.org/jira/browse/IGNITE-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Belyakov reassigned IGNITE-8376:
-
Assignee: Igor Belyakov
> Add cluster (de)activation events
> -
>
> Key: IGNITE-8376
> URL: https://issues.apache.org/jira/browse/IGNITE-8376
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Igor Belyakov
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
>
> Currently, we do not have any way to detect that a cluster got activated,
> which results in busy-loops polling {{cluster().active()}}.
> I suggest to add new events, {{EVT_CLUSTER_ACTIVATED}},
> {{EVT_CLUSTER_DEACTIVATED}}, {{EVT_CLUSTER_ACTIVATION_FAILED}} which will be
> fired when corresponding steps are completed. The event should contain, if
> possible, information about the activation source (public API or
> auto-activation), topology version on which activation was performed. The
> fail event should contain information about the cause of the failure. If
> needed, a new class for this event should be introduced.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9530) MVCC TX: Local caches support.
[ https://issues.apache.org/jira/browse/IGNITE-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9530: - Ignite Flags: (was: Docs Required) > MVCC TX: Local caches support. > -- > > Key: IGNITE-9530 > URL: https://issues.apache.org/jira/browse/IGNITE-9530 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Roman Kondakov >Priority: Major > > Mvcc support for local caches is turned off now. We need to consider > implementing it in the future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts
[
https://issues.apache.org/jira/browse/IGNITE-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11464:
Summary: Support Automatic modules for ignite-indexing: bypass or fix
Lucene, fix queries and visor package conflicts (was: Support Automatic
modules for ignite-indexing: bypass or fix H2, Lucene, fix queries and visor
package conflicts)
> Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix
> queries and visor package conflicts
>
>
> Key: IGNITE-11464
> URL: https://issues.apache.org/jira/browse/IGNITE-11464
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> {noformat}
> error: the unnamed module reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: the unnamed module reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: the unnamed module reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module ignite.indexing reads package org.apache.lucene.search from
> both lucene.sandbox and lucene.core
> error: module ignite.indexing reads package org.apache.lucene.document from
> both lucene.sandbox and lucene.core
> error: module ignite.indexing reads package
> org.apache.lucene.analysis.standard from both lucene.core and
> lucene.analyzers.common
> error: module ignite.indexing reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module ignite.indexing reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module cache.api reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module cache.api reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module cache.api reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module cache.api reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module cache.api reads package org.apache.ignite.internal.visor.verify
> from both ignite.indexing and ignite.core
> error: module annotations reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module annotations reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module annotations reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module annotations reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module annotations reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module ignite.shmem reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module ignite.shmem reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module ignite.shmem reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module ignite.shmem reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module ignite.shmem reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module org.apache.commons.codec reads package org.apache.lucene.search
> from both lucene.sandbox and lucene.core
> error: module org.apache.commons.codec reads package
> org.apache.lucene.document from both lucene.sandbox and lucene.core
> error: module org.apache.commons.codec reads package
> org.apache.lucene.analysis.standard from both lucene.core and
> lucene.analyzers.common
> error: module org.apache.commons.codec reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module org.apache.commons.codec reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module lucene.analyzers.common reads package org.apache.lucene.search
> from both lucene.sandbox and lucene.core
> error: module lucene.analyzers.common reads package
> org.apache.lucene.document from both lucene.sandbox a
[jira] [Comment Edited] (IGNITE-8178) ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
[
https://issues.apache.org/jira/browse/IGNITE-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783317#comment-16783317
]
Amelchev Nikita edited comment on IGNITE-8178 at 3/4/19 1:02 PM:
-
[~sergey-chugunov], Thanks for review!
[~dpavlov], Hi, could you help with a merge, please?
was (Author: nsamelchev):
[~sergey-chugunov], Thanks for review!
[~dpavlov], Hi, could you help with a merge?
> ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
> ---
>
> Key: IGNITE-8178
> URL: https://issues.apache.org/jira/browse/IGNITE-8178
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> The following stack trace appears in logs:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGridsMultiThreaded(GridAbstractTest.java:710)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:497)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectServersRestart(ZookeeperDiscoverySpiTest.java:3513)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testReconnectServersRestart_1(ZookeeperDiscoverySpiTest.java:3498)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:46237,127.0.0.1:38364,127.0.0.1:45674,
> joinTimeout=0, sesTimeout=1, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 24 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ign
[jira] [Updated] (IGNITE-9470) MVCC TX: Mvcc transactions should throw proper exception.
[
https://issues.apache.org/jira/browse/IGNITE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-9470:
-
Summary: MVCC TX: Mvcc transactions should throw proper exception. (was:
MVCC TX: Mvcc transactions should throw proper exception when rolled back.)
> MVCC TX: Mvcc transactions should throw proper exception.
> -
>
> Key: IGNITE-9470
> URL: https://issues.apache.org/jira/browse/IGNITE-9470
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, mvcc, odbc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: Muted_test, mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When MVCC transaction is rolled back due to a write conflict it throws
> {{CacheException}} with "Mvcc version mismatch" message. This behavior
> violates Ignite transactions API. Instead it should throw
> {{TransactionRollbackException}} with a clear message like a "Transaction has
> been aborted due to a write conflict (Please try again.)"
> It is also need to propogate this changes to JDBC and ODBC components and fix
> mvcc tests.
>
> In some tests we have to repeat tx operation in case of version conflict.
> Most likely, we can rely to caused-exception with some meaningful type (e.g.
> MvccVersionMismatchException) to repeat operation.
> Pay attention that tx could be aborted at different stages, but we should
> fail consistently. Some examples:
> 1. Before next operation in tx started.
> 2. While operation in tx is in progress.
> 3. When {{tx.commit()}} is called.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts
[
https://issues.apache.org/jira/browse/IGNITE-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783348#comment-16783348
]
Dmitriy Pavlov commented on IGNITE-11464:
-
Removal of Lucene dependency
{code}
compile(group: 'org.apache.ignite', name: 'ignite-indexing', version:
ignVer) {
exclude group: 'org.apache.lucene' // to remove "lucene-sandbox and
analyzers-commons" package conflicts.
}
{code}
helps to locate issues from automatic packages to following 3 issues:
- Lucene auto-packaging failed
- error: module ignite.indexing reads package
org.apache.ignite.internal.processors.cache.query from both ignite.core and
ignite.indexing
-- org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery
-- org.apache.ignite.internal.processors.cache.query.QueryTable
-- org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor
- error: module ignite.indexing reads package
org.apache.ignite.internal.visor.verify from both ignite.core and
ignite.indexing
-- org.apache.ignite.internal.visor.verify.ValidateIndexesClosure
-- org.apache.ignite.internal.visor.verify.VisorValidateIndexesTask
> Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix
> queries and visor package conflicts
>
>
> Key: IGNITE-11464
> URL: https://issues.apache.org/jira/browse/IGNITE-11464
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> {noformat}
> error: the unnamed module reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: the unnamed module reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: the unnamed module reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module ignite.indexing reads package org.apache.lucene.search from
> both lucene.sandbox and lucene.core
> error: module ignite.indexing reads package org.apache.lucene.document from
> both lucene.sandbox and lucene.core
> error: module ignite.indexing reads package
> org.apache.lucene.analysis.standard from both lucene.core and
> lucene.analyzers.common
> error: module ignite.indexing reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module ignite.indexing reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module cache.api reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module cache.api reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module cache.api reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module cache.api reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module cache.api reads package org.apache.ignite.internal.visor.verify
> from both ignite.indexing and ignite.core
> error: module annotations reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module annotations reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module annotations reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module annotations reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module annotations reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module ignite.shmem reads package org.apache.lucene.search from both
> lucene.sandbox and lucene.core
> error: module ignite.shmem reads package org.apache.lucene.document from both
> lucene.sandbox and lucene.core
> error: module ignite.shmem reads package org.apache.lucene.analysis.standard
> from both lucene.core and lucene.analyzers.common
> error: module ignite.shmem reads package
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing
> and ignite.core
> error: module ignite.shmem reads package
> org.apache.ignite.internal.visor.verify from both ignite.indexing and
> ignite.core
> error: module org.apache.commons.codec reads package org.apache.lucene.search
> from both lucene.sandbox and lucene.core
> error: module or
[jira] [Comment Edited] (IGNITE-11446) Common prefix for local node system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783345#comment-16783345 ] Yury Gerzhedovich edited comment on IGNITE-11446 at 3/4/19 12:35 PM: - [~vozerov], Vladimir, please review the trivial patch. Bot vise is in progress was (Author: jooger): [~vozerov], Vladimir, please review the trivial patch. > Common prefix for local node system SQL view > > > Key: IGNITE-11446 > URL: https://issues.apache.org/jira/browse/IGNITE-11446 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > All local views should have common prefix. Agreed on "LOCAL_". Now it affects > view CACHE_GROUPS_IO only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11446) Common prefix for local node system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783345#comment-16783345 ] Yury Gerzhedovich commented on IGNITE-11446: [~vozerov], Vladimir, please review the trivial patch. > Common prefix for local node system SQL view > > > Key: IGNITE-11446 > URL: https://issues.apache.org/jira/browse/IGNITE-11446 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > All local views should have common prefix. Agreed on "LOCAL_". Now it affects > view CACHE_GROUPS_IO only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | |ignite-ml |(x) blocked by indexing | was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) blocked by indexing | > |ignite-ml |(x) blocked by indexing | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11446) Common prefix for local node system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich reassigned IGNITE-11446: -- Assignee: Yury Gerzhedovich > Common prefix for local node system SQL view > > > Key: IGNITE-11446 > URL: https://issues.apache.org/jira/browse/IGNITE-11446 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > All local views should have common prefix. Agreed on "LOCAL_". Now it affects > view CACHE_GROUPS_IO only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
[ https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11461: Description: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) blocked by indexing | was: Example of failure in a modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io Ignite compatibility with Jigsaw is tested in a separate project. See details in https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project Currenly investigated modules to be used as automatic modules: ||Module||Run In Modular Environment|| |ignite-code|(/)| |ignite-indexing|(x) [IGNITE-11464] | |ignite-direct-io|(x) blocked by indexing | |ignite-spring|(x) | > Automatic modules support for Apache Ignite: find and resolve packages > conflicts > > > Key: IGNITE-11461 > URL: https://issues.apache.org/jira/browse/IGNITE-11461 > Project: Ignite > Issue Type: Improvement >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Example of failure in a modular environment: > Error:java: the unnamed module reads package > org.apache.ignite.internal.processors.cache.persistence.file from both > ignite.core and ignite.direct.io > Ignite compatibility with Jigsaw is tested in a separate project. See details > in > https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project > > Currenly investigated modules to be used as automatic modules: > ||Module||Run In Modular Environment|| > |ignite-code|(/)| > |ignite-indexing|(x) [IGNITE-11464] | > |ignite-direct-io|(x) blocked by indexing | > |ignite-spring|(x) blocked by indexing | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11277) Use maven plugin as default code style checker for project
[
https://issues.apache.org/jira/browse/IGNITE-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783319#comment-16783319
]
Andrew Mashenkov commented on IGNITE-11277:
---
I see TW-58504 is Fixed in TC version 2018.2.2 and we already have updated
version, but Inspection Core still failed.
Is there some another issue that should be fixed? Have someone investigate this?
> Use maven plugin as default code style checker for project
> --
>
> Key: IGNITE-11277
> URL: https://issues.apache.org/jira/browse/IGNITE-11277
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, {{[Inspections] Core suite}} [1] on TC doesn't work well enough.
> The suite has a {{FAILED}} status for more than 2 months due to some issues
> on TeamCity application [2]. It confuses most of the members of the Apache
> Ignite community.
> Moreover, this suite is no longer checks configured rules. For instance, in
> the master branch, 11 {{Unused imports}} can be found (e.g. for
> {{IgniteCachePutAllRestartTest}
> [3]).
> I think the maven-checkstyle-plugin should be used as the default code style
> checker.
> _Advantages:_
> * An IDE agnostic way for code checks
> * Can be used with different CI and build tools
> * Executable from the command line
> * Single configuration
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv
> [2] https://youtrack.jetbrains.com/issue/TW-58504
> [3]
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCachePutAllRestartTest.java#L29
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8178) ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
[
https://issues.apache.org/jira/browse/IGNITE-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783317#comment-16783317
]
Amelchev Nikita commented on IGNITE-8178:
-
[~sergey-chugunov], Thanks for review!
[~dpavlov], Hi, could you help with a merge?
> ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
> ---
>
> Key: IGNITE-8178
> URL: https://issues.apache.org/jira/browse/IGNITE-8178
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> The following stack trace appears in logs:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGridsMultiThreaded(GridAbstractTest.java:710)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:497)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectServersRestart(ZookeeperDiscoverySpiTest.java:3513)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testReconnectServersRestart_1(ZookeeperDiscoverySpiTest.java:3498)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:46237,127.0.0.1:38364,127.0.0.1:45674,
> joinTimeout=0, sesTimeout=1, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 24 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManag
[jira] [Updated] (IGNITE-11446) Common prefix for local node system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11446: --- Description: All local views should have common prefix. Agreed on "LOCAL_". Now it affects view CACHE_GROUPS_IO only. (was: All local views should have common prefix. Agreed on "NODE_". Affected view are CACHE_GROUPS_IO and LOCAL_SQL_RUNNING_QUERIES) > Common prefix for local node system SQL view > > > Key: IGNITE-11446 > URL: https://issues.apache.org/jira/browse/IGNITE-11446 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > All local views should have common prefix. Agreed on "LOCAL_". Now it affects > view CACHE_GROUPS_IO only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11453) SQL: command to work with permission must thrown clear exception witn UNSUPPORTED error code
[ https://issues.apache.org/jira/browse/IGNITE-11453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov resolved IGNITE-11453. --- Resolution: Duplicate The small trivial patch is a part of the patch IGNITE-7664 > SQL: command to work with permission must thrown clear exception witn > UNSUPPORTED error code > > > Key: IGNITE-11453 > URL: https://issues.apache.org/jira/browse/IGNITE-11453 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > > The command to work with permissions may produce confused error when Ignite > used with specified name is created. > These command must be disabled and throw exception witn UNSUPPORTED error > code: > - GRANT / REVOKE ON TO ; > - GRANT / REVOKE TO ; > - GRANT ALTER ANY SCHEMA ; -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8178) ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
[
https://issues.apache.org/jira/browse/IGNITE-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783313#comment-16783313
]
Sergey Chugunov commented on IGNITE-8178:
-
[~NSAmelchev],
I verified your change, it looks good to me, also don't see any regression from
TC test report.
Please proceed with merging.
Thank you for contribution!
> ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
> ---
>
> Key: IGNITE-8178
> URL: https://issues.apache.org/jira/browse/IGNITE-8178
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> The following stack trace appears in logs:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGridsMultiThreaded(GridAbstractTest.java:710)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:497)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectServersRestart(ZookeeperDiscoverySpiTest.java:3513)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testReconnectServersRestart_1(ZookeeperDiscoverySpiTest.java:3498)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:46237,127.0.0.1:38364,127.0.0.1:45674,
> joinTimeout=0, sesTimeout=1, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 24 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
[jira] [Commented] (IGNITE-11446) Common prefix for local node system SQL view
[ https://issues.apache.org/jira/browse/IGNITE-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783310#comment-16783310 ] Yury Gerzhedovich commented on IGNITE-11446: [~alex_pl], Yes, you are right, it has been fast and not deep investigate what we already have. Now we will use "LOCAL_" prefix for local views. > Common prefix for local node system SQL view > > > Key: IGNITE-11446 > URL: https://issues.apache.org/jira/browse/IGNITE-11446 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > All local views should have common prefix. Agreed on "NODE_". Affected view > are CACHE_GROUPS_IO and LOCAL_SQL_RUNNING_QUERIES -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11450) SQL: HELP and SHOW commands must throw clear exception with UNSUPPORTED error code
[ https://issues.apache.org/jira/browse/IGNITE-11450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov resolved IGNITE-11450. --- Resolution: Duplicate The small patch is a part of the patch IGNITE-7664 > SQL: HELP and SHOW commands must throw clear exception with UNSUPPORTED error > code > -- > > Key: IGNITE-11450 > URL: https://issues.apache.org/jira/browse/IGNITE-11450 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > > SQL command SHOW SCHEMAS / TABLES / COLUMNS don't work properly. They must > throw exception with UNSUPPORTED error code. > SQL command HELP must be disabled and throw exception with UNSUPPORTED error > code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10161) Be able to cancel any query by query id
[
https://issues.apache.org/jira/browse/IGNITE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783287#comment-16783287
]
Yury Gerzhedovich edited comment on IGNITE-10161 at 3/4/19 11:44 AM:
-
[~vozerov],
1,2 - done
3,4 - separated tickets have been created:
https://issues.apache.org/jira/browse/IGNITE-11452,
https://issues.apache.org/jira/browse/IGNITE-11456
waiting a Bot vise
was (Author: jooger):
[~vozerov],
1,2 - done
3,4 - separated tickets have been created:
https://issues.apache.org/jira/browse/IGNITE-11452,
https://issues.apache.org/jira/browse/IGNITE-11456
> Be able to cancel any query by query id
> ---
>
> Key: IGNITE-10161
> URL: https://issues.apache.org/jira/browse/IGNITE-10161
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User should be able to cancel any query by query id through SQL command.
> SQL syntax: *KILL QUERY '<_query_id>' \{ASYNC}_*
> _ASYNC_ is optional parameter which return control immediately without
> waiting real cancellation will be done.
> By default, without ASYNC parameter, the request is blocking untill
> cancellation is not done.
> Query should be canceled together with its parts on all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10161) Be able to cancel any query by query id
[
https://issues.apache.org/jira/browse/IGNITE-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783287#comment-16783287
]
Yury Gerzhedovich commented on IGNITE-10161:
[~vozerov],
1,2 - done
3,4 - separated tickets have been created:
https://issues.apache.org/jira/browse/IGNITE-11452,
https://issues.apache.org/jira/browse/IGNITE-11456
> Be able to cancel any query by query id
> ---
>
> Key: IGNITE-10161
> URL: https://issues.apache.org/jira/browse/IGNITE-10161
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> User should be able to cancel any query by query id through SQL command.
> SQL syntax: *KILL QUERY '<_query_id>' \{ASYNC}_*
> _ASYNC_ is optional parameter which return control immediately without
> waiting real cancellation will be done.
> By default, without ASYNC parameter, the request is blocking untill
> cancellation is not done.
> Query should be canceled together with its parts on all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11364) Segmenting node can cause ring topology broke
[
https://issues.apache.org/jira/browse/IGNITE-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783197#comment-16783197
]
Ignite TC Bot commented on IGNITE-11364:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3211378&buildTypeId=IgniteTests24Java8_RunAll]
> Segmenting node can cause ring topology broke
> -
>
> Key: IGNITE-11364
> URL: https://issues.apache.org/jira/browse/IGNITE-11364
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5, 2.6, 2.7
>Reporter: Ivan Daschinskiy
>Assignee: Sergey Chugunov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While segmenting by partial network drop, i.e. by applying iptables rules,
> can cause ring broke.
> Scenario:
> On each machine there are two nodes, client and server respectivelly.
> Lets draw diagram (only server nodes for brevity, they have been started
> before clients).
> => grid915 => ... => grid947 => grid945 => grid703 => ..skip 12
> nodes...=> grid952 => grid946.
> On grid945 machine we drop incoming/outgoing connections by iptables.
> During ongoing drop of connection, grid945 send
> TcpDiscoveryStatusCheckMessage, but cannot send them to grid703 and others
> mentioned above 12 nodes, but some next node accepted it with collection of
> failedNodes (13 nodes above). This message was received by grid947 and it
> skip these 13 nodes in
> org.apache.ignite.spi.discovery.tcp.ServerImpl.RingMessageWorker#sendMessageAcrossRing.
> So we see this situation in topology:
> .. => grid947 => grid952=>..
> //
> grid703=>=>grid662
> Mentioned above nodes are not considered by grid as failed, so we see
> topology as tail connected to ring.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11462) MVCC: Fix GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.
[ https://issues.apache.org/jira/browse/IGNITE-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783186#comment-16783186 ] Ivan Pavlukhin commented on IGNITE-11462: - [~amashenkov], thank you! Looks good. > MVCC: Fix GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest. > -- > > Key: IGNITE-11462 > URL: https://issues.apache.org/jira/browse/IGNITE-11462 > Project: Ignite > Issue Type: Test > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > Next tests failed on TC: > GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.testPessimisticRepeatableReadCommitMultithreaded > GridCacheReplicatedMvccTxMultiThreadedSelfTest.testPessimisticRepeatableReadCommitMultithreaded > > Seems, retry on write conflict is missed in test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11462) MVCC: Fix GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.
[ https://issues.apache.org/jira/browse/IGNITE-11462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783182#comment-16783182 ] Andrew Mashenkov commented on IGNITE-11462: --- [~Pavlukhin], thanks, you are right. I've fixed exception type and tests pass on TC. > MVCC: Fix GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest. > -- > > Key: IGNITE-11462 > URL: https://issues.apache.org/jira/browse/IGNITE-11462 > Project: Ignite > Issue Type: Test > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > Next tests failed on TC: > GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.testPessimisticRepeatableReadCommitMultithreaded > GridCacheReplicatedMvccTxMultiThreadedSelfTest.testPessimisticRepeatableReadCommitMultithreaded > > Seems, retry on write conflict is missed in test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10583) MVCC: Assertion on txLog state update when recovering from WAL.
[
https://issues.apache.org/jira/browse/IGNITE-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov reassigned IGNITE-10583:
-
Assignee: Andrew Mashenkov
> MVCC: Assertion on txLog state update when recovering from WAL.
> ---
>
> Key: IGNITE-10583
> URL: https://issues.apache.org/jira/browse/IGNITE-10583
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: WAL, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Assertion in txLog state update occurs sporadically during recovery from WAL.
> Reproducer:
> {{IgnitePdsContinuousRestartTest#testRebalancingDuringLoad_10_10_1_1}} with
> enabled MVCC.
> Stacktrace:
> {noformat}
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on search row: TxKey [major=1544121790766, minor=10468]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1812)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.put(TxLog.java:245)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.updateState(MvccProcessorImpl.java:609)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLogicalUpdates(GridCacheDatabaseSharedManager.java:2456)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1934)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1050)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:961)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:902)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:890)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:856)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.checkRebalancingDuringLoad(IgnitePdsContinuousRestartTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_10_10_1_1(IgnitePdsContinuousRestartTest.java:221)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unexpected new transaction state.
> [currState=2, newState=3, cntr=10468]
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.invalid(TxLog.java:581)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.checkAborted(TxLog.java:562)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:451)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:393)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3755)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$5900(BPlusTree.java:3649)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1901)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1779)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#7600
[jira] [Commented] (IGNITE-10991) JDBC thin: STREAMING mode fails on streamer reopen on not ordered mode
[
https://issues.apache.org/jira/browse/IGNITE-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783167#comment-16783167
]
Taras Ledkov commented on IGNITE-10991:
---
[~vozerov], because It is possible that the queue dosn't contain the request
with expected order.
In this case we can do {{poll / add}} to return the request to queue or do
{{peek / poll}} and poll only expected message.
> JDBC thin: STREAMING mode fails on streamer reopen on not ordered mode
> --
>
> Key: IGNITE-10991
> URL: https://issues.apache.org/jira/browse/IGNITE-10991
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.8
>
> Attachments: CacheSqlStreamingAllowOverwriteTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached test. Repeatedly overwriting same cache entries over and
> over in streaming mode with ALLOW_OVERWRITE ON will cause either:
> {code}
> java.sql.BatchUpdateException: Failed to INSERT some keys because they are
> already in cache [keys=[2054...]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1052)
> ... 1 more
> {code}
> or
> {code}
> WARNING: Exception during batch send on streamed connection close
> java.sql.BatchUpdateException: class
> org.apache.ignite.IgniteCheckedException: Data streamer has been closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1016)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Expecter behavior - no failures, all records overwritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10693) MVCC TX: Random server restart tests became failed
[ https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-10693: - Assignee: Andrew Mashenkov (was: Igor Seliverstov) > MVCC TX: Random server restart tests became failed > -- > > Key: IGNITE-10693 > URL: https://issues.apache.org/jira/browse/IGNITE-10693 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Igor Seliverstov >Assignee: Andrew Mashenkov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > [one|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7945125576049372508&branch=%3Cdefault%3E&tab=testDetails], > > [two|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=8412476034648229784&branch=%3Cdefault%3E&tab=testDetails], > > [three|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=254244004184327163&branch=%3Cdefault%3E&tab=testDetails], > all these tests became failed after IGNITE-9630 has been merged to master. > Seems there is an issue in partition calculating mechanism on unstable > topology. I suppose the algorithm uses partitions on nodes just become > primary while the partitions are in moving state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10991) JDBC thin: STREAMING mode fails on streamer reopen on not ordered mode
[
https://issues.apache.org/jira/browse/IGNITE-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783140#comment-16783140
]
Vladimir Ozerov commented on IGNITE-10991:
--
[~tledkov-gridgain], looks good to me in general, but I am not quite understand
{{JdbcRequestHandler.OrderedBatchWorker#body}} method: why do we do {{peek}}
and then make {{poll}}? Can we just make one {{poll}} instead?
> JDBC thin: STREAMING mode fails on streamer reopen on not ordered mode
> --
>
> Key: IGNITE-10991
> URL: https://issues.apache.org/jira/browse/IGNITE-10991
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.8
>
> Attachments: CacheSqlStreamingAllowOverwriteTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached test. Repeatedly overwriting same cache entries over and
> over in streaming mode with ALLOW_OVERWRITE ON will cause either:
> {code}
> java.sql.BatchUpdateException: Failed to INSERT some keys because they are
> already in cache [keys=[2054...]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1052)
> ... 1 more
> {code}
> or
> {code}
> WARNING: Exception during batch send on streamed connection close
> java.sql.BatchUpdateException: class
> org.apache.ignite.IgniteCheckedException: Data streamer has been closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1016)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Expecter behavior - no failures, all records overwritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9913) Prevent data updates blocking in case of backup BLT server node leave
[ https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita reassigned IGNITE-9913: --- Assignee: Amelchev Nikita (was: Ivan Rakov) > Prevent data updates blocking in case of backup BLT server node leave > - > > Key: IGNITE-9913 > URL: https://issues.apache.org/jira/browse/IGNITE-9913 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ivan Rakov >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.8 > > > Ignite cluster performs distributed partition map exchange when any server > node leaves or joins the topology. > Distributed PME blocks all updates and may take a long time. If all > partitions are assigned according to the baseline topology and server node > leaves, there's no actual need to perform distributed PME: every cluster node > is able to recalculate new affinity assigments and partition states locally. > If we'll implement such lightweight PME and handle mapping and lock requests > on new topology version correctly, updates won't be stopped (except updates > of partitions that lost their primary copy). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11465) Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
[
https://issues.apache.org/jira/browse/IGNITE-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783102#comment-16783102
]
Ivan Rakov commented on IGNITE-11465:
-
Possible new TC failures appeared, investigating.
> Multiple client leave/join events may wipe affinity assignment history and
> cause transactions fail
> --
>
> Key: IGNITE-11465
> URL: https://issues.apache.org/jira/browse/IGNITE-11465
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We keep history of GridAffinityAssignmentCache#MAX_HIST_SIZE affinity
> assignments. However, flood of client joins/leaves may wipe it out entirely
> and cause fail/hang of transaction that was started before the flood due to
> the following exception:
> {code:java}
> if (cache == null || cache.topologyVersion().compareTo(topVer) >
> 0) {
> throw new IllegalStateException("Getting affinity for
> topology version earlier than affinity is " +
> "calculated [locNode=" + ctx.discovery().localNode() +
> ", grp=" + cacheOrGrpName +
> ", topVer=" + topVer +
> ", head=" + head.get().topologyVersion() +
> ", history=" + affCache.keySet() +
> ']');
> }
> {code}
> History is limited in order to prevent JVM heap overflow. At the same time,
> only "server event" affinity assignments are heavy: "client event"
> assignments are just shallow copies of "server event" assignments.
> I suggest to limit history by the number of "server event" assignments.
> Also, considering the provided fix, I don't see any need to keep 500 items in
> history. I propose to change history size to 50.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11465) Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
[
https://issues.apache.org/jira/browse/IGNITE-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783099#comment-16783099
]
Alexei Scherbakov commented on IGNITE-11465:
[~ivan.glukos],
I consider changing default value to 50 risky because we still can have history
overflow due to massive not batched dynamic cache operations. Backward
compatibility could be broken as well in such scenarios.
Default value looks OK especially after IGNITE-10920 optimization.
Otherwise looks good.
> Multiple client leave/join events may wipe affinity assignment history and
> cause transactions fail
> --
>
> Key: IGNITE-11465
> URL: https://issues.apache.org/jira/browse/IGNITE-11465
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We keep history of GridAffinityAssignmentCache#MAX_HIST_SIZE affinity
> assignments. However, flood of client joins/leaves may wipe it out entirely
> and cause fail/hang of transaction that was started before the flood due to
> the following exception:
> {code:java}
> if (cache == null || cache.topologyVersion().compareTo(topVer) >
> 0) {
> throw new IllegalStateException("Getting affinity for
> topology version earlier than affinity is " +
> "calculated [locNode=" + ctx.discovery().localNode() +
> ", grp=" + cacheOrGrpName +
> ", topVer=" + topVer +
> ", head=" + head.get().topologyVersion() +
> ", history=" + affCache.keySet() +
> ']');
> }
> {code}
> History is limited in order to prevent JVM heap overflow. At the same time,
> only "server event" affinity assignments are heavy: "client event"
> assignments are just shallow copies of "server event" assignments.
> I suggest to limit history by the number of "server event" assignments.
> Also, considering the provided fix, I don't see any need to keep 500 items in
> history. I propose to change history size to 50.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11465) Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
[
https://issues.apache.org/jira/browse/IGNITE-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783097#comment-16783097
]
Sergey Antonov commented on IGNITE-11465:
-
[~ivan.glukos] Changes looks good for me! Please, create ticket for update
documentation about new default value of {{IGNITE_AFFINITY_HISTORY_SIZE}}
property.
> Multiple client leave/join events may wipe affinity assignment history and
> cause transactions fail
> --
>
> Key: IGNITE-11465
> URL: https://issues.apache.org/jira/browse/IGNITE-11465
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We keep history of GridAffinityAssignmentCache#MAX_HIST_SIZE affinity
> assignments. However, flood of client joins/leaves may wipe it out entirely
> and cause fail/hang of transaction that was started before the flood due to
> the following exception:
> {code:java}
> if (cache == null || cache.topologyVersion().compareTo(topVer) >
> 0) {
> throw new IllegalStateException("Getting affinity for
> topology version earlier than affinity is " +
> "calculated [locNode=" + ctx.discovery().localNode() +
> ", grp=" + cacheOrGrpName +
> ", topVer=" + topVer +
> ", head=" + head.get().topologyVersion() +
> ", history=" + affCache.keySet() +
> ']');
> }
> {code}
> History is limited in order to prevent JVM heap overflow. At the same time,
> only "server event" affinity assignments are heavy: "client event"
> assignments are just shallow copies of "server event" assignments.
> I suggest to limit history by the number of "server event" assignments.
> Also, considering the provided fix, I don't see any need to keep 500 items in
> history. I propose to change history size to 50.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11215) MVCC: JVM crash in MVCC PDS 1 suite
[
https://issues.apache.org/jira/browse/IGNITE-11215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-11215:
Description:
Sometimes JVM crash
[occurs|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeHistoryList&state=failed]
in {{vacuum-cleaner}} thread in {{ExplicitWalDeltaConsistencyTest}}.
See attached crash report.
was:
Sometimes JVM crush
[occurs|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeHistoryList&state=failed]
in {{vacuum-cleaner}} thread in {{ExplicitWalDeltaConsistencyTest}}.
See attached crush report.
> MVCC: JVM crash in MVCC PDS 1 suite
> ---
>
> Key: IGNITE-11215
> URL: https://issues.apache.org/jira/browse/IGNITE-11215
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Critical
> Labels: mvcc_stabilization_stage_1
> Attachments: hs_err_pid429215.log
>
>
> Sometimes JVM crash
> [occurs|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds1&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeHistoryList&state=failed]
> in {{vacuum-cleaner}} thread in {{ExplicitWalDeltaConsistencyTest}}.
> See attached crash report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
