[jira] [Commented] (IGNITE-6587) Ignite watchdog service
[
https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799408#comment-16799408
]
Ignite TC Bot commented on IGNITE-6587:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386454]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386456]]
{color:#d04437}Client Nodes{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386458]]
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 Exit Code , Failure
on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3386476]]
{color:#d04437}Thin client: PHP{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386482]]
{color:#d04437}Hibernate 5.3{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386484]]
{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386486]]
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386492]]
{color:#d04437}Spring (Data){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3386496]]
{color:#d04437}Queries 1{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=3386460]]
* IgniteBinaryCacheQueryTestSuite:
SchemaExchangeSelfTest.testServerRestartWithNewTypes - 0,0% fails in last 422
master runs.
{color:#d04437}Cache 1{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=3386462]]
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testTwoClientsAllowOverwrite
- 0,0% fails in last 419 master runs.
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testOneClientAllowOverwrite
- 0,0% fails in last 419 master runs.
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testTwoClients - 0,0% fails
in last 419 master runs.
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testOneClient - 0,0% fails
in last 419 master runs.
{color:#d04437}PDS (Indexing){color} [[tests 3 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3386464]]
* IgnitePdsWithIndexingCoreTestSuite:
IgniteLogicalRecoveryTest.testRecoveryOnDynamicallyStartedCaches - 0,0% fails
in last 414 master runs.
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite - 0,0% fails in last
414 master runs.
{color:#d04437}Cache 3{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3386466]]
* IgniteBinaryObjectsCacheTestSuite3:
CacheMetricsManageTest.testJmxPdsStatisticsEnable
* IgniteBinaryObjectsCacheTestSuite3:
CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime
{color:#d04437}Queries 2{color} [[tests
13|https://ci.ignite.apache.org/viewLog.html?buildId=3386468]]
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalReplicatedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
IgniteCacheQueryNodeRestartSelfTest2.testRestarts - 0,0% fails in last 0 master
runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testClientReconnectWithNonDynamicCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicPartitionedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIndexPartitionedTransactionalConcurrentSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testClientReconnectWithNonDynamicCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIndexPartitionedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalReplicatedSelfTest.testClientReconnectWithNonDynamicCacheRestart
- 0,0% fails in last 426 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIndexReplicatedTransactionalConcurrentSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last
[jira] [Commented] (IGNITE-11587) MVCC: Remote tx determine its type in wrong way.
[
https://issues.apache.org/jira/browse/IGNITE-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799372#comment-16799372
]
Ignite TC Bot commented on IGNITE-11587:
{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=3371795buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Remote tx determine its type in wrong way.
> -
>
> Key: IGNITE-11587
> URL: https://issues.apache.org/jira/browse/IGNITE-11587
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Remote tx adapters implements IgniteTxState.mvccEnabled in wrong way.
> mvccEnabled() checks if writeMap contains a mvcc-entry, but writeMap is
> always empty for mvcc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799336#comment-16799336
]
Ignite TC Bot commented on IGNITE-11600:
{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=3384964buildTypeId=IgniteTests24Java8_RunAll]
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799255#comment-16799255
]
Ivan Rakov commented on IGNITE-11591:
-
Let's extend logging added in IGNITE-11059. I propose to:
1) Dump pending locks info for every timed out transaction, but for
transactions with timeout less than minute add throttling based on
HitRateMetrics (e.g. print no more than 10 messages per minute)
2) Make messages rate configurable and changeable in runtime (we can add new
method for this - something like TransactionsMXBean#setPendingLocksMessageRate).
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or
[jira] [Reopened] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov reopened IGNITE-11591:
-
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or information about all
> transactions that are ahead in queue if there are several).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-1436) C++: Port to MAC OS.
[ https://issues.apache.org/jira/browse/IGNITE-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799213#comment-16799213 ] Stephen Darlington commented on IGNITE-1436: [~isapego], updated version force-pushed to my branch. I updated the documentation so _hopefully_ enough for you to get started. > C++: Port to MAC OS. > > > Key: IGNITE-1436 > URL: https://issues.apache.org/jira/browse/IGNITE-1436 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Stephen Darlington >Priority: Major > Labels: cpp > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > It will require minimal porting of "common" and "utils" stuff. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11614) Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely
Anton Kurbanov created IGNITE-11614: --- Summary: Transaction with timeout on cache with near configuration hangs after cache store failure indefinitely Key: IGNITE-11614 URL: https://issues.apache.org/jira/browse/IGNITE-11614 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Anton Kurbanov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11436) sqlline is not working on Java 9+
[
https://issues.apache.org/jira/browse/IGNITE-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799161#comment-16799161
]
Dmitriy Pavlov commented on IGNITE-11436:
-
Cherry-picked to 2.7.5
> sqlline is not working on Java 9+
> -
>
> Key: IGNITE-11436
> URL: https://issues.apache.org/jira/browse/IGNITE-11436
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
>
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/var/lib/teamcity/data/work/ead1d0aeaa1f7813/i2test/var/suite-client/art-gg-pro/libs/ignite-core-2.7.2-p1.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
> at org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.loadConfiguration(JdbcConnection.java:323)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.getIgnite(JdbcConnection.java:295)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.(JdbcConnection.java:229)
> at org.apache.ignite.IgniteJdbcDriver.connect(IgniteJdbcDriver.java:437)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:156)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11436) sqlline is not working on Java 9+
[
https://issues.apache.org/jira/browse/IGNITE-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11436:
Fix Version/s: 2.7.5
> sqlline is not working on Java 9+
> -
>
> Key: IGNITE-11436
> URL: https://issues.apache.org/jira/browse/IGNITE-11436
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
>
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/var/lib/teamcity/data/work/ead1d0aeaa1f7813/i2test/var/suite-client/art-gg-pro/libs/ignite-core-2.7.2-p1.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
> at org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.loadConfiguration(JdbcConnection.java:323)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.getIgnite(JdbcConnection.java:295)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.(JdbcConnection.java:229)
> at org.apache.ignite.IgniteJdbcDriver.connect(IgniteJdbcDriver.java:437)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:156)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11436) sqlline is not working on Java 9+
[
https://issues.apache.org/jira/browse/IGNITE-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11436:
Labels: important (was: )
> sqlline is not working on Java 9+
> -
>
> Key: IGNITE-11436
> URL: https://issues.apache.org/jira/browse/IGNITE-11436
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: important
> Fix For: 2.8
>
>
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/var/lib/teamcity/data/work/ead1d0aeaa1f7813/i2test/var/suite-client/art-gg-pro/libs/ignite-core-2.7.2-p1.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
> at org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.loadConfiguration(JdbcConnection.java:323)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.getIgnite(JdbcConnection.java:295)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.(JdbcConnection.java:229)
> at org.apache.ignite.IgniteJdbcDriver.connect(IgniteJdbcDriver.java:437)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:156)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799137#comment-16799137 ] Peter Ivanov commented on IGNITE-11600: --- PR looks good to me. > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.8, 2.7.5 > > Time Spent: 0.5h > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
[ https://issues.apache.org/jira/browse/IGNITE-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11613: -- Fix Version/s: 2.8 > GridSpringBeanSerializationSelfTest fails in master > --- > > Key: IGNITE-11613 > URL: https://issues.apache.org/jira/browse/IGNITE-11613 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > From the logs it's clear that the test fails because the node being started > picks up some other nodes through multicast and fails because of an > incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
[ https://issues.apache.org/jira/browse/IGNITE-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-11613. --- Resolution: Fixed > GridSpringBeanSerializationSelfTest fails in master > --- > > Key: IGNITE-11613 > URL: https://issues.apache.org/jira/browse/IGNITE-11613 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 20m > Remaining Estimate: 0h > > From the logs it's clear that the test fails because the node being started > picks up some other nodes through multicast and fails because of an > incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11612) http.GridHttpDeploymentSelfTest always fails
[ https://issues.apache.org/jira/browse/IGNITE-11612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799103#comment-16799103 ] Ivan Bessonov commented on IGNITE-11612: Successful run: [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy_IgniteTests24Java8=pull%2F6328%2Fhead=buildTypeStatusDiv] > http.GridHttpDeploymentSelfTest always fails > > > Key: IGNITE-11612 > URL: https://issues.apache.org/jira/browse/IGNITE-11612 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8313984068492573325=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
Alexey Goncharuk created IGNITE-11613: - Summary: GridSpringBeanSerializationSelfTest fails in master Key: IGNITE-11613 URL: https://issues.apache.org/jira/browse/IGNITE-11613 Project: Ignite Issue Type: Test Reporter: Alexey Goncharuk >From the logs it's clear that the test fails because the node being started >picks up some other nodes through multicast and fails because of an >incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
[ https://issues.apache.org/jira/browse/IGNITE-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11613: -- Labels: MakeTeamcityGreenAgain (was: ) > GridSpringBeanSerializationSelfTest fails in master > --- > > Key: IGNITE-11613 > URL: https://issues.apache.org/jira/browse/IGNITE-11613 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > > From the logs it's clear that the test fails because the node being started > picks up some other nodes through multicast and fails because of an > incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
[ https://issues.apache.org/jira/browse/IGNITE-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11613: -- Ignite Flags: (was: Docs Required) > GridSpringBeanSerializationSelfTest fails in master > --- > > Key: IGNITE-11613 > URL: https://issues.apache.org/jira/browse/IGNITE-11613 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Priority: Major > > From the logs it's clear that the test fails because the node being started > picks up some other nodes through multicast and fails because of an > incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11613) GridSpringBeanSerializationSelfTest fails in master
[ https://issues.apache.org/jira/browse/IGNITE-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11613: - Assignee: Alexey Goncharuk > GridSpringBeanSerializationSelfTest fails in master > --- > > Key: IGNITE-11613 > URL: https://issues.apache.org/jira/browse/IGNITE-11613 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > > From the logs it's clear that the test fails because the node being started > picks up some other nodes through multicast and fails because of an > incompatible configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11612) http.GridHttpDeploymentSelfTest always fails
[ https://issues.apache.org/jira/browse/IGNITE-11612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-11612: --- Labels: MakeTeamcityGreenAgain (was: ) > http.GridHttpDeploymentSelfTest always fails > > > Key: IGNITE-11612 > URL: https://issues.apache.org/jira/browse/IGNITE-11612 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8313984068492573325=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11612) http.GridHttpDeploymentSelfTest always fails
Ivan Bessonov created IGNITE-11612: -- Summary: http.GridHttpDeploymentSelfTest always fails Key: IGNITE-11612 URL: https://issues.apache.org/jira/browse/IGNITE-11612 Project: Ignite Issue Type: Test Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.8 [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8313984068492573325=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Labels: important (was: )
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11611) If partition cannot be recovered during rebalance it should be moved to LOST state.
Alexei Scherbakov created IGNITE-11611: -- Summary: If partition cannot be recovered during rebalance it should be moved to LOST state. Key: IGNITE-11611 URL: https://issues.apache.org/jira/browse/IGNITE-11611 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11153:
Labels: important (was: )
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --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 \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --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 \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--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-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11153:
Fix Version/s: 2.7.5
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --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 \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --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 \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--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-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11610) Add note to the DROP TABLE doc that it can be used only for table created with DDL
Evgenii Zhuravlev created IGNITE-11610: -- Summary: Add note to the DROP TABLE doc that it can be used only for table created with DDL Key: IGNITE-11610 URL: https://issues.apache.org/jira/browse/IGNITE-11610 Project: Ignite Issue Type: Bug Components: documentation Reporter: Evgenii Zhuravlev Assignee: Artem Budnikov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11216:
Labels: important (was: )
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11595:
Labels: (was: important)
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8, 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11233:
Fix Version/s: 2.7.5
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.8, 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc=ignite-11213=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy=ignite-11213=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd=ignite-11213=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11=ignite-11213=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
> uses or overrides a deprecated API that is marked for removal.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
> Recompile with -Xlint:removal for details.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
> uses unchecked or unsafe operations.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
> Recompile with -Xlint:unchecked for details.
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
> package com.sun.tools.doclets does not exist
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[30,42]
> cannot find symbol
> [21:28:32][Step 1/1] symbol: class Taglet
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[37,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[44,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[51,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[58,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[65,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[72,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
>
[jira] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Fix Version/s: 2.7.5
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8, 2.7.5
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799056#comment-16799056
]
Dmitriy Pavlov commented on IGNITE-11155:
-
Cherry-picked to 2.7.5
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8, 2.7.5
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11609) Add support of authentication and SSL in yardstick IgniteThinClient benchmark
Dmitry Sherstobitov created IGNITE-11609: Summary: Add support of authentication and SSL in yardstick IgniteThinClient benchmark Key: IGNITE-11609 URL: https://issues.apache.org/jira/browse/IGNITE-11609 Project: Ignite Issue Type: New Feature Affects Versions: 2.7 Reporter: Dmitry Sherstobitov Fix For: 2.8 Add support of following keys: Mandatory authentication: USER PASSWORD Mandatory SSL: SSL_KEY_PASSWORD SSL_KEY_PATH Optional SSL: SSL_CLIENT_STORE_TYPE (default JKS) SSL_SERVER_STORE_TYPE (default JKS) SSL_KEY_ALGORITHM (default SunX509) SSL_TRUST_ALL (default false) SSL_PROTOCOL (default TLS) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11569) Enable baseline auto-adjust by default only for empty cluster
[ https://issues.apache.org/jira/browse/IGNITE-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-11569: Fix Version/s: 2.8 > Enable baseline auto-adjust by default only for empty cluster > - > > Key: IGNITE-11569 > URL: https://issues.apache.org/jira/browse/IGNITE-11569 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > It is required to enable baseline auto-adjust by default only for empty > cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799039#comment-16799039
]
Dmitriy Pavlov commented on IGNITE-11595:
-
[~Pavlukhin], [~vveider] thank you for review and contribution, merged to
master and cherry-picked to 2.7.5.
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11608) Document static persistent caches and DDL behavior
[ https://issues.apache.org/jira/browse/IGNITE-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11608: -- Ignite Flags: (was: Docs Required) > Document static persistent caches and DDL behavior > -- > > Key: IGNITE-11608 > URL: https://issues.apache.org/jira/browse/IGNITE-11608 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > > In IGNITE-11541 we changed the logic to ignore static cache configuration in > favor of persisted cache config because the old behavior was incorrect in > regards with DDL. A system property was introduced to keep the old behavior. > These changes should be documented in > https://apacheignite.readme.io/docs/cache-configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11608) Document static persistent caches and DDL behavior
Alexey Goncharuk created IGNITE-11608: - Summary: Document static persistent caches and DDL behavior Key: IGNITE-11608 URL: https://issues.apache.org/jira/browse/IGNITE-11608 Project: Ignite Issue Type: Task Components: documentation Reporter: Alexey Goncharuk In IGNITE-11541 we changed the logic to ignore static cache configuration in favor of persisted cache config because the old behavior was incorrect in regards with DDL. A system property was introduced to keep the old behavior. These changes should be documented in https://apacheignite.readme.io/docs/cache-configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799025#comment-16799025
]
Ivan Pavlukhin commented on IGNITE-11595:
-
[~vveider], everything looks good, thank you!
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11541) Dynamic columns and indexes can be lost after the cluster restart
[ https://issues.apache.org/jira/browse/IGNITE-11541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799022#comment-16799022 ] Alexey Goncharuk commented on IGNITE-11541: --- Suggested solution is to ignore static cache configuration for persistent caches. At the same time I introduced an additional system property to keep the old behavior. When this property is set, DDL operations over static persistent caches are forbidden because it may lead to index corruption. > Dynamic columns and indexes can be lost after the cluster restart > - > > Key: IGNITE-11541 > URL: https://issues.apache.org/jira/browse/IGNITE-11541 > Project: Ignite > Issue Type: Bug > Components: cache, persistence, sql >Affects Versions: 2.7 >Reporter: Roman Guseinov >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > Attachments: StaticCacheAndDdlReproducer.java > > Time Spent: 10m > Remaining Estimate: 0h > > The case is the following: > # Run a server node (persistence enabled. static cache configuration with > queryEnities). > # Add/drop column/index via DDL. > # Restart the node with the same configuration. > # The changes are lost... > It seems the issue is related to merging cache metadata. > There are some workarounds: > # Remove/comment cache configuration. After the restart, the metadata will be > loaded from the persistence store. This will work for a rolling restart. > # Make the same changes in the configuration (update queryEntity). It > requires the whole cluster restart. > Reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11598) Add possibility to have different rebalance thread pool size for nodes in the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-11598: --- Summary: Add possibility to have different rebalance thread pool size for nodes in the cluster (was: Add possibility to have different rebalance thread pool size for nodes in cluster) > Add possibility to have different rebalance thread pool size for nodes in the > cluster > - > > Key: IGNITE-11598 > URL: https://issues.apache.org/jira/browse/IGNITE-11598 > Project: Ignite > Issue Type: Improvement >Reporter: Evgenii Zhuravlev >Priority: Major > > It can be used for changing this property without downtime when rebalance is > slow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799008#comment-16799008
]
Peter Ivanov commented on IGNITE-11595:
---
Updated PR.
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11607) Historical rebalance is not possible from partition which was recently rebalanced itself
[ https://issues.apache.org/jira/browse/IGNITE-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-11607: --- Description: This is due to current rebalance implementation limitations (history is marked as un-reservable). (was: This is due to current rebalance implementation limitations.) > Historical rebalance is not possible from partition which was recently > rebalanced itself > > > Key: IGNITE-11607 > URL: https://issues.apache.org/jira/browse/IGNITE-11607 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Priority: Major > Fix For: 2.8 > > > This is due to current rebalance implementation limitations (history is > marked as un-reservable). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11493) Test CheckpointFreeListTest#testFreeListRestoredCorrectly always fails in DiskCompression suite
[
https://issues.apache.org/jira/browse/IGNITE-11493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov reassigned IGNITE-11493:
--
Assignee: Anton Kalashnikov
> Test CheckpointFreeListTest#testFreeListRestoredCorrectly always fails in
> DiskCompression suite
> ---
>
> Key: IGNITE-11493
> URL: https://issues.apache.org/jira/browse/IGNITE-11493
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Anton Kalashnikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails with the following NullPointerException in logs:
> {code}
> [2019-03-06
> 16:05:24,353][ERROR][exchange-worker-#94%client%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteCheckedException:
> null]]
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2948)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2769)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheCompressionManager.start0(CacheCompressionManager.java:55)
> at
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.start(GridCacheManagerAdapter.java:50)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.initCacheContext(GridCacheProcessor.java:2534)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:2344)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2270)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:2141)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$5(GridCacheProcessor.java:2094)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:2138)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:2093)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:2039)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:951)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:810)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2920)
> ... 3 more
> {code}
> Root cause of it is that CacheManager when initializing CacheContext on
> client tries to start GridCompressionManager which doesn't make sense on
> client node.
> We should either exclude compression manager from cache context on client or
> not start it during initialization phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10896) Add ability to use simultaneous cache filtering options with control.sh --cache idle_verify
[
https://issues.apache.org/jira/browse/IGNITE-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov reassigned IGNITE-10896:
-
Assignee: Denis Chudov
> Add ability to use simultaneous cache filtering options with control.sh
> --cache idle_verify
> ---
>
> Key: IGNITE-10896
> URL: https://issues.apache.org/jira/browse/IGNITE-10896
> Project: Ignite
> Issue Type: Improvement
>Reporter: ARomantsov
>Assignee: Denis Chudov
>Priority: Major
> Fix For: 2.8
>
>
> Now I can use only one of next options
> 1) --exclude-caches cache1,...,cacheN
> 2) --cache-filter ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT
> 3) cache1,...,cacheN
> Trying to use two or more of this options currently results in error:
> {noformat}
> Error: Should use only one of option: --excludeCaches, --cache-filter or pass
> caches explicitly
> {noformat}
> Instead, utility should do the following:
> 1) when two or more options specified, result cache set to make dump of
> should be logical AND of results of each option applied individually.
> ex.
> {noformat}
> cache.* --cache-filter PERSISTENT
> {noformat}
> should select all persistent caches starting from 'cache'
> {noformat}
>--cache-filter ALL
>--exclude-caches wrong-.*-caches
> {noformat}
> should select all caches but matching 'wrong-.*-caches' regexp
> etc.
> 2) filtering options passed to control utility should be logged into result
> dump file, so that user could understand that dump was taken from subset of
> cluster caches
> 3) when result of filter or filters AND'ing is empty set of cache names,
> proper error message should be given and no dump file generated.
> e.g.
> {noformat}Error: can't find any cache matching cache names '--skup-zerus' and
> cache filter 'PERSISTENT', dump won't be generated.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798978#comment-16798978
]
Ivan Pavlukhin commented on IGNITE-11595:
-
[~vveider], could you please remove {{assembly/docfiles/javadoc.css}} file as
it seems not needed anymore? Everything else looks good. I hope that we will
not forget to check javadocs when pre-release packages is ready.
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11607) Historical rebalance is not possible from partition which was recently rebalanced itself
[ https://issues.apache.org/jira/browse/IGNITE-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-11607: --- Description: This is due to current rebalance implementation limitations. > Historical rebalance is not possible from partition which was recently > rebalanced itself > > > Key: IGNITE-11607 > URL: https://issues.apache.org/jira/browse/IGNITE-11607 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Priority: Major > Fix For: 2.8 > > > This is due to current rebalance implementation limitations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11607) Historical rebalance is not possible from partition which was recently rebalanced itself
Alexei Scherbakov created IGNITE-11607: -- Summary: Historical rebalance is not possible from partition which was recently rebalanced itself Key: IGNITE-11607 URL: https://issues.apache.org/jira/browse/IGNITE-11607 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-11606:
---
Ignite Flags: (was: Docs Required)
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[
https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798966#comment-16798966
]
Dmitry Melnichuk commented on IGNITE-11593:
---
Today I did a little research on this topic. Seems like Ignite SQL accepts
VARBINARY data as an UTF8/ASCII string, that consists of hexadecimal digit
pairs, but returns it as an array of integers, with each integer representing a
byte value. For example, this code behaves quite as expected:
{code}
client.sql('DROP TABLE test_sql_binary IF EXISTS')
client.sql(
'CREATE TABLE test_sql_binary(id int primary key, varbin VARBINARY)'
)
client.sql(
'INSERT INTO test_sql_binary(id, varbin) VALUES (?, ?)',
query_args=(1, '0123456789abcdef'),
)
result = client.sql('SELECT * FROM test_sql_binary')
data = list(*result)[1]
print(data)
# [1, 35, 69, 103, -119, -85, -51, -17]
{code}
I do not know why Ignite accepts your arguments on server side without throwing
an SQL error. As for client side, I think this is not a bug.
> python thin client: insert and select VARBINARY data type through SQL
> -
>
> Key: IGNITE-11593
> URL: https://issues.apache.org/jira/browse/IGNITE-11593
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Dmitry Melnichuk
>Priority: Major
>
> varbin data type select is getting not parsed array of integer values
> Example:
> https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev reassigned IGNITE-11606:
--
Assignee: Eduard Shangareev
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[ https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Melnichuk updated IGNITE-11593: -- Labels: python (was: ) > python thin client: insert and select VARBINARY data type through SQL > - > > Key: IGNITE-11593 > URL: https://issues.apache.org/jira/browse/IGNITE-11593 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > > varbin data type select is getting not parsed array of integer values > Example: > https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-11299) During SSL Handshake GridNioServer.processWrite is invoked constantly
[
https://issues.apache.org/jira/browse/IGNITE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11299:
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI (URI Deploy){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3376332]]
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 500 JVM CRASH , Exit
Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=3376346]]
* IgniteOdbcTest: SslQueriesTestSuite: TestConnectionSslSuccess - 1,2% fails in
last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionVersionMismatchError - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingManyObjects - 0,9% fails in
last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite:
TestEscConvertFunctionByteArray - 0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionBool -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionDecimal
- 0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionFloat -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionDate -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite: TestEscConvertFunctionTime -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlEscConvertFunctionTestSuite:
TestEscConvertFunctionTimestamp - 0,9% fails in last 772 master runs.
* IgniteOdbcTest: SqlOperatorTestSuite: TestOperatorSubDouble - 0,9% fails in
last 772 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestGuidTrivial - 0,9% fails in last 772
master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestGuidEqualsToColumn - 0,9% fails in
last 772 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestByteArraySelect - 0,9% fails in last
772 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestByteArrayParam - 0,9% fails in last
772 master runs.
* IgniteOdbcTest: SqlTypesTestSuite: TestByteParamInsert - 0,9% fails in last
772 master runs.
* IgniteOdbcTest: TypesTestSuite: TestZeroDecimal - 0,9% fails in last 772
master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingSimple - 0,9% fails in last
772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionCommit - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionRollbackInsert -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionRollbackUpdate1 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionRollbackUpdate2 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionRollbackDelete1 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionRollbackDelete2 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionTxModeError - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionTxModeIgnore -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionConnectionTxModeCommit -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingClosingStatement - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingSeveralStatements - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingSeveralStatementsClosing -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: StreamingTestSuite: TestStreamingDifferentStatements - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentCommit - 0,9%
fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentRollbackInsert -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentRollbackUpdate1 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentRollbackUpdate2 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentRollbackDelete1 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentRollbackDelete2 -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentTxModeError -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite: TransactionEnvironmentTxModeIgnore -
0,9% fails in last 772 master runs.
* IgniteOdbcTest: TransactionTestSuite:
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798962#comment-16798962 ] Dmitriy Pavlov commented on IGNITE-11600: - [~vveider], Problem here is that we don't have any continuous delivery mechanism for Apache Ignite. So if we could update all Ignite instances worldwide in a couple of days, it could work. I've also asked fellow Igniters, they also think that it is better to be optimistic and allow 12,13,14 to run. Probably our vision difference is subject for dev list discussion. For now, I've applied `>11` condition to master. > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.7.5 > > Time Spent: 20m > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11600: Fix Version/s: 2.8 > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.8, 2.7.5 > > Time Spent: 20m > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11606) Index could not contain all values from cache after full rebuild
Eduard Shangareev created IGNITE-11606:
--
Summary: Index could not contain all values from cache after full
rebuild
Key: IGNITE-11606
URL: https://issues.apache.org/jira/browse/IGNITE-11606
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
If index.bin was deleted, we would rebuild it on node start.
But it could cause to the situation when a key is in the cache but SQL query
doesn't return it.
{code}
[18:29:07][:363] idle_verify check has finished, found 1194 conflict
partitions: [counterConflicts=0, hashConflicts=1194]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-11606:
---
Summary: Index could not contain all values from cache after index full
rebuild (was: Index could not contain all values from cache after full rebuild)
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Priority: Major
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11589) GridDhtPartitionsExchangeFuture remained incompleted in some circumstances
[
https://issues.apache.org/jira/browse/IGNITE-11589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11589:
-
Ignite Flags: (was: Docs Required)
> GridDhtPartitionsExchangeFuture remained incompleted in some circumstances
> --
>
> Key: IGNITE-11589
> URL: https://issues.apache.org/jira/browse/IGNITE-11589
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridDhtPartitionsExchangeFuture#onDone}} contains a piece of code that
> should be executed before {{GridFutureAdapter#onDone}} is called and so,
> in case of an exception is thrown by that code, exchange future is not
> completed and, therefore, it may cause a deadlock.
> the following stack trace can be used as an example of that behavior:
> {noformat}
> [GridDhtPartitionsExchangeFuture] Failed to reinitialize local partitions
> (rebalancing will be stopped): GridDhtPartitionExchangeId [...msg=Node left:
> TcpDiscoveryNode [ ], type=NODE_LEFT]
> class org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.detectLostPartitions(GridDhtPartitionsExchangeFuture.java:3152)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3549)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3301)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1516)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:849)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2878)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2727)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10846)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.detectLostPartitions(GridDhtPartitionsExchangeFuture.java:3135)
> ... 9 more
> Caused by: java.lang.InterruptedException
> at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:404)
> at java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.ignite.internal.util.IgniteUtils$Batch.result(IgniteUtils.java:10947)
> at
> org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10836)
> ... 10 more{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798938#comment-16798938
]
Peter Ivanov edited comment on IGNITE-11600 at 3/22/19 11:51 AM:
-
[~dpavlov], no. My point — we know that JDK XX is going to be released some
times forward — we add support by just adding IF clause.
Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party)
JDK with correct message that it is not supported (and add support in default
development cycle a little bit later) then start by default and work in some
unpredictable way.
I'm sure, some instances are installed on the environments, where default JDK
can be subject to change without any notes (include software autoupdate and
etc.).
Also that hack's with {{--add-exports}} can no longer work from JDK to JDK, as
it was between 9 and 11.
was (Author: vveider):
[~dpavlov], no. My point — we know that JDK XX is going to be released some
times forward — we add support by just adding IF clause.
Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party)
JDK with correct message that it is not supported (and add support in default
development cycle a little bit later) then start by default and work in some
unpredictable way.
I'm sure, some instances are installed on the environments, where default JDK
can be subject to change without any notes (include software autoupdate and
etc.).
Also that hack's with {{—add-exports}} can no longer work from JDK to JDK, as
it was between 9 and 11.
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798938#comment-16798938 ] Peter Ivanov commented on IGNITE-11600: --- [~dpavlov], no. My point — we know that JDK XX is going to be released some times forward — we add support by just adding IF clause. Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party) JDK with correct message that it is not supported (and add support in default development cycle a little bit later) then start by default and work in some unpredictable way. I'm sure, some instances are installed on the environments, where default JDK can be subject to change without any notes (include software autoupdate and etc.). > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798938#comment-16798938
]
Peter Ivanov edited comment on IGNITE-11600 at 3/22/19 11:51 AM:
-
[~dpavlov], no. My point — we know that JDK XX is going to be released some
times forward — we add support by just adding IF clause.
Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party)
JDK with correct message that it is not supported (and add support in default
development cycle a little bit later) then start by default and work in some
unpredictable way.
I'm sure, some instances are installed on the environments, where default JDK
can be subject to change without any notes (include software autoupdate and
etc.).
Also that hack's with {{—add-exports}} can no longer work from JDK to JDK, as
it was between 9 and 11.
was (Author: vveider):
[~dpavlov], no. My point — we know that JDK XX is going to be released some
times forward — we add support by just adding IF clause.
Because it is better (IMO) to fail to start on unknown (new | old | 3-rd party)
JDK with correct message that it is not supported (and add support in default
development cycle a little bit later) then start by default and work in some
unpredictable way.
I'm sure, some instances are installed on the environments, where default JDK
can be subject to change without any notes (include software autoupdate and
etc.).
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11299) During SSL Handshake GridNioServer.processWrite is invoked constantly
[
https://issues.apache.org/jira/browse/IGNITE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798940#comment-16798940
]
Ignite TC Bot commented on IGNITE-11299:
{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=3376416buildTypeId=IgniteTests24Java8_RunAll]
> During SSL Handshake GridNioServer.processWrite is invoked constantly
> -
>
> Key: IGNITE-11299
> URL: https://issues.apache.org/jira/browse/IGNITE-11299
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
> Labels: important, ssl
> Fix For: 2.8, 2.7.5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Causes busy looping in processSelectionKeyOptimized()
> This also causes problems on Windows/Java 11 since if key is always ready for
> writing it will never be shown as ready for reading.
> The reason for this behavior that during handshake we never un-listen OP_WRITE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11265) Node stop causes JVM Crashes in page memory
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798936#comment-16798936 ] Dmitriy Pavlov commented on IGNITE-11265: - [~EdShangGG] could you please double check if the cherry-picked to 2.7.5 commit was migrated successfully? https://github.com/apache/ignite/commit/0d04b0236e42ec7a826e8b57e894251ed65ed77c > Node stop causes JVM Crashes in page memory > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.8, 2.7.5 > > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > Time Spent: 20m > Remaining Estimate: 0h > > Reproduced on Teamcity:All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798934#comment-16798934
]
Ignite TC Bot commented on IGNITE-11600:
{panel:title=-- Run :: Basic Tests: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests 5 JVM CRASH , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3382144]]
* exe: PartitionLossTest.TestReadOnlyAll - 79,4% fails in last 506 master runs.
* exe: PartitionLossTest.TestReadOnlySafe - 72,1% fails in last 506 master runs.
* exe: PartitionLossTest.TestReadWriteAll - 64,6% fails in last 506 master runs.
* exe: PartitionLossTest.TestReadWriteSafe - 60,3% fails in last 506 master
runs.
* exe: ConsoleRedirectTest.TestMultipleDomains - 26,9% fails in last 505 master
runs.
{panel}
[TeamCity *-- Run :: Basic Tests*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3382147buildTypeId=IgniteTests24Java8_RunBasicTests]
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798933#comment-16798933 ] Dmitriy Pavlov commented on IGNITE-11600: - ok, thank you. I suppose if Java community will build newer java each month Apache Ignite will not be able to build a newer version so often. So, is it better to try to start Apache Ignite? Or just give up by default and fail with a comment please specify --add-exports. > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11605) Incorrect check condition in BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage
Anton Kalashnikov created IGNITE-11605:
--
Summary: Incorrect check condition in
BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage
Key: IGNITE-11605
URL: https://issues.apache.org/jira/browse/IGNITE-11605
Project: Ignite
Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov
BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage is flaky.
{noformat}
java.lang.AssertionError:
Expected :1
Actual :2
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.ignite.testframework.junits.JUnitAssertAware.assertEquals(JUnitAssertAware.java:94)
at
org.apache.ignite.internal.processors.cache.BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage(BinaryTypeRegistrationTest.java:106)
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
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2102)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11531) Merge concurrent registrations of the same binary type
[
https://issues.apache.org/jira/browse/IGNITE-11531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov resolved IGNITE-11531.
Resolution: Fixed
> Merge concurrent registrations of the same binary type
> --
>
> Key: IGNITE-11531
> URL: https://issues.apache.org/jira/browse/IGNITE-11531
> Project: Ignite
> Issue Type: Improvement
> Components: binary
>Reporter: Denis Mekhanikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When a binary type is registered multiple times simultaneously, then a lot of
> type versions are generated with the same schema. It leads to long binary
> type registration especially on big topologies.
> The following code sample demonstrates the problem:
> {code:java}
> public class LongRegistration {
> public static void main(String[] args) throws InterruptedException {
> Ignite ignite = Ignition.start(igniteConfig());
> int threadsNum = 50;
> ExecutorService exec = Executors.newFixedThreadPool(threadsNum);
> CyclicBarrier barrier = new CyclicBarrier(threadsNum);
> long startTime = System.currentTimeMillis();
> // register(ignite);
> for (int i = 0; i < threadsNum; i++)
> exec.submit(new TypeRegistrator(ignite, barrier));
> exec.shutdown();
> exec.awaitTermination(Long.MAX_VALUE, TimeUnit.SECONDS);
> System.out.println("Total registration time: " +
> (System.currentTimeMillis() - startTime));
> }
> private static IgniteConfiguration igniteConfig() {
> IgniteConfiguration igniteCfg = new IgniteConfiguration();
> TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
>
> ipFinder.setAddresses(Collections.singletonList("127.0.0.1:47500..47509"));
> TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
> discoverySpi.setLocalAddress("127.0.0.1");
> discoverySpi.setLocalPort(47500);
> discoverySpi.setIpFinder(ipFinder);
> igniteCfg.setDiscoverySpi(discoverySpi);
> return igniteCfg;
> }
> private static void register(Ignite ignite) {
> long startTime = System.currentTimeMillis();
> IgniteBinary binary = ignite.binary();
> BinaryObjectBuilder builder = binary.builder("TestType");
> builder.setField("intField", 1);
> builder.build();
> System.out.println("Registration time: " +
> (System.currentTimeMillis() - startTime));
> }
> private static class TypeRegistrator implements Runnable {
> private Ignite ignite;
> private CyclicBarrier cyclicBarrier;
> TypeRegistrator(Ignite ignite, CyclicBarrier cyclicBarrier) {
> this.ignite = ignite;
> this.cyclicBarrier = cyclicBarrier;
> }
> @Override public void run() {
> try {
> cyclicBarrier.await();
> register(ignite);
> } catch (InterruptedException | BrokenBarrierException e) {
> e.printStackTrace();
> }
> }
> }
> }
> {code}
> This code sample leads to registration of 50 versions of the same type. The
> effect is more noticeable if a cluster contains a lot of nodes.
> If you uncomment the call to {{register()}} method, then overall registration
> becomes 10 times faster on topology of 5 nodes.
> Registration of matching types should be merged to avoid long processing of
> such cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798927#comment-16798927 ] Peter Ivanov commented on IGNITE-11600: --- I do not agree. Anyway — code is fine. > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11590) NPE during onKernalStop in mvcc processor
[
https://issues.apache.org/jira/browse/IGNITE-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798926#comment-16798926
]
Ignite TC Bot commented on IGNITE-11590:
{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=3372334buildTypeId=IgniteTests24Java8_RunAll]
> NPE during onKernalStop in mvcc processor
> --
>
> Key: IGNITE-11590
> URL: https://issues.apache.org/jira/browse/IGNITE-11590
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IgniteProjectionStartStopRestartSelfTest#testStopNodesByIds
> {noformat}
> java.lang.NullPointerException
> at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
> at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onCoordinatorFailed(MvccProcessorImpl.java:527)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onKernalStop(MvccProcessorImpl.java:459)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2335)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:297)
> at org.apache.ignite.Ignition.stop(Ignition.java:200)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.afterTest(IgniteProjectionStartStopRestartSelfTest.java:190)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1804)
> at
> org.apache.ignite.testframework.junits.JUnit3TestLegacySupport.runTestCase(JUnit3TestLegacySupport.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.evaluate(GridAbstractTest.java:185)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.evaluateInsideFixture(GridAbstractTest.java:2579)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$500(GridAbstractTest.java:152)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$BeforeFirstAndAfterLastTestRule$1.evaluate(GridAbstractTest.java:2559)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11265) Node stop causes JVM Crashes in page memory
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Fix Version/s: 2.7.5 > Node stop causes JVM Crashes in page memory > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.8, 2.7.5 > > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > Time Spent: 20m > Remaining Estimate: 0h > > Reproduced on Teamcity:All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11265) Node stop causes JVM Crashes in page memory
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Summary: Node stop causes JVM Crashes in page memory (was: JVM Crashes on TeamCity) > Node stop causes JVM Crashes in page memory > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.8 > > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > Time Spent: 20m > Remaining Estimate: 0h > > All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11265) Node stop causes JVM Crashes in page memory
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Description: Reproduced on Teamcity:All crash dumps complain about the same method org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log Other recent examples Queries 1 https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log Client Nodes https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log Zookeeper Discovery https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log was: All crash dumps complain about the same method org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log Other recent examples Queries 1 https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log Client Nodes https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log Zookeeper Discovery https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log > Node stop causes JVM Crashes in page memory > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.8 > > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > Time Spent: 20m > Remaining Estimate: 0h > > Reproduced on Teamcity:All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11191) Fix Hibernate 5.3 integration by providing JAXB & RMI dependencies
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11191:
Summary: Fix Hibernate 5.3 integration by providing JAXB & RMI dependencies
(was: Fix Hibernate integration by providing JAXB & RMI dependencies)
> Fix Hibernate 5.3 integration by providing JAXB & RMI dependencies
> --
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733=buildResultsDiv=IgniteTests24Java8_Hibernate53#testNameId-1306520535171712877
> {noformat}
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1018)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
> at
> org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
> at org.apache.ignite.cache
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798914#comment-16798914 ] Dmitriy Pavlov commented on IGNITE-11600: - I suppose that is better to try to start on newer JDKs, I've tried to add code, which will add java-9+ related parameters without JAXB for Javas ver. >= 11. So 11,12,13,... all should be handled equally with Java 11. > Fix launch script for Java 12 > - > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11590) NPE during onKernalStop in mvcc processor
[
https://issues.apache.org/jira/browse/IGNITE-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-11590:
--
Ignite Flags: (was: Docs Required)
> NPE during onKernalStop in mvcc processor
> --
>
> Key: IGNITE-11590
> URL: https://issues.apache.org/jira/browse/IGNITE-11590
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IgniteProjectionStartStopRestartSelfTest#testStopNodesByIds
> {noformat}
> java.lang.NullPointerException
> at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
> at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onCoordinatorFailed(MvccProcessorImpl.java:527)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onKernalStop(MvccProcessorImpl.java:459)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2335)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:297)
> at org.apache.ignite.Ignition.stop(Ignition.java:200)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.afterTest(IgniteProjectionStartStopRestartSelfTest.java:190)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1804)
> at
> org.apache.ignite.testframework.junits.JUnit3TestLegacySupport.runTestCase(JUnit3TestLegacySupport.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.evaluate(GridAbstractTest.java:185)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.evaluateInsideFixture(GridAbstractTest.java:2579)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$500(GridAbstractTest.java:152)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$BeforeFirstAndAfterLastTestRule$1.evaluate(GridAbstractTest.java:2559)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798904#comment-16798904
]
Peter Ivanov edited comment on IGNITE-11600 at 3/22/19 10:55 AM:
-
Not sure that this is correct fix. It will by default silently fail with on
future JDK versions to prevent from starting on unsupported JDKs.
How about double clause:
{code}
IF %MAJOR_JAVA_VER% EQU 11 IF %MAJOR_JAVA_VER% EQU 12 (
...
{code}
was (Author: vveider):
Not sure that this is correct fix. It will by default silently fail with future
JDK versions to prevent from starting on unsupported JDKs.
How about double clause:
{code}
IF %MAJOR_JAVA_VER% EQU 11 IF %MAJOR_JAVA_VER% EQU 12 (
...
{code}
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798904#comment-16798904
]
Peter Ivanov commented on IGNITE-11600:
---
Not sure that is correct fix. It will by default silently fail with future JDK
versions to prevent from starting on unsupported JDKs.
How about double clause:
{code}
IF %MAJOR_JAVA_VER% EQU 11 IF %MAJOR_JAVA_VER% EQU 12 (
...
{code}
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11600) Fix launch script for Java 12
[
https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798904#comment-16798904
]
Peter Ivanov edited comment on IGNITE-11600 at 3/22/19 10:55 AM:
-
Not sure that this is correct fix. It will by default silently fail with future
JDK versions to prevent from starting on unsupported JDKs.
How about double clause:
{code}
IF %MAJOR_JAVA_VER% EQU 11 IF %MAJOR_JAVA_VER% EQU 12 (
...
{code}
was (Author: vveider):
Not sure that is correct fix. It will by default silently fail with future JDK
versions to prevent from starting on unsupported JDKs.
How about double clause:
{code}
IF %MAJOR_JAVA_VER% EQU 11 IF %MAJOR_JAVA_VER% EQU 12 (
...
{code}
> Fix launch script for Java 12
> -
>
> Key: IGNITE-11600
> URL: https://issues.apache.org/jira/browse/IGNITE-11600
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> bin/ignite.bat:251
> if "%MAJOR_JAVA_VER%" == "11" (
> need to change to "%MAJOR_JAVA_VER%" GEQ "11" (
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-1090) GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
[
https://issues.apache.org/jira/browse/IGNITE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-1090:
-
Fix Version/s: 2.8
> GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
> --
>
> Key: IGNITE-1090
> URL: https://issues.apache.org/jira/browse/IGNITE-1090
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Denis Magda
>Assignee: Semen Boikov
>Priority: Critical
> Labels: Muted_test, test-fail
> Fix For: 2.8
>
>
> The test hangs with the following errors:
> {noformat}
> [16:26:33] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Map reducer: {}, init=true,
> res=java.util.concurrent.atomic.AtomicMarkableReference@3c6fff03, err=null,
> done=false, cancelled=false, err=null, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Failed to wait for topology version
> to change: AffinityTopologyVersion [topVer=274, minorTopVer=0]
> at
> org.apache.ignite.internal.processors.cache.distributed.GridFutureRemapTimeoutObject.onTimeout(GridFutureRemapTimeoutObject.java:64)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Remote
> node left grid (will retry): 703c58e1-e099-4f22-b5c3-6c3676338007
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onNodeLeft(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:186)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1719)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1910)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1758)
> ... 2 more
> {noformat}
> This issue appeared after IGNITE-882 was fixed. Until it wasn't fixed the
> tests hung because of this issue:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Remote node ID is
> not as expected [expected=9019c94c-84f5-4065-89b1-f16fdf708009,
> rcvd=707ed613-1b65-4771-ac98-5faa6857e007]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2203)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2025)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11541) Dynamic columns and indexes can be lost after the cluster restart
[
https://issues.apache.org/jira/browse/IGNITE-11541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798902#comment-16798902
]
Ignite TC Bot commented on IGNITE-11541:
{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=3373394buildTypeId=IgniteTests24Java8_RunAll]
> Dynamic columns and indexes can be lost after the cluster restart
> -
>
> Key: IGNITE-11541
> URL: https://issues.apache.org/jira/browse/IGNITE-11541
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.8
>
> Attachments: StaticCacheAndDdlReproducer.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The case is the following:
> # Run a server node (persistence enabled. static cache configuration with
> queryEnities).
> # Add/drop column/index via DDL.
> # Restart the node with the same configuration.
> # The changes are lost...
> It seems the issue is related to merging cache metadata.
> There are some workarounds:
> # Remove/comment cache configuration. After the restart, the metadata will be
> loaded from the persistence store. This will work for a rolling restart.
> # Make the same changes in the configuration (update queryEntity). It
> requires the whole cluster restart.
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-1090) GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
[
https://issues.apache.org/jira/browse/IGNITE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798873#comment-16798873
]
Ignite TC Bot commented on IGNITE-1090:
---
{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=3346033buildTypeId=IgniteTests24Java8_RunAll]
> GridCachePartitionedOptimisticTxNodeRestartTest hangs when node lefts topology
> --
>
> Key: IGNITE-1090
> URL: https://issues.apache.org/jira/browse/IGNITE-1090
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Denis Magda
>Assignee: Semen Boikov
>Priority: Critical
> Labels: Muted_test, test-fail
>
> The test hangs with the following errors:
> {noformat}
> [16:26:33] (err) Failed to execute compound future reducer: Compound future
> listener: GridCompoundIdentityFuture [super=GridCompoundFuture [lsnrCalls=0,
> finished=false, rdc=Map reducer: {}, init=true,
> res=java.util.concurrent.atomic.AtomicMarkableReference@3c6fff03, err=null,
> done=false, cancelled=false, err=null, futs=[true]]]class
> org.apache.ignite.IgniteCheckedException: Failed to wait for topology version
> to change: AffinityTopologyVersion [topVer=274, minorTopVer=0]
> at
> org.apache.ignite.internal.processors.cache.distributed.GridFutureRemapTimeoutObject.onTimeout(GridFutureRemapTimeoutObject.java:64)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: Remote
> node left grid (will retry): 703c58e1-e099-4f22-b5c3-6c3676338007
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onNodeLeft(GridNearGetFuture.java:215)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$3.onEvent(GridCacheMvccManager.java:186)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:745)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:730)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:270)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:1719)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:1910)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:1758)
> ... 2 more
> {noformat}
> This issue appeared after IGNITE-882 was fixed. Until it wasn't fixed the
> tests hung because of this issue:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Remote node ID is
> not as expected [expected=9019c94c-84f5-4065-89b1-f16fdf708009,
> rcvd=707ed613-1b65-4771-ac98-5faa6857e007]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2203)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2025)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11595:
Fix Version/s: 2.8
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.8, 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798871#comment-16798871
]
Dmitriy Pavlov commented on IGNITE-11595:
-
[~Pavlukhin], could you please review the fix?
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11569) Enable baseline auto-adjust by default only for empty cluster
[
https://issues.apache.org/jira/browse/IGNITE-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798869#comment-16798869
]
Ignite TC Bot commented on IGNITE-11569:
{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=3373640buildTypeId=IgniteTests24Java8_RunAll]
> Enable baseline auto-adjust by default only for empty cluster
> -
>
> Key: IGNITE-11569
> URL: https://issues.apache.org/jira/browse/IGNITE-11569
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It is required to enable baseline auto-adjust by default only for empty
> cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11590) NPE during onKernalStop in mvcc processor
[
https://issues.apache.org/jira/browse/IGNITE-11590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798846#comment-16798846
]
Anton Kalashnikov commented on IGNITE-11590:
[~amashenkov] thanks for your comment. Can you please review my changes?
> NPE during onKernalStop in mvcc processor
> --
>
> Key: IGNITE-11590
> URL: https://issues.apache.org/jira/browse/IGNITE-11590
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IgniteProjectionStartStopRestartSelfTest#testStopNodesByIds
> {noformat}
> java.lang.NullPointerException
> at
> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
> at
> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onCoordinatorFailed(MvccProcessorImpl.java:527)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onKernalStop(MvccProcessorImpl.java:459)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2335)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:297)
> at org.apache.ignite.Ignition.stop(Ignition.java:200)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.afterTest(IgniteProjectionStartStopRestartSelfTest.java:190)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1804)
> at
> org.apache.ignite.testframework.junits.JUnit3TestLegacySupport.runTestCase(JUnit3TestLegacySupport.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.evaluate(GridAbstractTest.java:185)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.evaluateInsideFixture(GridAbstractTest.java:2579)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$500(GridAbstractTest.java:152)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$BeforeFirstAndAfterLastTestRule$1.evaluate(GridAbstractTest.java:2559)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11604) Drop column does not remove column from internal schema
[
https://issues.apache.org/jira/browse/IGNITE-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11604:
--
Component/s: sql
> Drop column does not remove column from internal schema
> ---
>
> Key: IGNITE-11604
> URL: https://issues.apache.org/jira/browse/IGNITE-11604
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> Discovered this during the work on IGNITE-11541 (see
> {{StaticCacheDdlTest.testDropColumn}}).
> After a quick debug I see the following: in
> {{GridQueryProcessor#onSchemaFinishDiscovery}} we call
> {{DynamicCacheDescriptor.schemaChangeFinish(msg)}}, which eventually calls
> {{QuerySchema.finish(op)}}.
> Inside that method we have the following: the {{message.columns()}}
> collection has the field name in upper case (in the test it's
> "FIELD_TO_DROP"), but the entity's fields map contains lower-case names
> ("field_to_drop"). As a result, we do not remove the field from the query
> entity, this query entity is saved to the stored cache data and field
> re-appears after restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11604) Drop column does not remove column from internal schema
[
https://issues.apache.org/jira/browse/IGNITE-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11604:
--
Ignite Flags: (was: Docs Required)
> Drop column does not remove column from internal schema
> ---
>
> Key: IGNITE-11604
> URL: https://issues.apache.org/jira/browse/IGNITE-11604
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Major
>
> Discovered this during the work on IGNITE-11541 (see
> {{StaticCacheDdlTest.testDropColumn}}).
> After a quick debug I see the following: in
> {{GridQueryProcessor#onSchemaFinishDiscovery}} we call
> {{DynamicCacheDescriptor.schemaChangeFinish(msg)}}, which eventually calls
> {{QuerySchema.finish(op)}}.
> Inside that method we have the following: the {{message.columns()}}
> collection has the field name in upper case (in the test it's
> "FIELD_TO_DROP"), but the entity's fields map contains lower-case names
> ("field_to_drop"). As a result, we do not remove the field from the query
> entity, this query entity is saved to the stored cache data and field
> re-appears after restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11604) Drop column does not remove column from internal schema
[
https://issues.apache.org/jira/browse/IGNITE-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11604:
--
Fix Version/s: 2.8
> Drop column does not remove column from internal schema
> ---
>
> Key: IGNITE-11604
> URL: https://issues.apache.org/jira/browse/IGNITE-11604
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
>
> Discovered this during the work on IGNITE-11541 (see
> {{StaticCacheDdlTest.testDropColumn}}).
> After a quick debug I see the following: in
> {{GridQueryProcessor#onSchemaFinishDiscovery}} we call
> {{DynamicCacheDescriptor.schemaChangeFinish(msg)}}, which eventually calls
> {{QuerySchema.finish(op)}}.
> Inside that method we have the following: the {{message.columns()}}
> collection has the field name in upper case (in the test it's
> "FIELD_TO_DROP"), but the entity's fields map contains lower-case names
> ("field_to_drop"). As a result, we do not remove the field from the query
> entity, this query entity is saved to the stored cache data and field
> re-appears after restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11604) Drop column does not remove column from internal schema
Alexey Goncharuk created IGNITE-11604:
-
Summary: Drop column does not remove column from internal schema
Key: IGNITE-11604
URL: https://issues.apache.org/jira/browse/IGNITE-11604
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
Discovered this during the work on IGNITE-11541 (see
{{StaticCacheDdlTest.testDropColumn}}).
After a quick debug I see the following: in
{{GridQueryProcessor#onSchemaFinishDiscovery}} we call
{{DynamicCacheDescriptor.schemaChangeFinish(msg)}}, which eventually calls
{{QuerySchema.finish(op)}}.
Inside that method we have the following: the {{message.columns()}} collection
has the field name in upper case (in the test it's "FIELD_TO_DROP"), but the
entity's fields map contains lower-case names ("field_to_drop"). As a result,
we do not remove the field from the query entity, this query entity is saved to
the stored cache data and field re-appears after restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11443) Usability improvements system SQL view
[
https://issues.apache.org/jira/browse/IGNITE-11443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798835#comment-16798835
]
Ignite TC Bot commented on IGNITE-11443:
{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=3373759buildTypeId=IgniteTests24Java8_RunAll]
> Usability improvements system SQL view
> --
>
> Key: IGNITE-11443
> URL: https://issues.apache.org/jira/browse/IGNITE-11443
> 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
>
> For all views need to:
> 1) move cache and cache group attributes to the beginning to form consistent
> hierarchy: cache group -> cache -> schema -> table -> index
> 2) columns GROUP_ID and GROUP_NAME should be renamed to CACHE_GROUP_ID and
> CACHE_GROUP_NAME respectively
> 3) TABLES view: add CACHE_GROUP_NAME and CACHE_GROUP_ID attributes
> 4) CACHES and CACHE_GROUPS: if there is no node filter
> (IgniteAllNodesPredicate) we should print NULL
> 5) CACHE_GROUPS.BACKUPS - show NULL for REPLICATED caches (Integer.MAX_VALUE
> is shown at the moment)
> 6) For all columns with name ID need to add prefix which reflect real meaning
> of the column
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798831#comment-16798831
]
Sergey Kozlov commented on IGNITE-11588:
probably the linked isssues will be fixed as well
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11603) ESCAPE key word in combination with LIKE statement seems to be prohibited
Emanuel Warga created IGNITE-11603:
--
Summary: ESCAPE key word in combination with LIKE statement seems
to be prohibited
Key: IGNITE-11603
URL: https://issues.apache.org/jira/browse/IGNITE-11603
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 2.7
Reporter: Emanuel Warga
As described in
https://stackoverflow.com/questions/55283492/like-statement-causes-unsupported-query-on-ignite-2-7-with-querydsl
Ignite seems to have a problem when I use LIKE with the ESCAPE key word.
Example:
{{ select * from mytable mt where (mt.c1 LIKE 'Abc%' ESCAPE '!');}}
I get an error announcing this is an unsupported query.
The error doesn't show up if I don't use '% inside the search string so the
problem doesn't seem to be a general one like "we don't support the ESCAPE key
word."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7152) Failure detection timeout don't work on permanent send message errors causing infinite loop
[
https://issues.apache.org/jira/browse/IGNITE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798820#comment-16798820
]
Sergey Chugunov commented on IGNITE-7152:
-
[~zstan],
As I can see from TC Bot report there are non-flaky failures
*IgniteDiscoveryMassiveNodeFailTest.testMassiveFailSelfKill* and
*IgniteDiscoveryMassiveNodeFailTest.testMassiveFailAndRecovery* that don't fail
in master.
These tests cover connection recovery mechanism so it seems that your change
breaks something in it.
I think we need to come up with another way to fix the issue, either by
modifying connection recovery mechanism to segment node facing read receipt
failures or by improving timeouts handling.
> Failure detection timeout don't work on permanent send message errors causing
> infinite loop
> ---
>
> Key: IGNITE-7152
> URL: https://issues.apache.org/jira/browse/IGNITE-7152
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Fix For: 2.8
>
> Attachments: testFailureDetectionOnReceiptError.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Relative to {{RingMessageWorker.sendMessageAcrossRing}} implementation.
> {{IgniteSpiOperationTimeoutHelper}} reinitialized every time the socket
> successfully connected.
> If any of {{IOException, IgniteCheckedException}} occurs upon message send
> the socket will be closed and old {{IgniteSpiOperationTimeoutHelper}} will be
> used to reconnect.
> But after successful reconnect the new one will be created and the cycle
> repeat. With a permanent send message error this causes an infinite loop.
> The only send error which may cause to exit out of the loop and the next node
> failure is {{IgniteSpiOperationTimeoutException, SocketTimeoutException,
> SocketException}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798812#comment-16798812
]
Peter Ivanov commented on IGNITE-11595:
---
[~dpavlov], yes, exactly.
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.7.5
>
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-11595:
--
Description:
After moving to JDK 8 build the bug in Javadoc HTML view was introduced due to
new javadoc.css from JDK 8 which was overridden by hardcode
({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
{{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.7.5
>
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11011) Initialize components with grid disco data when NodeAddFinished message is received
[ https://issues.apache.org/jira/browse/IGNITE-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-11011: - Ignite Flags: (was: Docs Required) > Initialize components with grid disco data when NodeAddFinished message is > received > --- > > Key: IGNITE-11011 > URL: https://issues.apache.org/jira/browse/IGNITE-11011 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > There is an issue when CacheProcessor on fresh coordinator (the very first > node in new topology) receives grid discovery data from another cluster that > died before this node has joined its topology but after sending NodeAdded > message. > IGNITE-10878 fixes it by filtering cache descriptors and cache groups in > GridCacheProcessor which is not generic solution. > To fix the issue in a true generic way node should initialize its components > (including cache processor) not on receiving NodeAdded message but > NodeAddFinished message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11011) Initialize components with grid disco data when NodeAddFinished message is received
[
https://issues.apache.org/jira/browse/IGNITE-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798804#comment-16798804
]
Ignite TC Bot commented on IGNITE-11011:
{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=3361394buildTypeId=IgniteTests24Java8_RunAll]
> Initialize components with grid disco data when NodeAddFinished message is
> received
> ---
>
> Key: IGNITE-11011
> URL: https://issues.apache.org/jira/browse/IGNITE-11011
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is an issue when CacheProcessor on fresh coordinator (the very first
> node in new topology) receives grid discovery data from another cluster that
> died before this node has joined its topology but after sending NodeAdded
> message.
> IGNITE-10878 fixes it by filtering cache descriptors and cache groups in
> GridCacheProcessor which is not generic solution.
> To fix the issue in a true generic way node should initialize its components
> (including cache processor) not on receiving NodeAdded message but
> NodeAddFinished message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
