[jira] [Comment Edited] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795584#comment-16795584
]
Pavel Konstantinov edited comment on IGNITE-11386 at 3/19/19 3:22 AM:
--
Tested in the branch, but failed to save a generated project due to
{code}Failed to generate project preview: [object ErrorEvent]{code}
was (Author: pkonstantinov):
Tested in branch
> Web console: Actualize configuragion for localEventListeners field of
> IgniteConfiguration
> -
>
> Key: IGNITE-11386
> URL: https://issues.apache.org/jira/browse/IGNITE-11386
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Missed field in configurator.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795584#comment-16795584 ] Pavel Konstantinov edited comment on IGNITE-11386 at 3/19/19 3:20 AM: -- Tested in branch was (Author: pkonstantinov): Can't find such field on UI. [~vsisko] please help. > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-11386: --- Assignee: Vasiliy Sisko (was: Pavel Konstantinov) > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11386) Web console: Actualize configuragion for localEventListeners field of IgniteConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795584#comment-16795584 ] Pavel Konstantinov commented on IGNITE-11386: - Can't find such field on UI. [~vsisko] please help. > Web console: Actualize configuragion for localEventListeners field of > IgniteConfiguration > - > > Key: IGNITE-11386 > URL: https://issues.apache.org/jira/browse/IGNITE-11386 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Missed field in configurator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10797) Remove unused methods from IgniteCacheSnapshotManager.
[
https://issues.apache.org/jira/browse/IGNITE-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795446#comment-16795446
]
Ignite TC Bot commented on IGNITE-10797:
{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=3347498buildTypeId=IgniteTests24Java8_RunAll]
> Remove unused methods from IgniteCacheSnapshotManager.
> --
>
> Key: IGNITE-10797
> URL: https://issues.apache.org/jira/browse/IGNITE-10797
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Remove unused methods:
> IgniteCacheSnapshotManager#flushDirtyPageHandler
> IgniteCacheSnapshotManager#onPageWrite
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7538) Update several maven plugins version for Java 9 compilation
[ https://issues.apache.org/jira/browse/IGNITE-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795320#comment-16795320 ] Peter Ivanov commented on IGNITE-7538: -- I guess it should be tested on Basic Run All at least. > Update several maven plugins version for Java 9 compilation > --- > > Key: IGNITE-7538 > URL: https://issues.apache.org/jira/browse/IGNITE-7538 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > * rat plugin > * flat plugin > * java plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11397) Binary mode for Ignite Set
[
https://issues.apache.org/jira/browse/IGNITE-11397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795275#comment-16795275
]
Ignite TC Bot commented on IGNITE-11397:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3345258]]
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testLockAllMultinode - 0,0% fails in
last 383 master runs.
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3345261]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackups - 0,0%
fails in last 305 master runs.
{color:#d04437}Data Structures{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=3345269]]
* IgniteCacheDataStructuresSelfTestSuite:
IgnitePartitionedSetNoBackupsSelfTest.testAffinityRun - 0,0% fails in last 388
master runs.
* IgniteCacheDataStructuresSelfTestSuite:
IgnitePartitionedSetNoBackupsSelfTest.testAffinityCall - 0,0% fails in last 388
master runs.
* IgniteCacheDataStructuresSelfTestSuite:
GridCacheReplicatedSetWithClientSelfTest.testAffinityRun - 0,0% fails in last
388 master runs.
* IgniteCacheDataStructuresSelfTestSuite:
GridCacheReplicatedSetWithClientSelfTest.testAffinityCall - 0,0% fails in last
388 master runs.
* IgniteCacheDataStructuresSelfTestSuite:
GridCacheReplicatedSetSelfTest.testAffinityRun - 0,0% fails in last 388 master
runs.
* IgniteCacheDataStructuresSelfTestSuite:
GridCacheReplicatedSetSelfTest.testAffinityCall - 0,0% fails in last 388 master
runs.
{color:#d04437}Cache 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3345260]]
* IgniteCacheTestSuite4:
CacheStoreUsageMultinodeStaticStartTxTest.testStaticConfigurationTxWriteBehindStoreNoClientStore
- 0,0% fails in last 394 master runs.
{color:#d04437}_Javadoc_{color} [[tests 0 BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=3345244]]
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 TIMEOUT , Failure on
metric |https://ci.ignite.apache.org/viewLog.html?buildId=3345239]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3345309buildTypeId=IgniteTests24Java8_RunAll]
> Binary mode for Ignite Set
> --
>
> Key: IGNITE-11397
> URL: https://issues.apache.org/jira/browse/IGNITE-11397
> Project: Ignite
> Issue Type: New Feature
> Components: binary, data structures
>Reporter: Uday Kale
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add binary mode (withKeepBinary) to Data Structures Set.
> This will allow retrieving values in binary format when needed or when class
> is not available, and will allow implementing the structures in other
> platforms (.NET, C++).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795270#comment-16795270
]
Roman Kondakov commented on IGNITE-11548:
-
[~amashenkov], tests look good. Six runs of six without timeout (see my
previous comment). Please, review the patch.
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795227#comment-16795227
]
Roman Kondakov commented on IGNITE-11548:
-
Waiting for massive run results:
[https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=pull%2F6291%2Fhead=buildTypeStatusDiv]
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11482) MVCC: Error on TxLog initialization.
[
https://issues.apache.org/jira/browse/IGNITE-11482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795198#comment-16795198
]
Roman Kondakov commented on IGNITE-11482:
-
[~amashenkov], patch looks good for me.
> MVCC: Error on TxLog initialization.
>
>
> Key: IGNITE-11482
> URL: https://issues.apache.org/jira/browse/IGNITE-11482
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: mvcc_stability
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some [tests remained
> flaky|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-935846982857542309=TEST_STATUS_DESC=50_IgniteTests24Java8=__all_branches__]
> even after IGNITE-10582 has been fixed. It should be investigated again.
> {noformat}
> [21:44:14] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true, false, false,
> false]]class org.apache.ignite.IgniteCheckedException: Failed to complete
> exchange process.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3209)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3237)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3323)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3304)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1519)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:852)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2920)
> 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:748)
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to
> initialize exchange locally [locNodeId=140a9253-f646-4691-9947-2b211a90]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1254)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:782)
> ... 4 more
> Caused by: java.lang.IllegalStateException: Failed to get page IO
> instance (page content is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:181)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:57)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.init(TxLog.java:161)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.(TxLog.java:87)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.ensureStarted(MvccProcessorImpl.java:302)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1552)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:2325)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$null$6a5b31b9$1(GridCacheProcessor.java:2164)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCachesIfPossible$6(GridCacheProcessor.java:2104)
> at
>
[jira] [Commented] (IGNITE-8550) CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also return 2 or 0
[
https://issues.apache.org/jira/browse/IGNITE-8550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795217#comment-16795217
]
Ilya Kasnacheev commented on IGNITE-8550:
-
[~smoldachev] I think it's too much of a change that we ignore the result of
'0', since it would usually mean a serious data inconsistency (I guess).
Do you have any ideas how this can be mitigated? Maybe throttle those messages
instead of just ignoring this condition?
> CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also
> return 2 or 0
>
>
> Key: IGNITE-8550
> URL: https://issues.apache.org/jira/browse/IGNITE-8550
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Stanislav Lukyanov
>Assignee: Moldachev Sergey
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> CacheAbstractJdbcStore.write attempts to execute a merge update if it is
> available, and expects the merge to always return 1 (as the number of updated
> entries is always 1).
> However, MySQL's `INSERT ... ON DUPLICATE KEY UPDATE`
> (https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html) may return
> 0 or 2, depending on what was updated:
> {quote}With ON DUPLICATE KEY UPDATE, the affected-rows value per row is 1 if
> the row is inserted as a new row, 2 if an existing row is updated, and 0 if
> an existing row is set to its current values.{quote}
> Because of that, CacheAbstractJdbcStore may report a false warning.
> Need to consider either removing the warning or special-case the MySQL
> dialect to allow to return values other than 1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795224#comment-16795224
]
Ignite TC Bot commented on IGNITE-11548:
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3344934buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11215) MVCC: JVM crash in MVCC PDS 1 suite
[
https://issues.apache.org/jira/browse/IGNITE-11215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795210#comment-16795210
]
Roman Kondakov commented on IGNITE-11215:
-
[~amashenkov], patch looks good for me.
> MVCC: JVM crash in MVCC PDS 1 suite
> ---
>
> Key: IGNITE-11215
> URL: https://issues.apache.org/jira/browse/IGNITE-11215
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Critical
> Labels: mvcc_stability
> Fix For: 2.8
>
> Attachments: No_C2_opts_hs_err_pid957384.log, hs_err_pid429215.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes JVM crash
> [occurs|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds1_IgniteTests24Java8=%3Cdefault%3E=buildTypeHistoryList=failed]
> in {{vacuum-cleaner}} thread in {{ExplicitWalDeltaConsistencyTest}}.
> See attached crash report.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795199#comment-16795199 ] Andrew Mashenkov commented on IGNITE-7718: -- [~pvinokurov], Please, resolve conflicts against latest master and re-run TC to get Bot's visa. > Collections.singleton() and Collections.singletonMap() are not properly > serialized by binary marshaller > --- > > Key: IGNITE-7718 > URL: https://issues.apache.org/jira/browse/IGNITE-7718 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > > After desialization collections obtained by Collections.singleton() and > Collections.singletonMap() does not return collection of binary objects, but > rather collection of deserialized objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10476) Merge similar tests.
[ https://issues.apache.org/jira/browse/IGNITE-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795187#comment-16795187 ] Alexey Goncharuk commented on IGNITE-10476: --- Thanks, merged to master. > Merge similar tests. > > > Key: IGNITE-10476 > URL: https://issues.apache.org/jira/browse/IGNITE-10476 > Project: Ignite > Issue Type: Test >Reporter: Andrew Mashenkov >Assignee: Andrey Kalinin >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > CacheNamesSelfTest and CacheNamesWithSpecialCharactersTest looks similar and > can be merged. > We already have test suite these tests are related to, so we can merge them > into GridCacheConfigurationValidationSelfTest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10476) Merge similar tests.
[ https://issues.apache.org/jira/browse/IGNITE-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10476: -- Fix Version/s: 2.8 > Merge similar tests. > > > Key: IGNITE-10476 > URL: https://issues.apache.org/jira/browse/IGNITE-10476 > Project: Ignite > Issue Type: Test >Reporter: Andrew Mashenkov >Assignee: Andrey Kalinin >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > CacheNamesSelfTest and CacheNamesWithSpecialCharactersTest looks similar and > can be merged. > We already have test suite these tests are related to, so we can merge them > into GridCacheConfigurationValidationSelfTest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-11432) Add ability to specify auto-generated consistent ID in IgniteConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11432:
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3314121]]
* exe: BinaryStringTest.TestNewMode - 0,0% fails in last 379 master runs.
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3314040]]
* IgniteStandByClusterSuite:
IgniteClusterActivateDeactivateTest.testDeactivateFailover3 - 0,0% fails in
last 322 master runs.
{color:#d04437}MVCC PDS 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3314147]]
{color:#d04437}Client Nodes{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3314041]]
* IgniteClientConnectAfterCommunicationFailureTest.testClientReconnects (last
started)
{color:#d04437}Platform C++ (Linux){color} [[tests 500 JVM CRASH , Exit Code ,
Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3314075]]
* IgniteOdbcTest: SslQueriesTestSuite: TestConnectionSslSuccess - 1,2% fails in
last 505 master runs.
*
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3314391buildTypeId=IgniteTests24Java8_RunAll])
> Add ability to specify auto-generated consistent ID in IgniteConfiguration
> --
>
> Key: IGNITE-11432
> URL: https://issues.apache.org/jira/browse/IGNITE-11432
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Let's consider the following scenario:
> 1) A user starts an empty node, the node generates a consistent ID as UUID
> and creates a persistence folder {{node00-UUID}}
> 2) If a user cleans up the persistence directory, the node will generate
> another consistent ID.
> Now, the user has no option to specify the old consistent ID in
> configuration: if we set the conistent ID to the UUD, the persistece folder
> will be named {{UUID}}. If the user specifies {{node00-UUID}}, the folder
> will be named properly, but the actual consistent ID will be {{node00-UUID}}.
> We need to add an option to specify the proper consistent ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-11432) Add ability to specify auto-generated consistent ID in IgniteConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11432:
Comment: was deleted
(was: {panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3321594]]
* IgniteStandByClusterSuite:
IgniteClusterActivateDeactivateTest.testActivateFailover2 - 0,0% fails in last
333 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3314391buildTypeId=IgniteTests24Java8_RunAll])
> Add ability to specify auto-generated consistent ID in IgniteConfiguration
> --
>
> Key: IGNITE-11432
> URL: https://issues.apache.org/jira/browse/IGNITE-11432
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Let's consider the following scenario:
> 1) A user starts an empty node, the node generates a consistent ID as UUID
> and creates a persistence folder {{node00-UUID}}
> 2) If a user cleans up the persistence directory, the node will generate
> another consistent ID.
> Now, the user has no option to specify the old consistent ID in
> configuration: if we set the conistent ID to the UUD, the persistece folder
> will be named {{UUID}}. If the user specifies {{node00-UUID}}, the folder
> will be named properly, but the actual consistent ID will be {{node00-UUID}}.
> We need to add an option to specify the proper consistent ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7538) Update several maven plugins version for Java 9 compilation
[ https://issues.apache.org/jira/browse/IGNITE-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795160#comment-16795160 ] Dmitriy Pavlov commented on IGNITE-7538: [~vveider] please chime in ^ > Update several maven plugins version for Java 9 compilation > --- > > Key: IGNITE-7538 > URL: https://issues.apache.org/jira/browse/IGNITE-7538 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > * rat plugin > * flat plugin > * java plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795146#comment-16795146 ] Pavel Vinokurov commented on IGNITE-7718: - [~amashenkov] Please review > Collections.singleton() and Collections.singletonMap() are not properly > serialized by binary marshaller > --- > > Key: IGNITE-7718 > URL: https://issues.apache.org/jira/browse/IGNITE-7718 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > > After desialization collections obtained by Collections.singleton() and > Collections.singletonMap() does not return collection of binary objects, but > rather collection of deserialized objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11432) Add ability to specify auto-generated consistent ID in IgniteConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-11432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11432:
Fix Version/s: 2.8
> Add ability to specify auto-generated consistent ID in IgniteConfiguration
> --
>
> Key: IGNITE-11432
> URL: https://issues.apache.org/jira/browse/IGNITE-11432
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Let's consider the following scenario:
> 1) A user starts an empty node, the node generates a consistent ID as UUID
> and creates a persistence folder {{node00-UUID}}
> 2) If a user cleans up the persistence directory, the node will generate
> another consistent ID.
> Now, the user has no option to specify the old consistent ID in
> configuration: if we set the conistent ID to the UUD, the persistece folder
> will be named {{UUID}}. If the user specifies {{node00-UUID}}, the folder
> will be named properly, but the actual consistent ID will be {{node00-UUID}}.
> We need to add an option to specify the proper consistent ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11537) SQL: enchanced log mode for SQL queries
[ https://issues.apache.org/jira/browse/IGNITE-11537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795104#comment-16795104 ] Alexei Scherbakov commented on IGNITE-11537: [~tledkov-gridgain], I think it's also be useful to measure amount of bytes read by query both from memory and from disk, if a page is missing in pagecache. > SQL: enchanced log mode for SQL queries > --- > > Key: IGNITE-11537 > URL: https://issues.apache.org/jira/browse/IGNITE-11537 > Project: Ignite > Issue Type: Task >Reporter: Taras Ledkov >Priority: Major > > Additional information about run queries are needed: > - log each query start execution on H2 engine includes local queries and map > parts of distributed query (needs to monitoring node SQL pressure); > - EXPLAIN / ANALYZE for long running queries; > - ResultSet cardinality for long running queries (e.g. by threshold); > Enable / disable enhanced log mode may be managed by JMX, internal SQL > command or other way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11091: Fix Version/s: (was: 2.7) 2.8 > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11524) Memory leak caused by executing a jdbc prepared statement
[
https://issues.apache.org/jira/browse/IGNITE-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795035#comment-16795035
]
Taras Ledkov edited comment on IGNITE-11524 at 3/18/19 1:59 PM:
[~vozerov]
1. Fixed,
2. {{JdbcThinConnection#stmts}} is cleared on close. I guess the statements
shouldn't close explicitly on connection close:
- The object on server side are cleared by {{onDisconnect}}.
- On client side {{JdbcThinStatement#isClosed}} check connection state.
- It takes additional time on close to send not useful close commands.
I guess clear {{JdbcThinConnection#stmts}} is enough for decrease memory
pressure when {{JdbcThinConnection}}s leak at user code.
We have to nullify the content of the {{JdbcThinStatement}} to reduce memory
pressure when {{JdbcThinStatement}}s leak at user code.
was (Author: tledkov-gridgain):
[~vozerov]
1. Fixed,
2. {{JdbcThinConnection#stmts}} is cleared on close. I guess the statements
shouldn't close explicitly on connection close:
- The object on server side are cleared by {{onDisconnect}}.
- On client side {{JdbcThinStatement#isClosed}} check connection state.
I guess clear {{JdbcThinConnection#stmts}} is enough for decrease memory
pressure when {{JdbcThinConnection}}s leak at user code.
We have to nullify the content of the {{JdbcThinStatement}} to reduce memory
pressure when {{JdbcThinStatement}}s leak at user code.
> Memory leak caused by executing a jdbc prepared statement
> -
>
> Key: IGNITE-11524
> URL: https://issues.apache.org/jira/browse/IGNITE-11524
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Reporter: Pavel Vinokurov
>Assignee: Taras Ledkov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: PreparedStatementOOMReproducer.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Executing a prepared statement multiple times lead to OOM.
> VisualVM indicates that heap contains a lot of JdbcThinPreparedStatament
> objects.
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11396) Actualize JUnit3TestLegacyAssert
[ https://issues.apache.org/jira/browse/IGNITE-11396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11396: Fix Version/s: 2.8 > Actualize JUnit3TestLegacyAssert > > > Key: IGNITE-11396 > URL: https://issues.apache.org/jira/browse/IGNITE-11396 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: iep-30 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Rename JUnit3TestLegacyAssert class and actualize methods. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11562) Critical failure on stopping client node
Ryabov Dmitrii created IGNITE-11562:
---
Summary: Critical failure on stopping client node
Key: IGNITE-11562
URL: https://issues.apache.org/jira/browse/IGNITE-11562
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Ryabov Dmitrii
Critical failure in
{{IgniteAbstractDynamicCacheStartFailTest#testBrokenAffinityFunStartOnServerFailedOnClient()}}
is ignored because of no-op failure handler.
{code:java}
[2019-03-18
16:26:26,953][ERROR][exchange-worker-#210%clienttestBrokenAffinityFunStartOnServerFailedOnClient%][GridCachePartitionExchangeManager]
Failed to wait for completion of partition map exchange (preloading will not
start): GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryCustomEvent
[customMsg=null, affTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=b9afbb48-3396-4ca6-b714-d2aa4e90,
consistentId=53086654-443a-44ab-88e3-a4d4f50d2477, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1552915586426, loc=false, ver=2.7.0#20190318-sha1:,
isClient=false], topVer=4, nodeId8=7355a5c6, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1552915586506]], crd=TcpDiscoveryNode
[id=b9afbb48-3396-4ca6-b714-d2aa4e90,
consistentId=53086654-443a-44ab-88e3-a4d4f50d2477, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1552915586426, loc=false, ver=2.7.0#20190318-sha1:,
isClient=false], exchId=GridDhtPartitionExchangeId
[topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
discoEvt=DiscoveryCustomEvent [customMsg=null,
affTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=b9afbb48-3396-4ca6-b714-d2aa4e90,
consistentId=53086654-443a-44ab-88e3-a4d4f50d2477, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1552915586426, loc=false, ver=2.7.0#20190318-sha1:,
isClient=false], topVer=4, nodeId8=7355a5c6, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1552915586506]], nodeId=b9afbb48,
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter
[ignoreInterrupts=false, state=DONE, res=true, hash=731087400], init=true,
lastVer=null, partReleaseFut=null, exchActions=ExchangeActions
[startCaches=[TestDynamicCache-server-1], stopCaches=null,
startGrps=[TestDynamicCache-server-1], stopGrps=[], resetParts=null,
stateChangeRequest=null], affChangeMsg=null, initTs=1552915586506,
centralizedAff=false, forceAffReassignment=false, exchangeLocE=class
o.a.i.IgniteCheckedException: Failed to initialize exchange locally
[locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96],
cacheChangeFailureMsgSent=false, done=true, state=DONE,
registerCachesFuture=null, partitionsSent=false, partitionsReceived=false,
delayedLatestMsg=null, afterLsnrCompleteFut=GridFutureAdapter
[ignoreInterrupts=false, state=DONE, res=null, hash=1846768135],
timeBag=o.a.i.i.util.TimeBag@7682124a, startTime=20675138215608, evtLatch=0,
remaining=HashSet [7b53fbf7-537c-451a-b939-7099f492,
d63e4f5f-83b7-4449-8067-8d51bca1, b9afbb48-3396-4ca6-b714-d2aa4e90],
mergedJoinExchMsgs=null, super=GridFutureAdapter [ignoreInterrupts=false,
state=DONE, res=class o.a.i.IgniteCheckedException: Failed to initialize
exchange locally [locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96],
hash=1196794290]]
class org.apache.ignite.IgniteCheckedException: Failed to initialize exchange
locally [locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:782)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2920)
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:748)
Caused by: java.lang.IllegalStateException: Simulated exception
[locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96]
at
org.apache.ignite.internal.processors.cache.IgniteAbstractDynamicCacheStartFailTest$BrokenAffinityFunction.assignPartitions(IgniteAbstractDynamicCacheStartFailTest.java:920)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.calculate(GridAffinityAssignmentCache.java:369
[jira] [Commented] (IGNITE-11524) Memory leak caused by executing a jdbc prepared statement
[
https://issues.apache.org/jira/browse/IGNITE-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795035#comment-16795035
]
Taras Ledkov commented on IGNITE-11524:
---
[~vozerov]
1. Fixed,
2. {{JdbcThinConnection#stmts}} is cleared on close. I guess the statements
shouldn't close explicitly on connection close:
- The object on server side are cleared by {{onDisconnect}}.
- On client side {{JdbcThinStatement#isClosed}} check connection state.
I guess clear {{JdbcThinConnection#stmts}} is enough for decrease memory
pressure when {{JdbcThinConnection}}s leak at user code.
We have to nullify the content of the {{JdbcThinStatement}} to reduce memory
pressure when {{JdbcThinStatement}}s leak at user code.
> Memory leak caused by executing a jdbc prepared statement
> -
>
> Key: IGNITE-11524
> URL: https://issues.apache.org/jira/browse/IGNITE-11524
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Reporter: Pavel Vinokurov
>Assignee: Taras Ledkov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: PreparedStatementOOMReproducer.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Executing a prepared statement multiple times lead to OOM.
> VisualVM indicates that heap contains a lot of JdbcThinPreparedStatament
> objects.
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795024#comment-16795024
]
Roman Kondakov edited comment on IGNITE-11548 at 3/18/19 1:50 PM:
--
It seems the problem was in ignoring pending acknowledgement futures in
{{MvccProcessorImpl}} on node stop. When node is stopped, the client thread may
be waiting on this future forever because nothing can resolve it.
The solution is to cleanup and resolve pending futures on node stop.
was (Author: rkondakov):
It seems the problem was in ignoring pending acknowledge futures in
{{MvccProcessorImpl}} on node stop. When node is stopped, the client thread may
be waiting on this future forever because nothing can resolve it.
The solution is to cleanup and resolve pending futures on node stop.
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11524) Memory leak caused by executing a jdbc prepared statement
[
https://issues.apache.org/jira/browse/IGNITE-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795030#comment-16795030
]
Ignite TC Bot commented on IGNITE-11524:
{panel:title=- Run :: SQL: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: SQL*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3322922buildTypeId=IgniteTests24Java8_RunAllSql]
> Memory leak caused by executing a jdbc prepared statement
> -
>
> Key: IGNITE-11524
> URL: https://issues.apache.org/jira/browse/IGNITE-11524
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
>Reporter: Pavel Vinokurov
>Assignee: Taras Ledkov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: PreparedStatementOOMReproducer.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Executing a prepared statement multiple times lead to OOM.
> VisualVM indicates that heap contains a lot of JdbcThinPreparedStatament
> objects.
> The reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795024#comment-16795024
]
Roman Kondakov edited comment on IGNITE-11548 at 3/18/19 1:45 PM:
--
It seems the problem was in ignoring pending acknowledge futures in
{{MvccProcessorImpl}} on node stop. When node is stopped, the client thread may
be waiting on this future forever because nothing can resolve it.
The solution is to cleanup and resolve pending futures on node stop.
was (Author: rkondakov):
It seems the problem was in ignoring pending acknowledge futures in
{{MvccProcessorImpl}} on node stop. When node is stopped, the client thread may
be waiting on this future forever because nothing is resolve it.
The solution is to cleanup and resolve pending futures on node stop.
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795024#comment-16795024
]
Roman Kondakov commented on IGNITE-11548:
-
It seems the problem was in ignoring pending acknowledge futures in
{{MvccProcessorImpl}} on node stop. When node is stopped, the client thread may
be waiting on this future forever because nothing is resolve it.
The solution is to cleanup and resolve pending futures on node stop.
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-11548:
Summary: MVCC: MVCC PDS 2 suite became unstable after the get operation
mapping fix (was: Problems with transaction finish in some cases)
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov reassigned IGNITE-11548:
---
Assignee: Roman Kondakov
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11371) Cache get operation with readThrough returns null if remove is performed concurrently
[
https://issues.apache.org/jira/browse/IGNITE-11371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11371:
--
Fix Version/s: 2.8
> Cache get operation with readThrough returns null if remove is performed
> concurrently
> -
>
> Key: IGNITE-11371
> URL: https://issues.apache.org/jira/browse/IGNITE-11371
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8, 2.5, 2.7
>Reporter: Denis Mekhanikov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8
>
> Attachments: IgniteInvalidationNullRunner.java
>
>
> Consider a situation, when you have a cache with {{CacheStore}} and
> {{readThrough}} configured.
> One may expect, that {{IgniteCache#get(...)}} operation will never return
> {{null}} for keys, that are present in the underlying {{CacheStore}}. But
> actually it's possible to get {{null}} in case if remove operation is called
> on the same key while {{CacheStore#load}} is running.
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11561) [ML] IgniteDistributedModel for XGBoost doesn't work in example
[ https://issues.apache.org/jira/browse/IGNITE-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-11561: Affects Version/s: (was: 2.7) > [ML] IgniteDistributedModel for XGBoost doesn't work in example > --- > > Key: IGNITE-11561 > URL: https://issues.apache.org/jira/browse/IGNITE-11561 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Alexey Platonov >Assignee: Anton Dmitriev >Priority: Major > Labels: stability > Time Spent: 10m > Remaining Estimate: 0h > > Distributed inference model for XGBoost doesn't work in example > (XGBoostModelParserExample). It always returns same value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
[
https://issues.apache.org/jira/browse/IGNITE-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794988#comment-16794988
]
Ignite TC Bot commented on IGNITE-11557:
{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=3342581buildTypeId=IgniteTests24Java8_RunAll]
> flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
> --
>
> Key: IGNITE-11557
> URL: https://issues.apache.org/jira/browse/IGNITE-11557
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 1.8
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> test failed with the following trace
> _[2019-03-18
> 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor]
> Failed to execute local query. class
> org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
> Exception calling user-defined function: "can_fail(): null"; SQL statement:
> SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND
> sleep()>0 AND can_fail()=0 [90105-197] at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102)
> at
> org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121)
> at
> org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349)
> at
> org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317)
> at
> org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347)
> 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$7.run(GridAbstractTest.java:2107)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> org.h2.jdbc.JdbcSQLException: Exception calling user-defined function:
> "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM
> "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at
> org.h2.message.DbException.get(DbException.java:168) at
>
[jira] [Updated] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
[ https://issues.apache.org/jira/browse/IGNITE-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11557: --- Ignite Flags: (was: Docs Required) > flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes > -- > > Key: IGNITE-11557 > URL: https://issues.apache.org/jira/browse/IGNITE-11557 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 1.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > test failed with the following trace > _[2019-03-18 > 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor] > Failed to execute local query. class > org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. > Exception calling user-defined function: "can_fail(): null"; SQL statement: > SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND > sleep()>0 AND can_fail()=0 [90105-197] at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161) > at > org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102) > at > org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349) > at > org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347) > 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$7.run(GridAbstractTest.java:2107) > at java.lang.Thread.run(Thread.java:748) Caused by: > org.h2.jdbc.JdbcSQLException: Exception calling user-defined function: > "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM > "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at > org.h2.message.DbException.get(DbException.java:168) at > org.h2.message.DbException.convertInvocation(DbException.java:324) at > org.h2.engine.FunctionAlias$JavaMethod.getValue(FunctionAlias.java:468) at > org.h2.expression.JavaFunction.getValue(JavaFunction.java:38) at >
[jira] [Resolved] (IGNITE-11476) [ML] Use new feature extraction API in examples
[ https://issues.apache.org/jira/browse/IGNITE-11476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov resolved IGNITE-11476. -- Resolution: Fixed > [ML] Use new feature extraction API in examples > --- > > Key: IGNITE-11476 > URL: https://issues.apache.org/jira/browse/IGNITE-11476 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Platonov >Assignee: Alexey Platonov >Priority: Critical > Labels: stability > > Introduce new feature/label extraction API to all examples. These examples > should work on binary builds without sharing additional jars to libs > directory (except ml-jar). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling
[
https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794973#comment-16794973
]
Ivan Pavlukhin commented on IGNITE-11356:
-
[~ilyak], I created PR with a single squashed commit. Please take a look
https://github.com/apache/ignite/pull/6288/commits
> Test framework: Remove custom assumption exceptions handling
>
>
> Key: IGNITE-11356
> URL: https://issues.apache.org/jira/browse/IGNITE-11356
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be
> removed. Currently with custom handling tests with unmet assumptions are
> marked as passed. With default handling failed assumptions on instance level
> mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look
> perfect. But with custom handling a particular test is not included into TC
> report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11371) Cache get operation with readThrough returns null if remove is performed concurrently
[
https://issues.apache.org/jira/browse/IGNITE-11371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk reassigned IGNITE-11371:
-
Assignee: Alexey Goncharuk
> Cache get operation with readThrough returns null if remove is performed
> concurrently
> -
>
> Key: IGNITE-11371
> URL: https://issues.apache.org/jira/browse/IGNITE-11371
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8, 2.5, 2.7
>Reporter: Denis Mekhanikov
>Assignee: Alexey Goncharuk
>Priority: Major
> Attachments: IgniteInvalidationNullRunner.java
>
>
> Consider a situation, when you have a cache with {{CacheStore}} and
> {{readThrough}} configured.
> One may expect, that {{IgniteCache#get(...)}} operation will never return
> {{null}} for keys, that are present in the underlying {{CacheStore}}. But
> actually it's possible to get {{null}} in case if remove operation is called
> on the same key while {{CacheStore#load}} is running.
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11561) [ML] IgniteDistributedModel for XGBoost doesn't work in example
[ https://issues.apache.org/jira/browse/IGNITE-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov updated IGNITE-11561: - Labels: stability (was: ) > [ML] IgniteDistributedModel for XGBoost doesn't work in example > --- > > Key: IGNITE-11561 > URL: https://issues.apache.org/jira/browse/IGNITE-11561 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.7, 2.8 >Reporter: Alexey Platonov >Assignee: Anton Dmitriev >Priority: Major > Labels: stability > > Distributed inference model for XGBoost doesn't work in example > (XGBoostModelParserExample). It always returns same value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11560) @WithSystemProperty annotation breaks some existing tests.
[ https://issues.apache.org/jira/browse/IGNITE-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11560: Fix Version/s: 2.8 > @WithSystemProperty annotation breaks some existing tests. > -- > > Key: IGNITE-11560 > URL: https://issues.apache.org/jira/browse/IGNITE-11560 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4555192785549771867=%3Cdefault%3E=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-11548:
Priority: Critical (was: Major)
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11548) Problems with transaction finish in some cases
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-11548:
Summary: Problems with transaction finish in some cases (was: MVCC: MVCC
PDS 2 suite became unstable after the get operation mapping fix)
> Problems with transaction finish in some cases
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11548) MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
[
https://issues.apache.org/jira/browse/IGNITE-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov reassigned IGNITE-11548:
---
Assignee: (was: Roman Kondakov)
> MVCC: MVCC PDS 2 suite became unstable after the get operation mapping fix
> --
>
> Key: IGNITE-11548
> URL: https://issues.apache.org/jira/browse/IGNITE-11548
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Critical
> Fix For: 2.8
>
>
> It looks like {{MVCC PDS 2}} suite became unstable after IGNITE-10261 is
> merged to master. It should be investigated.
> TC run:
> [https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds2_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11561) [ML] IgniteDistributedModel for XGBoost doesn't work in example
Alexey Platonov created IGNITE-11561: Summary: [ML] IgniteDistributedModel for XGBoost doesn't work in example Key: IGNITE-11561 URL: https://issues.apache.org/jira/browse/IGNITE-11561 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.7, 2.8 Reporter: Alexey Platonov Assignee: Anton Dmitriev Distributed inference model for XGBoost doesn't work in example (XGBoostModelParserExample). It always returns same value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11373) varchar_ignorecase doesn't work properly
[
https://issues.apache.org/jira/browse/IGNITE-11373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794955#comment-16794955
]
Taras Ledkov edited comment on IGNITE-11373 at 3/18/19 12:03 PM:
-
*Root cause:*
The type of column is lost between parsed {{CreateTableData}} and real data
generated at the node on
{{GridDhtPartitionsExchangeFuture#onCacheChangeRequest -> .. ->
GridCacheProcessor#prepareStartCaches -> .. -> IgniteH2Indexing#registerType
-> .. -> H2TableEngine#createTable}}.
We have to hold information about {{IGNORECASE}} and the {{QueryEntity}} and
and pass by {{QueryTypeDescriptorImpl}} to the created table {{GridH2Table}}
was (Author: tledkov-gridgain):
*Root cause:*
The type of column is lost between parsed {{CreateTableData}} and real data
generated ant the node on
{{GridDhtPartitionsExchangeFuture#onCacheChangeRequest -> .. ->
GridCacheProcessor#prepareStartCaches -> .. -> IgniteH2Indexing#registerType
-> .. -> H2TableEngine#createTable}}.
We have to hold information about {{IGNORECASE}} and the {{QueryEntity}} and
and pass by {{QueryTypeDescriptorImpl}} to the created table {{GridH2Table}}
> varchar_ignorecase doesn't work properly
>
>
> Key: IGNITE-11373
> URL: https://issues.apache.org/jira/browse/IGNITE-11373
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Evgenii Zhuravlev
>Priority: Major
>
> Looks like a field with type varchar_ignorecase can't be used for filtering
> the values for different cases.
> {code:java}
> Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
>
> IgniteCache cache = ignite.getOrCreateCache("TEST");
> cache.query(new SqlFieldsQuery("CREATE TABLE IF NOT EXISTS TEST\n" +
> "(\n" +
> " TEST_IDNUMBER(15)NOT NULL,\n" +
> " TEST_VALUE VARCHAR_IGNORECASE(100),\n" +
> " PRIMARY KEY (TEST_ID)\n" +
> ") "));
> System.out.println("INSERTED:" + ignite.cache("TEST").query(new
> SqlFieldsQuery("INSERT INTO TEST values (1,'aAa')")).getAll().size());
> System.out.println("FOUND:" + ignite.cache("TEST").query(new
> SqlFieldsQuery("Select * from TEST where TEST_VALUE like
> '%aaa%'")).getAll().size());
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11373) varchar_ignorecase doesn't work properly
[
https://issues.apache.org/jira/browse/IGNITE-11373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794955#comment-16794955
]
Taras Ledkov commented on IGNITE-11373:
---
*Root cause:*
The type of column is lost between parsed {{CreateTableData}} and real data
generated ant the node on
{{GridDhtPartitionsExchangeFuture#onCacheChangeRequest -> .. ->
GridCacheProcessor#prepareStartCaches -> .. -> IgniteH2Indexing#registerType
-> .. -> H2TableEngine#createTable}}.
We have to hold information about {{IGNORECASE}} and the {{QueryEntity}} and
and pass by {{QueryTypeDescriptorImpl}} to the created table {{GridH2Table}}
> varchar_ignorecase doesn't work properly
>
>
> Key: IGNITE-11373
> URL: https://issues.apache.org/jira/browse/IGNITE-11373
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Evgenii Zhuravlev
>Priority: Major
>
> Looks like a field with type varchar_ignorecase can't be used for filtering
> the values for different cases.
> {code:java}
> Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
>
> IgniteCache cache = ignite.getOrCreateCache("TEST");
> cache.query(new SqlFieldsQuery("CREATE TABLE IF NOT EXISTS TEST\n" +
> "(\n" +
> " TEST_IDNUMBER(15)NOT NULL,\n" +
> " TEST_VALUE VARCHAR_IGNORECASE(100),\n" +
> " PRIMARY KEY (TEST_ID)\n" +
> ") "));
> System.out.println("INSERTED:" + ignite.cache("TEST").query(new
> SqlFieldsQuery("INSERT INTO TEST values (1,'aAa')")).getAll().size());
> System.out.println("FOUND:" + ignite.cache("TEST").query(new
> SqlFieldsQuery("Select * from TEST where TEST_VALUE like
> '%aaa%'")).getAll().size());
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11323) Reduce boilerplate "System.setProperty" code in tests
[
https://issues.apache.org/jira/browse/IGNITE-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794961#comment-16794961
]
Ivan Bessonov commented on IGNITE-11323:
Related fix is in IGNITE-11323
> Reduce boilerplate "System.setProperty" code in tests
> -
>
> Key: IGNITE-11323
> URL: https://issues.apache.org/jira/browse/IGNITE-11323
> Project: Ignite
> Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are many examples in tests where some property gets new value in
> "beforeTestsStarted"/"beforeTest"/"beginning of test method" and then gets
> its previous value in "afterTestsStopped"/"afterTest"/"finally block of test
> method". This approach leads to excessive code that can be avoided.
> I suggest implementing annotation "WithSystemProperty" (name is the subject
> to discussion) that will allow us to write this:
> {code:java}
> @Test
> @WithSystemProperty(key = IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, value
> = "true")
> public void testSkipCheckConsistencyFlagEnabled() throws Exception {
> ...
> }
> {code}
> instead of this:
> {code:java}
> @Test
> public void testSkipCheckConsistencyFlagEnabled() throws Exception {
> String backup =
> System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, "true");
> try {
> ...
> }
> finally {
> if (backup != null)
> System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK,
> backup);
> else
> System.clearProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK);
> }
> }
> {code}
>
> There also has to be ability to use this annotation on test class so new
> value of system properties will be used in all of its test methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11323) Reduce boilerplate "System.setProperty" code in tests
[
https://issues.apache.org/jira/browse/IGNITE-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794961#comment-16794961
]
Ivan Bessonov edited comment on IGNITE-11323 at 3/18/19 12:01 PM:
--
Related fix is in IGNITE-11560
was (Author: ibessonov):
Related fix is in IGNITE-11323
> Reduce boilerplate "System.setProperty" code in tests
> -
>
> Key: IGNITE-11323
> URL: https://issues.apache.org/jira/browse/IGNITE-11323
> Project: Ignite
> Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are many examples in tests where some property gets new value in
> "beforeTestsStarted"/"beforeTest"/"beginning of test method" and then gets
> its previous value in "afterTestsStopped"/"afterTest"/"finally block of test
> method". This approach leads to excessive code that can be avoided.
> I suggest implementing annotation "WithSystemProperty" (name is the subject
> to discussion) that will allow us to write this:
> {code:java}
> @Test
> @WithSystemProperty(key = IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, value
> = "true")
> public void testSkipCheckConsistencyFlagEnabled() throws Exception {
> ...
> }
> {code}
> instead of this:
> {code:java}
> @Test
> public void testSkipCheckConsistencyFlagEnabled() throws Exception {
> String backup =
> System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, "true");
> try {
> ...
> }
> finally {
> if (backup != null)
> System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK,
> backup);
> else
> System.clearProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK);
> }
> }
> {code}
>
> There also has to be ability to use this annotation on test class so new
> value of system properties will be used in all of its test methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11560) @WithSystemProperty annotation breaks some existing tests.
Ivan Bessonov created IGNITE-11560: -- Summary: @WithSystemProperty annotation breaks some existing tests. Key: IGNITE-11560 URL: https://issues.apache.org/jira/browse/IGNITE-11560 Project: Ignite Issue Type: Bug Reporter: Ivan Bessonov Assignee: Ivan Bessonov https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4555192785549771867=%3Cdefault%3E=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling
[
https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794959#comment-16794959
]
Ilya Kasnacheev commented on IGNITE-11356:
--
[~Pavlukhin]
Unfortunately I still get "Could not merge the pull-request to master without
conflicts. " when trying to apply this PR. I'm not an expert on how to make it
work. Maybe create a different PR with squashed commit?
> Test framework: Remove custom assumption exceptions handling
>
>
> Key: IGNITE-11356
> URL: https://issues.apache.org/jira/browse/IGNITE-11356
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be
> removed. Currently with custom handling tests with unmet assumptions are
> marked as passed. With default handling failed assumptions on instance level
> mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look
> perfect. But with custom handling a particular test is not included into TC
> report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9876) .NET: Thin Client: Implement Best Effort Affinity
[ https://issues.apache.org/jira/browse/IGNITE-9876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9876: Component/s: thin client > .NET: Thin Client: Implement Best Effort Affinity > - > > Key: IGNITE-9876 > URL: https://issues.apache.org/jira/browse/IGNITE-9876 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-23 > > Currently we connect to a random node, so when the primary node for the given > key is different from that random node, there is an additional network hop. > For single-key operations (scope of this ticket) we should strive to > determine primary node and connect there directly. > To determine primary node for a given key: > 1. Retrieve partition map from server node (partition -> primaryNodeId) > 2. Connect to all known server nodes (all endpoints from > IgniteClientConfiguration) and get their Node Ids, build a map from endpoint > (IP or host) to Node Id > 3. Implement RendezvousAffinityFunction in C# > Efficient automatic partition map retrieval: > 1. When a partition map is needed, send a separate asynchronous operation > (new server op type is required) > 2. Do not block current user operation. If partition map is not present, just > skip affinity step and use current connection > 3. When response arrives with the partition map, save it with a timestamp > 4. On every partition map access check the timestamp. Request new map if > current map is older than N minutes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
[ https://issues.apache.org/jira/browse/IGNITE-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11557: --- Affects Version/s: 1.8 > flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes > -- > > Key: IGNITE-11557 > URL: https://issues.apache.org/jira/browse/IGNITE-11557 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 1.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > test failed with the following trace > _[2019-03-18 > 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor] > Failed to execute local query. class > org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. > Exception calling user-defined function: "can_fail(): null"; SQL statement: > SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND > sleep()>0 AND can_fail()=0 [90105-197] at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161) > at > org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102) > at > org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349) > at > org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347) > 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$7.run(GridAbstractTest.java:2107) > at java.lang.Thread.run(Thread.java:748) Caused by: > org.h2.jdbc.JdbcSQLException: Exception calling user-defined function: > "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM > "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at > org.h2.message.DbException.get(DbException.java:168) at > org.h2.message.DbException.convertInvocation(DbException.java:324) at > org.h2.engine.FunctionAlias$JavaMethod.getValue(FunctionAlias.java:468) at > org.h2.expression.JavaFunction.getValue(JavaFunction.java:38) at >
[jira] [Updated] (IGNITE-11559) MVCC: Tx hangs on finish if StorageException occurs.
[ https://issues.apache.org/jira/browse/IGNITE-11559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-11559: -- Labels: WAL mvcc_stability transactions (was: hangs mvcc_stability transactions) > MVCC: Tx hangs on finish if StorageException occurs. > > > Key: IGNITE-11559 > URL: https://issues.apache.org/jira/browse/IGNITE-11559 > Project: Ignite > Issue Type: Bug > Components: mvcc, persistence >Reporter: Andrew Mashenkov >Priority: Major > Labels: WAL, mvcc_stability, transactions > > By default non-mvcc transactions don't log their states in WAL log, so tx > rollbacks without hanging as there is nothing to save to WAL or PageMemory. > So, it may be helpful to check case for non-mvcc tx with txState WAL-logging > enabled at first. > When StorageException occurs during any mvcc tx operation enabled, then > storage locks become blocked. Then Ignite try to rollback Tx due to the error > and try to save txState into WAL and TxLog and hangs forever. A thread hangs > awaiting uninterruptibly for next WAL segment or lock released. > Failure handler tries to stop a node and hangs as well. > Looks like we shouldn't wait if kernal context become invalid. > Good startpoint is IgniteWalFlush* tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11559) MVCC: Tx hangs on finish if StorageException occurs.
Andrew Mashenkov created IGNITE-11559: - Summary: MVCC: Tx hangs on finish if StorageException occurs. Key: IGNITE-11559 URL: https://issues.apache.org/jira/browse/IGNITE-11559 Project: Ignite Issue Type: Bug Components: mvcc, persistence Reporter: Andrew Mashenkov By default non-mvcc transactions don't log their states in WAL log, so tx rollbacks without hanging as there is nothing to save to WAL or PageMemory. So, it may be helpful to check case for non-mvcc tx with txState WAL-logging enabled at first. When StorageException occurs during any mvcc tx operation enabled, then storage locks become blocked. Then Ignite try to rollback Tx due to the error and try to save txState into WAL and TxLog and hangs forever. A thread hangs awaiting uninterruptibly for next WAL segment or lock released. Failure handler tries to stop a node and hangs as well. Looks like we shouldn't wait if kernal context become invalid. Good startpoint is IgniteWalFlush* tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
[ https://issues.apache.org/jira/browse/IGNITE-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-11557: --- Component/s: sql > flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes > -- > > Key: IGNITE-11557 > URL: https://issues.apache.org/jira/browse/IGNITE-11557 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > test failed with the following trace > _[2019-03-18 > 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor] > Failed to execute local query. class > org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. > Exception calling user-defined function: "can_fail(): null"; SQL statement: > SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND > sleep()>0 AND can_fail()=0 [90105-197] at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161) > at > org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102) > at > org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349) > at > org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347) > 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$7.run(GridAbstractTest.java:2107) > at java.lang.Thread.run(Thread.java:748) Caused by: > org.h2.jdbc.JdbcSQLException: Exception calling user-defined function: > "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM > "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at > org.h2.message.DbException.get(DbException.java:168) at > org.h2.message.DbException.convertInvocation(DbException.java:324) at > org.h2.engine.FunctionAlias$JavaMethod.getValue(FunctionAlias.java:468) at > org.h2.expression.JavaFunction.getValue(JavaFunction.java:38) at > org.h2.expression.Comparison.getValue(Comparison.java:239) at >
[jira] [Assigned] (IGNITE-10797) Remove unused methods from IgniteCacheSnapshotManager.
[ https://issues.apache.org/jira/browse/IGNITE-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-10797: --- Assignee: Andrey Kalinin (was: Stanilovsky Evgeny) > Remove unused methods from IgniteCacheSnapshotManager. > -- > > Key: IGNITE-10797 > URL: https://issues.apache.org/jira/browse/IGNITE-10797 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Andrey Kalinin >Priority: Major > Fix For: 2.8 > > > Remove unused methods: > IgniteCacheSnapshotManager#flushDirtyPageHandler > IgniteCacheSnapshotManager#onPageWrite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11226) SQL: Remove GridQueryIndexing.prepareNativeStatement
[ https://issues.apache.org/jira/browse/IGNITE-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794936#comment-16794936 ] Pavel Kuznetsov commented on IGNITE-11226: -- to be confident scheduled re-run of mvcc queries https://ci.ignite.apache.org/viewQueued.html?itemId=3343473 > SQL: Remove GridQueryIndexing.prepareNativeStatement > > > Key: IGNITE-11226 > URL: https://issues.apache.org/jira/browse/IGNITE-11226 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This method is the only leak of H2 internals to the outer code. Close > analysis of code reveals that the only reason we have it is *JDBC metadata*. > Need to create a method which will prepare metadata for a statement and > return it as a detached object. Most probably we already have all necessary > mechanics. This is more about refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11226) SQL: Remove GridQueryIndexing.prepareNativeStatement
[ https://issues.apache.org/jira/browse/IGNITE-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794923#comment-16794923 ] Pavel Kuznetsov edited comment on IGNITE-11226 at 3/18/19 10:55 AM: [~vozerov] there are troubles with bot visa. Visa can be viewed at https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/6258/head=Latest 1) Inspections log tells about JobStealingCollisionSpi.java - out of the scope (https://ci.ignite.apache.org/viewLog.html?buildId=3339821) 2) MVCC Queries Failed due to timeout https://ci.ignite.apache.org/viewLog.html?buildId=3339776 3) PHP client tests failed due to auth troubles : https://ci.ignite.apache.org/viewLog.html?buildId=3339777 these tests failed in master (for exampl https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5512920338110762681=testDetails) was (Author: pkouznet): [~vozerov] there are troubles with bot visa. Visa can be viewed at https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/6258/head=Latest 1) Inspections log tells about JobStealingCollisionSpi.java - out of the scope (https://ci.ignite.apache.org/viewLog.html?buildId=3339821) 2) MVCC Queries Failed due to timeout https://ci.ignite.apache.org/viewLog.html?buildId=3339776 3) PHP client tests failed due to auth troubles : https://ci.ignite.apache.org/viewLog.html?buildId=3339777 > SQL: Remove GridQueryIndexing.prepareNativeStatement > > > Key: IGNITE-11226 > URL: https://issues.apache.org/jira/browse/IGNITE-11226 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This method is the only leak of H2 internals to the outer code. Close > analysis of code reveals that the only reason we have it is *JDBC metadata*. > Need to create a method which will prepare metadata for a statement and > return it as a detached object. Most probably we already have all necessary > mechanics. This is more about refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794935#comment-16794935 ] Pavel Kuznetsov commented on IGNITE-5962: - visa can be viewed at https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/6209/head=Latest 1) Inspections failed due to internal error. (https://ci.ignite.apache.org/viewLog.html?buildId=3338689) 2) TcpDiscoveryClientSuspensionSelfTest.testTwoServers - failure is not reproduced in previous run (before merge master) and is not reproduced locally. (https://ci.ignite.apache.org/viewLog.html?buildId=3338626) > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11427) Document custom node fail functional.
[ https://issues.apache.org/jira/browse/IGNITE-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794925#comment-16794925 ] Stanilovsky Evgeny commented on IGNITE-11427: - excludeNode: will initiate failure of provided node, in case of Server node - it will be SEGMENTED (replaced from topology), for Client node it would be replaced from topology but if [1] option: TcpDiscoverySpi#setClientReconnectDisabled not disabled, it would reconnect once more after timeout. [1] https://apacheignite.readme.io/docs/clients-vs-servers#reconnecting-a-client > Document custom node fail functional. > - > > Key: IGNITE-11427 > URL: https://issues.apache.org/jira/browse/IGNITE-11427 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > Attachments: Screenshot_20190227_100539.png > > > Append additional node fail documentation related to [1] > [1] https://issues.apache.org/jira/browse/IGNITE-11332 > > how it looks into jconsole: > !Screenshot_20190227_100539.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11226) SQL: Remove GridQueryIndexing.prepareNativeStatement
[ https://issues.apache.org/jira/browse/IGNITE-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794923#comment-16794923 ] Pavel Kuznetsov commented on IGNITE-11226: -- [~vozerov] there are troubles with bot visa. Visa can be viewed at https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/6258/head=Latest 1) Inspections log tells about JobStealingCollisionSpi.java - out of the scope (https://ci.ignite.apache.org/viewLog.html?buildId=3339821) 2) MVCC Queries Failed due to timeout https://ci.ignite.apache.org/viewLog.html?buildId=3339776 3) PHP client tests failed due to auth troubles : https://ci.ignite.apache.org/viewLog.html?buildId=3339777 > SQL: Remove GridQueryIndexing.prepareNativeStatement > > > Key: IGNITE-11226 > URL: https://issues.apache.org/jira/browse/IGNITE-11226 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This method is the only leak of H2 internals to the outer code. Close > analysis of code reveals that the only reason we have it is *JDBC metadata*. > Need to create a method which will prepare metadata for a statement and > return it as a detached object. Most probably we already have all necessary > mechanics. This is more about refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling
[
https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794899#comment-16794899
]
Ivan Pavlukhin commented on IGNITE-11356:
-
[~ilyak] I rebased changes, please take a look.
> Test framework: Remove custom assumption exceptions handling
>
>
> Key: IGNITE-11356
> URL: https://issues.apache.org/jira/browse/IGNITE-11356
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be
> removed. Currently with custom handling tests with unmet assumptions are
> marked as passed. With default handling failed assumptions on instance level
> mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look
> perfect. But with custom handling a particular test is not included into TC
> report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling
[
https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794884#comment-16794884
]
Ilya Kasnacheev commented on IGNITE-11356:
--
[~Pavlukhin] can you please rebase this change to latest master? Unfortunately
it would not apply without conflicts.
> Test framework: Remove custom assumption exceptions handling
>
>
> Key: IGNITE-11356
> URL: https://issues.apache.org/jira/browse/IGNITE-11356
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be
> removed. Currently with custom handling tests with unmet assumptions are
> marked as passed. With default handling failed assumptions on instance level
> mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look
> perfect. But with custom handling a particular test is not included into TC
> report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11398) Remove leftover @RunWith(JUnit4.class)
[
https://issues.apache.org/jira/browse/IGNITE-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-11398:
-
Fix Version/s: 2.8
> Remove leftover @RunWith(JUnit4.class)
> --
>
> Key: IGNITE-11398
> URL: https://issues.apache.org/jira/browse/IGNITE-11398
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During migration to junit4 transitional construction
> {{@RunWith(JUnit4.class)}} was used. And it was forgotten in couple of
> places. Let's clean up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11398) Remove leftover @RunWith(JUnit4.class)
[
https://issues.apache.org/jira/browse/IGNITE-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794880#comment-16794880
]
Ilya Kasnacheev commented on IGNITE-11398:
--
Thank you for cleaning tests up! I have merged this change.
> Remove leftover @RunWith(JUnit4.class)
> --
>
> Key: IGNITE-11398
> URL: https://issues.apache.org/jira/browse/IGNITE-11398
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During migration to junit4 transitional construction
> {{@RunWith(JUnit4.class)}} was used. And it was forgotten in couple of
> places. Let's clean up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11542) Fix flacky test testGivenCacheWithPojoValueAndPds_WhenPut_ThenNoHangup.
[ https://issues.apache.org/jira/browse/IGNITE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794876#comment-16794876 ] Andrew Mashenkov commented on IGNITE-11542: --- TC test looks ok. https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2893288071124380881=testDetails_IgniteTests24Java8=pull%2F6270%2Fhead > Fix flacky test testGivenCacheWithPojoValueAndPds_WhenPut_ThenNoHangup. > --- > > Key: IGNITE-11542 > URL: https://issues.apache.org/jira/browse/IGNITE-11542 > Project: Ignite > Issue Type: Test >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > IgnitePdsBinarySortObjectFieldsTest.testGivenCacheWithPojoValueAndPds_WhenPut_ThenNoHangup > fails sporadically on TC due to 5 sec timeout may be not enough for grid > startup. > Test checks "put" operation will complete in 5 sec timeout, > but grid initialization is included in this timeout with no reason. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11558) Developer warning when HashMap is passed to putAll()
Ilya Kasnacheev created IGNITE-11558: Summary: Developer warning when HashMap is passed to putAll() Key: IGNITE-11558 URL: https://issues.apache.org/jira/browse/IGNITE-11558 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 2.7 Reporter: Ilya Kasnacheev Currently when HashMap is passed to putAll it's very easy to cause deadlock since the order of keys is not stable. This is a pity because users will use HashMap by default and not expect any trouble. We should issue a warning when user passes HashMap (but not LinkedHashMap) to putAll(). On .Net we should probably check for Dictionary. Warning similar to the one issues when index cannot be efficiently inlined. Another approach is to turn keys into binary form and then sort them, if map is not a SortedMap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11535) AtomicLong cannot be found after creation
[
https://issues.apache.org/jira/browse/IGNITE-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794861#comment-16794861
]
Vyacheslav Koptilin commented on IGNITE-11535:
--
It seems that MVCC PDS2 hang is not caused by the proposed change.
> AtomicLong cannot be found after creation
> -
>
> Key: IGNITE-11535
> URL: https://issues.apache.org/jira/browse/IGNITE-11535
> 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
>
> For now, IgniteAtomics use {{PartitionLossPolicy.IGNORE}}, which is the
> default value for all caches, (see
> {{DataStructuresProcessor#cacheConfiguration}}). Therefore, partition loss
> leads to the fact that information about IgniteAtomic may be lost as well. In
> that case, any operation with IgniteAtomic results in the following exception:
> {code}
> javax.cache.processor.EntryProcessorException: Failed to find atomic long:
> atomicLong
> {code}
> {code:java}
> Value: An error occurred while calling o2248.incrementAndGet.
> : class org.apache.ignite.IgniteException: Failed to find atomic long:
> nodeIdFilter_7
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheAtomicLongImpl.incrementAndGet(GridCacheAtomicLongImpl.java:105)
> at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
> at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357)
> at py4j.Gateway.invoke(Gateway.java:282)
> at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
> at py4j.commands.CallCommand.execute(CallCommand.java:79)
> at py4j.GatewayConnection.run(GatewayConnection.java:238)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.processor.EntryProcessorException: Failed to find
> atomic long: nodeIdFilter_7
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheAtomicLongImpl$IncrementAndGetProcessor.process(GridCacheAtomicLongImpl.java:525)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheAtomicLongImpl$IncrementAndGetProcessor.process(GridCacheAtomicLongImpl.java:512)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:424)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1237)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:677)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1054)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:396)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:519)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:150)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:135)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:177)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:175)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
> at
>
[jira] [Assigned] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
[ https://issues.apache.org/jira/browse/IGNITE-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich reassigned IGNITE-11557: -- Assignee: Yury Gerzhedovich > flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes > -- > > Key: IGNITE-11557 > URL: https://issues.apache.org/jira/browse/IGNITE-11557 > Project: Ignite > Issue Type: Bug >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > > test failed with the following trace > _[2019-03-18 > 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor] > Failed to execute local query. class > org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. > Exception calling user-defined function: "can_fail(): null"; SQL statement: > SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND > sleep()>0 AND can_fail()=0 [90105-197] at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161) > at > org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102) > at > org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349) > at > org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347) > 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$7.run(GridAbstractTest.java:2107) > at java.lang.Thread.run(Thread.java:748) Caused by: > org.h2.jdbc.JdbcSQLException: Exception calling user-defined function: > "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM > "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at > org.h2.message.DbException.get(DbException.java:168) at > org.h2.message.DbException.convertInvocation(DbException.java:324) at > org.h2.engine.FunctionAlias$JavaMethod.getValue(FunctionAlias.java:468) at > org.h2.expression.JavaFunction.getValue(JavaFunction.java:38) at > org.h2.expression.Comparison.getValue(Comparison.java:239) at > org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:86) at >
[jira] [Commented] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
[ https://issues.apache.org/jira/browse/IGNITE-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794837#comment-16794837 ] Yury Gerzhedovich commented on IGNITE-11557: Locally run the test more 1k times - no any issues after fix. waiting a Bot Vise. > flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes > -- > > Key: IGNITE-11557 > URL: https://issues.apache.org/jira/browse/IGNITE-11557 > Project: Ignite > Issue Type: Bug >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > test failed with the following trace > _[2019-03-18 > 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor] > Failed to execute local query. class > org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. > Exception calling user-defined function: "can_fail(): null"; SQL statement: > SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND > sleep()>0 AND can_fail()=0 [90105-197] at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161) > at > org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102) > at > org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349) > at > org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317) > at > org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347) > 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$7.run(GridAbstractTest.java:2107) > at java.lang.Thread.run(Thread.java:748) Caused by: > org.h2.jdbc.JdbcSQLException: Exception calling user-defined function: > "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM > "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at > org.h2.message.DbException.get(DbException.java:168) at > org.h2.message.DbException.convertInvocation(DbException.java:324) at > org.h2.engine.FunctionAlias$JavaMethod.getValue(FunctionAlias.java:468) at > org.h2.expression.JavaFunction.getValue(JavaFunction.java:38) at >
[jira] [Created] (IGNITE-11557) flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes
Yury Gerzhedovich created IGNITE-11557: -- Summary: flaky test SqlSystemViewsSelfTest.testQueryHistoryMetricsModes Key: IGNITE-11557 URL: https://issues.apache.org/jira/browse/IGNITE-11557 Project: Ignite Issue Type: Bug Reporter: Yury Gerzhedovich test failed with the following trace _[2019-03-18 08:24:48,268][ERROR][test-runner-#443693%query.SqlSystemViewsSelfTest%][GridMapQueryExecutor] Failed to execute local query. class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. Exception calling user-defined function: "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:846) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:923) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:588) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:388) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203) at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:163) at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:161) at org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:2057) at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1234) at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:757) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1015) at org.apache.ignite.internal.processors.cache.QueryCursorImpl.iter(QueryCursorImpl.java:102) at org.apache.ignite.internal.processors.cache.query.RegisteredQueryCursor.iter(RegisteredQueryCursor.java:64) at org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:121) at org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.lambda$testQueryHistoryMetricsModes$0(SqlSystemViewsSelfTest.java:349) at org.apache.ignite.testframework.GridTestUtils.assertThrows(GridTestUtils.java:317) at org.apache.ignite.internal.processors.query.SqlSystemViewsSelfTest.testQueryHistoryMetricsModes(SqlSystemViewsSelfTest.java:347) 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$7.run(GridAbstractTest.java:2107) at java.lang.Thread.run(Thread.java:748) Caused by: org.h2.jdbc.JdbcSQLException: Exception calling user-defined function: "can_fail(): null"; SQL statement: SELECT "STRING"._KEY, "STRING"._VAL FROM "STRING" WHERE _key=100 AND sleep()>0 AND can_fail()=0 [90105-197] at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at org.h2.message.DbException.get(DbException.java:168) at org.h2.message.DbException.convertInvocation(DbException.java:324) at org.h2.engine.FunctionAlias$JavaMethod.getValue(FunctionAlias.java:468) at org.h2.expression.JavaFunction.getValue(JavaFunction.java:38) at org.h2.expression.Comparison.getValue(Comparison.java:239) at org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:86) at org.h2.expression.Expression.getBooleanValue(Expression.java:178) at org.h2.command.dml.Select.isConditionMet(Select.java:312) at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1455) at org.h2.result.LazyResult.hasNext(LazyResult.java:79) at org.h2.result.LazyResult.next(LazyResult.java:59) at org.h2.command.dml.Select.queryFlat(Select.java:527) at org.h2.command.dml.Select.queryWithoutCache(Select.java:633) at
[jira] [Assigned] (IGNITE-11556) Add color legend into series selection panel
[ https://issues.apache.org/jira/browse/IGNITE-11556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-11556: - Assignee: Alexander Kalinin > Add color legend into series selection panel > > > Key: IGNITE-11556 > URL: https://issues.apache.org/jira/browse/IGNITE-11556 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently we have a series selector for charts, but it lacks color indication > for matching series. Let's add them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11556) Add color legend into series selection panel
[ https://issues.apache.org/jira/browse/IGNITE-11556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-11556: -- Description: Currently we have a series selector for charts, but it lacks color indication for matching series. Let's add them. (was: Currently we have a seris selector for charts, but it lacks color indication for matching series. Let's add them.) > Add color legend into series selection panel > > > Key: IGNITE-11556 > URL: https://issues.apache.org/jira/browse/IGNITE-11556 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently we have a series selector for charts, but it lacks color indication > for matching series. Let's add them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
