[jira] [Commented] (IGNITE-14353) Ability to specify postfix for IgniteLogger instead of nodeId
[
https://issues.apache.org/jira/browse/IGNITE-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307424#comment-17307424
]
Nikolay Izhikov commented on IGNITE-14353:
--
[~mmuzaf]
[~namelchev]
Can you, please, take a look at my changes?
> Ability to specify postfix for IgniteLogger instead of nodeId
> -
>
> Key: IGNITE-14353
> URL: https://issues.apache.org/jira/browse/IGNITE-14353
> Project: Ignite
> Issue Type: New Feature
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-59
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Right now, user can't change IgniteLogger file name.
> CDC application should use it's own files for logging, something like
> {{cdc-[cdc_consumer_id].log}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14353) Ability to specify postfix for IgniteLogger instead of nodeId
[
https://issues.apache.org/jira/browse/IGNITE-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-14353:
-
Description:
Right now, user can't change IgniteLogger file name.
CDC application should use it's own files for logging, something like
{{ignite-cdc-[cdc-consumer-id].log}}.
was:
Right now, user can't change IgniteLogger file name.
CDC application should use it's own files for logging, something like
{{cdc-[cdc_consumer_id].log}}.
> Ability to specify postfix for IgniteLogger instead of nodeId
> -
>
> Key: IGNITE-14353
> URL: https://issues.apache.org/jira/browse/IGNITE-14353
> Project: Ignite
> Issue Type: New Feature
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-59
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Right now, user can't change IgniteLogger file name.
> CDC application should use it's own files for logging, something like
> {{ignite-cdc-[cdc-consumer-id].log}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13056) SchemaManager refactoring
[
https://issues.apache.org/jira/browse/IGNITE-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307399#comment-17307399
]
Ignite TC Bot commented on IGNITE-13056:
{panel:title=Branch: [pull/8490/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8490/head] Base: [master] : New Tests
(25)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5930801]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
InlineIndexKeyTypeRegistryTest.testStrings - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
InlineIndexKeyTypeRegistryTest.testNulls - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
InlineIndexKeyTypeRegistryTest.testObjectCheck - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
InlineIndexKeyTypeRegistryTest.testMismatchType - PASSED{color}
{color:#8b}PDS (Compatibility)*{color} [[tests
21|https://ci.ignite.apache.org/viewLog.html?buildId=5930788]]
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.9.1,
cfgInlineSize=true] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.9.1,
cfgInlineSize=false] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.7.0,
cfgInlineSize=false] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.6.0,
cfgInlineSize=true] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.9.0,
cfgInlineSize=true] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.7.6,
cfgInlineSize=true] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.7.6,
cfgInlineSize=false] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
IndexTypesCompatibilityTest.testQueryOldIndex[ver=2.7.0] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
IndexTypesCompatibilityTest.testQueryOldIndex[ver=2.6.0] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
InlineJavaObjectCompatibilityTest.testQueryOldInlinedIndex[ver=2.7.0,
cfgInlineSize=true] - PASSED{color}
* {color:#013220}IgniteCompatibilityBasicTestSuite:
IndexTypesCompatibilityTest.testQueryOldIndex[ver=2.8.1] - PASSED{color}
... and 10 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5930822buildTypeId=IgniteTests24Java8_RunAll]
> SchemaManager refactoring
> -
>
> Key: IGNITE-13056
> URL: https://issues.apache.org/jira/browse/IGNITE-13056
> Project: Ignite
> Issue Type: New Feature
> Components: sql
>Affects Versions: 2.8
>Reporter: Nikolay Izhikov
>Assignee: Maksim Timonin
>Priority: Major
> Labels: IEP-49, calcite
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> Since Ignite wants to leverage from several SQL engines we need to make work
> with index independent from the used SQL engine.
> We also should consider moving all machinery related to an index to the core
> module to make it available from any module that wants to use it.
> Requirements so far:
> * Ability to track indexes in several engines
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14353) Ability to specify postfix for IgniteLogger instead of nodeId
[
https://issues.apache.org/jira/browse/IGNITE-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-14353:
-
Summary: Ability to specify postfix for IgniteLogger instead of nodeId
(was: Ability to specify log file for IgniteLogger)
> Ability to specify postfix for IgniteLogger instead of nodeId
> -
>
> Key: IGNITE-14353
> URL: https://issues.apache.org/jira/browse/IGNITE-14353
> Project: Ignite
> Issue Type: New Feature
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-59
>
> Right now, user can't change IgniteLogger file name.
> CDC application should use it's own files for logging, something like
> {{cdc-[cdc_consumer_id].log}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14377) Enchance log of node ping failure.
[
https://issues.apache.org/jira/browse/IGNITE-14377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307237#comment-17307237
]
Ignite TC Bot commented on IGNITE-14377:
{panel:title=Branch: [pull/8913/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8913/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5930362buildTypeId=IgniteTests24Java8_RunAll]
> Enchance log of node ping failure.
> --
>
> Key: IGNITE-14377
> URL: https://issues.apache.org/jira/browse/IGNITE-14377
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Log of unsuccessful ping during the joining is insufficient. No failure
> reason is logged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14353) Ability to specify log file for IgniteLogger
[
https://issues.apache.org/jira/browse/IGNITE-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-14353:
Assignee: Nikolay Izhikov
> Ability to specify log file for IgniteLogger
>
>
> Key: IGNITE-14353
> URL: https://issues.apache.org/jira/browse/IGNITE-14353
> Project: Ignite
> Issue Type: New Feature
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-59
>
> Right now, user can't change IgniteLogger file name.
> CDC application should use it's own files for logging, something like
> {{cdc-[cdc_consumer_id].log}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14367) WAL reader. Read only specific Record Types
[ https://issues.apache.org/jira/browse/IGNITE-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov resolved IGNITE-14367. -- Resolution: Implemented > WAL reader. Read only specific Record Types > --- > > Key: IGNITE-14367 > URL: https://issues.apache.org/jira/browse/IGNITE-14367 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > > CDC application uses only specific WALRecord types. > So we should provide an ability to skip WALRecord without full deserializing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14367) WAL reader. Read only specific Record Types
[ https://issues.apache.org/jira/browse/IGNITE-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307229#comment-17307229 ] Nikolay Izhikov commented on IGNITE-14367: -- Filter already implemented in IGNITE-11749 > WAL reader. Read only specific Record Types > --- > > Key: IGNITE-14367 > URL: https://issues.apache.org/jira/browse/IGNITE-14367 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > > CDC application uses only specific WALRecord types. > So we should provide an ability to skip WALRecord without full deserializing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-7640) Refactor DiscoveryDataClusterState to be immutable
[ https://issues.apache.org/jira/browse/IGNITE-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-7640: --- Assignee: Maxim Muzafarov > Refactor DiscoveryDataClusterState to be immutable > -- > > Key: IGNITE-7640 > URL: https://issues.apache.org/jira/browse/IGNITE-7640 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.4 >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14367) WAL reader. Read only specific Record Types
[ https://issues.apache.org/jira/browse/IGNITE-14367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-14367: Assignee: Nikolay Izhikov > WAL reader. Read only specific Record Types > --- > > Key: IGNITE-14367 > URL: https://issues.apache.org/jira/browse/IGNITE-14367 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > > CDC application uses only specific WALRecord types. > So we should provide an ability to skip WALRecord without full deserializing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-408) Cleanup JCache and Ignite cache events API
[ https://issues.apache.org/jira/browse/IGNITE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-408: -- Assignee: Maxim Muzafarov > Cleanup JCache and Ignite cache events API > -- > > Key: IGNITE-408 > URL: https://issues.apache.org/jira/browse/IGNITE-408 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Semen Boikov >Assignee: Maxim Muzafarov >Priority: Major > > Now JCache cache events and Ignite cache events APIs are not related, this > can be confusing. Need to think how to unify cache events. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-18) Revisit logic for warmup closure, add tests and properly document
[ https://issues.apache.org/jira/browse/IGNITE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov resolved IGNITE-18. --- Resolution: Won't Fix > Revisit logic for warmup closure, add tests and properly document > - > > Key: IGNITE-18 > URL: https://issues.apache.org/jira/browse/IGNITE-18 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13358) Improvements for partition clearing related parts
[ https://issues.apache.org/jira/browse/IGNITE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13358: - Labels: important (was: ) > Improvements for partition clearing related parts > - > > Key: IGNITE-13358 > URL: https://issues.apache.org/jira/browse/IGNITE-13358 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > We have several issues related to a partition clearing worth fixing. > 1. PartitionsEvictManager doent's provide obvious guarantees for a > correctness when a node or a cache group is stopped while partitions are > concurrently clearing. > 2. GridDhtLocalPartition#awaitDestroy is called while holding topology write > lock, which is deadlock prone, because we currently require write lock to > destroy a partition. > 3. GridDhtLocalPartition contains a lot of messy code related to partition > clearing, most notably ClearFuture, but the clearing is done by > PartitionsEvictManager. We should get rid of a clearing code in > GridDhtLocalPartition. This should also bring better code readility and help > understand what happening during a clearing. > 4. Currently moving partitions are cleared before rebalancing in the order > different to rebalanceOrder, breaking the contract. Better to submit such > partitions for clearing to the rebalancing pool before each group starts to > rebalance. This will allow faster rebalancing (accoring to configured > rebalance pool size) and will provide rebalanceOrder guarantees. > 5. The clearing logic for for moving partitions (before rebalancing) seems > incorrect: it's possible to lost updates received during clearing. > 6. To clear partitions before full rebalancing we utilize same threads as for > a partition eviction. This can slow rebalancing even if we have resources. > Better to clear partitions in the rebalance pool (explicitely dedicated by > user). > 7. It's possible to reserve a renting partition, which have absolutely no > meaning. All operations with a renting partitions (except clearing) are a > waste of resources. > 8. Partition eviction causes system pool tasks starvation if a number of > threads in system pool=1. This can break crucial functionality. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12451) Introduce deadlock detection for cache entry reentrant locks
[ https://issues.apache.org/jira/browse/IGNITE-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12451: - Labels: important (was: ) > Introduce deadlock detection for cache entry reentrant locks > > > Key: IGNITE-12451 > URL: https://issues.apache.org/jira/browse/IGNITE-12451 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: Ivan Rakov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Aside from IGNITE-12365, we still have possible threat of cache-entry-level > deadlock in case of careless usage of JCache mass operations (putAll, > removeAll): > 1. If two different user threads will perform putAll on the same two keys in > reverse order (primary node for which is the same), there's a chance that > sys-stripe threads will be deadlocked. > 2. Even without direct contract violation from user side, HashMap can be > passed as argument for putAll. Even if user threads have called mass > operations with two keys in the same order, HashMap iteration order is not > strictly defined, which may cause the same deadlock. > Local deadlock detection should mitigate this issue. We can create a wrapper > for ReentrantLock with logic that performs cycle detection in wait-for graph > in case we are waiting for lock acquisition for too long. Exception will be > thrown from one of the threads in such case, failing user operation, but > letting the system make progress. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307164#comment-17307164 ] Atri Sharma commented on IGNITE-14346: -- [~ilyak] I have uploaded screenshots of test suite with Azure credentials and actual storage. > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Atri Sharma updated IGNITE-14346: - Attachment: Screenshot 2021-03-23 at 8.42.31 PM.png Screenshot 2021-03-23 at 8.43.31 PM.png Screenshot 2021-03-23 at 8.44.11 PM.png Screenshot 2021-03-23 at 8.45.05 PM.png > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13399) CpuLoad metric reports -1 under Java 11 in embedded mode
[
https://issues.apache.org/jira/browse/IGNITE-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307160#comment-17307160
]
Denis Mekhanikov commented on IGNITE-13399:
---
[~maliev] could you take a look?
> CpuLoad metric reports -1 under Java 11 in embedded mode
>
>
> Key: IGNITE-13399
> URL: https://issues.apache.org/jira/browse/IGNITE-13399
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When running a node in embedded mode under Java 11, the CpuLoad metric
> reports -1. The process needs to be started with the following option:
> {{--add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED}}
> We need to get rid of this requirement to run Java with additional flags to
> get proper values for the CpuLoad metric.
> Some investigation was done under the following issue:
> https://issues.apache.org/jira/browse/IGNITE-13306
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307142#comment-17307142
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5930552]]
* IgniteCacheTestSuite7:
TxRollbackAsyncWithPersistenceTest.testMixedAsyncRollbackTypes - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 4{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5930564]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5930546]]
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationExecutesSynchronously -
PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=5930608]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5930592buildTypeId=IgniteTests24Java8_RunAll]
> Callbacks from striped pool due to async/await may hang cluster
> ---
>
> Key: IGNITE-12033
> URL: https://issues.apache.org/jira/browse/IGNITE-12033
> Project: Ignite
> Issue Type: Bug
> Components: cache, platforms
>Affects Versions: 2.7.5
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: iep-70
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Discussed on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html
> *Must use the public pool for callbacks as the most obvious step.*
>
> http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051
> There's a reproducer project. Long story short, .Net can invoke cache
> operations with future callbacks, which will be invoked from striped pool. If
> such callbacks are to use cache operations, those will be possibly sheduled
> to the same stripe and cause a deadlock.
> The code is very simple:
> {code}
> Console.WriteLine("PutAsync");
> await cache.PutAsync(1, "Test");
> Console.WriteLine("Replace");
> cache.Replace(1, "Testing"); // Hangs here
> Console.WriteLine("Wait");
> await Task.Delay(Timeout.Infinite);
> {code}
> async/await should absolutely not allow any client code to be run from
> stripes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14254) Graceful stop rebuilding indexes when deactivating a cluster
[
https://issues.apache.org/jira/browse/IGNITE-14254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307137#comment-17307137
]
Ignite TC Bot commented on IGNITE-14254:
{panel:title=Branch: [pull/8837/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8837/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=5929992]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testSequentialRebuildIndexes - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testInternalIndexingRebuildFuture - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testSchemaIndexCacheCompoundFeature - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testStopRebuildIndexesOnDeactivation - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
StopRebuildIndexTest.testStopRebuildIndexesOnStopNode - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5930025buildTypeId=IgniteTests24Java8_RunAll]
> Graceful stop rebuilding indexes when deactivating a cluster
>
>
> Key: IGNITE-14254
> URL: https://issues.apache.org/jira/browse/IGNITE-14254
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> If in the process of rebuilding the indexes to deactivate the cluster, then a
> number of errors may appear, including a node fail. It is necessary to stop
> index rebuilding before stopping the cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307094#comment-17307094 ] Ilya Kasnacheev commented on IGNITE-14346: -- I did not have chance to try it on Azure, but I have left some comments regarding CC. > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14343) .NET: Allow arbitrary MemberInit projections in LINQ
[
https://issues.apache.org/jira/browse/IGNITE-14343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14343:
Description:
Ignite LINQ provider allows anonymous type projections:
{code}
query.Select(emp => new {Id = emp.Key, Name = emp.Value.Name});
{code}
However, it does not work with a custom class:
{code}
query.Select(emp => new Foo {Id = emp.Key, Name = emp.Value.Name});
{code}
throws exception:
{code}
System.NotSupportedException : The expression 'new Foo() {Id = [x].Key}' (type:
System.Linq.Expressions.MemberInitExpression) is not supported.
{code}
Add VisitMemberInit overload to CacheQueryExpressionVisitor to support this
scenario. See linked SO page for more details - there is a proposed fix as well.
was:
Ignite LINQ provider allows anonymous type projections:
{code}
query.Select(emp => new {Id = emp.Key, Name = emp.Value.Name});
{code}
However, it does not work with a custom class:
{code}
query.Select(emp => new Foo {Id = emp.Key, Name = emp.Value.Name});
{code}
throws exception:
{code}
System.NotSupportedException : The expression 'new Foo() {Id = [x].Key}' (type:
System.Linq.Expressions.MemberInitExpression) is not supported.
{code}
Add VisitMemberInit overload to CacheQueryExpressionVisitor to support this
scenario.
> .NET: Allow arbitrary MemberInit projections in LINQ
>
>
> Key: IGNITE-14343
> URL: https://issues.apache.org/jira/browse/IGNITE-14343
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, LINQ
> Fix For: 2.11
>
>
> Ignite LINQ provider allows anonymous type projections:
> {code}
> query.Select(emp => new {Id = emp.Key, Name = emp.Value.Name});
> {code}
> However, it does not work with a custom class:
> {code}
> query.Select(emp => new Foo {Id = emp.Key, Name = emp.Value.Name});
> {code}
> throws exception:
> {code}
> System.NotSupportedException : The expression 'new Foo() {Id = [x].Key}'
> (type: System.Linq.Expressions.MemberInitExpression) is not supported.
> {code}
> Add VisitMemberInit overload to CacheQueryExpressionVisitor to support this
> scenario. See linked SO page for more details - there is a proposed fix as
> well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13399) CpuLoad metric reports -1 under Java 11 in embedded mode
[
https://issues.apache.org/jira/browse/IGNITE-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307043#comment-17307043
]
Ignite TC Bot commented on IGNITE-13399:
{panel:title=Branch: [pull/8903/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8903/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 9{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5923138]]
* {color:#013220}IgniteCacheTestSuite9: SystemMetricsTest.testTotalSystemMemory
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite9: SystemMetricsTest.testCpuLoadMetric -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5923176buildTypeId=IgniteTests24Java8_RunAll]
> CpuLoad metric reports -1 under Java 11 in embedded mode
>
>
> Key: IGNITE-13399
> URL: https://issues.apache.org/jira/browse/IGNITE-13399
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When running a node in embedded mode under Java 11, the CpuLoad metric
> reports -1. The process needs to be started with the following option:
> {{--add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED}}
> We need to get rid of this requirement to run Java with additional flags to
> get proper values for the CpuLoad metric.
> Some investigation was done under the following issue:
> https://issues.apache.org/jira/browse/IGNITE-13306
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14378) Remove delay from node ping.
[ https://issues.apache.org/jira/browse/IGNITE-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307010#comment-17307010 ] Anton Vinogradov commented on IGNITE-14378: --- Merged into master. Thanks for your contribution! > Remove delay from node ping. > > > Key: IGNITE-14378 > URL: https://issues.apache.org/jira/browse/IGNITE-14378 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Remove U.sleep(200) from the node ping. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14378) Remove delay from node ping.
[ https://issues.apache.org/jira/browse/IGNITE-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-14378. --- Resolution: Fixed > Remove delay from node ping. > > > Key: IGNITE-14378 > URL: https://issues.apache.org/jira/browse/IGNITE-14378 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Remove U.sleep(200) from the node ping. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13547) Calcite integration. CREATE TABLE support
[ https://issues.apache.org/jira/browse/IGNITE-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov reassigned IGNITE-13547: - Assignee: Konstantin Orlov > Calcite integration. CREATE TABLE support > - > > Key: IGNITE-13547 > URL: https://issues.apache.org/jira/browse/IGNITE-13547 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Konstantin Orlov >Priority: Critical > Original Estimate: 40h > Remaining Estimate: 40h > > We need to support DDL commands. The task about the support of CREATE TABLE. > Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14378) Remove delay from node ping.
[
https://issues.apache.org/jira/browse/IGNITE-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307007#comment-17307007
]
Ignite TC Bot commented on IGNITE-14378:
{panel:title=Branch: [pull/8914/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8914/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5927888buildTypeId=IgniteTests24Java8_RunAll]
> Remove delay from node ping.
>
>
> Key: IGNITE-14378
> URL: https://issues.apache.org/jira/browse/IGNITE-14378
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Remove U.sleep(200) from the node ping.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14376) JmxMetricExporter fails to export discovery metrics
[
https://issues.apache.org/jira/browse/IGNITE-14376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-14376:
Description:
Error:
{code:java}
java.lang.StringIndexOutOfBoundsException: String index out of range: -2
at java.lang.String.substring(String.java:1931)
at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.lambda$getMBeanInfo$0(MetricRegistryMBean.java:105)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getMBeanInfo(MetricRegistryMBean.java:85)
at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getAttribute(MetricRegistryMBean.java:58)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
at com.sun.proxy.$Proxy32.getMBeanInfo(Unknown Source)
at
org.apache.ignite.internal.metric.JmxExporterSpiTest.test(JmxExporterSpiTest.java:146)
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:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2391)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer:
{code:java}
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi();
cfg.setMetricExporterSpi(jmxSpi);
return cfg;
}
/** */
@Test
public void test() throws Exception {
IgniteEx srv = startGrid();
DynamicMBean mBean = metricRegistry(srv.name(), "io", "discovery");
mBean.getMBeanInfo();
}
{code}
The main reason: JMX exporter assumes that each metric must starts with the
name of the registry it belongs to (see MetricRegistryMBean#getMBeanInfo), but
discovery metrics do not obey this naming convection (see
TcpDiscoveryStatistics/ZookeeperDiscoveryStatistics).
was:
Error:
{code:java}
java.lang.StringIndexOutOfBoundsException: String index out of range:
-2java.lang.StringIndexOutOfBoundsException: String index out of range: -2
at java.lang.String.substring(String.java:1931) at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.lambda$getMBeanInfo$0(MetricRegistryMBean.java:105)
at java.util.Iterator.forEachRemaining(Iterator.java:116) at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getMBeanInfo(MetricRegistryMBean.java:85)
at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getAttribute(MetricRegistryMBean.java:58)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
at com.sun.proxy.$Proxy32.getMBeanInfo(Unknown Source) at
org.apache.ignite.internal.metric.JmxExporterSpiTest.test(JmxExporterSpiTest.java:146)
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:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2391)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer:
{code:java}
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
JmxMetricExporterSpi jmxSpi = new
[jira] [Updated] (IGNITE-14376) JmxMetricExporter fails to export discovery metrics
[
https://issues.apache.org/jira/browse/IGNITE-14376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-14376:
Description:
Error:
{code:java}
java.lang.StringIndexOutOfBoundsException: String index out of range:
-2java.lang.StringIndexOutOfBoundsException: String index out of range: -2
at java.lang.String.substring(String.java:1931) at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.lambda$getMBeanInfo$0(MetricRegistryMBean.java:105)
at java.util.Iterator.forEachRemaining(Iterator.java:116) at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getMBeanInfo(MetricRegistryMBean.java:85)
at
org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getAttribute(MetricRegistryMBean.java:58)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
at com.sun.proxy.$Proxy32.getMBeanInfo(Unknown Source) at
org.apache.ignite.internal.metric.JmxExporterSpiTest.test(JmxExporterSpiTest.java:146)
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:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2391)
at java.lang.Thread.run(Thread.java:748)
{code}
Reproducer:
{code:java}
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi();
cfg.setMetricExporterSpi(jmxSpi);
return cfg;
}
/** */
@Test
public void test() throws Exception {
IgniteEx srv = startGrid();
DynamicMBean mBean = metricRegistry(srv.name(), "io", "discovery");
mBean.getMBeanInfo();
}
{code}
The main reason: JMX exporter assumes that each metric must starts with the
name of the registry it belongs to (see MetricRegistryMBean#getMBeanInfo), but
discovery metrics do not obey this naming convection (see
TcpDiscoveryStatistics/ZookeeperDiscoveryStatistics).
was:
Reproducer:
{code:java}
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi();
cfg.setMetricExporterSpi(jmxSpi);
return cfg;
}
/** */
@Test
public void test() throws Exception {
IgniteEx srv = startGrid();
DynamicMBean mBean = metricRegistry(srv.name(), "io", "discovery");
mBean.getMBeanInfo();
}
{code}
The main reason: JMX exporter assumes that each metric must starts with the
name of the registry it belongs to (see MetricRegistryMBean#getMBeanInfo), but
discovery metrics do not obey this naming convection (see
TcpDiscoveryStatistics/ZookeeperDiscoveryStatistics).
> JmxMetricExporter fails to export discovery metrics
> ---
>
> Key: IGNITE-14376
> URL: https://issues.apache.org/jira/browse/IGNITE-14376
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Error:
> {code:java}
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -2java.lang.StringIndexOutOfBoundsException: String index out of range: -2
> at java.lang.String.substring(String.java:1931) at
> org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.lambda$getMBeanInfo$0(MetricRegistryMBean.java:105)
> at java.util.Iterator.forEachRemaining(Iterator.java:116) at
> org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getMBeanInfo(MetricRegistryMBean.java:85)
> at
> org.apache.ignite.spi.metric.jmx.MetricRegistryMBean.getAttribute(MetricRegistryMBean.java:58)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
> at
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
>
[jira] [Commented] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306991#comment-17306991 ] Sergey Chugunov commented on IGNITE-13976: -- [~ilyak], I have an idea of how turn WalDisableTest reproducer into a stable JUnit test, will try it. Also definitely check your changes about ClusterCachesInfo though they look reasonable at the first glance. > WAL disable/enable with node restarts results in mismatching state, data loss > - > > Key: IGNITE-13976 > URL: https://issues.apache.org/jira/browse/IGNITE-13976 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Sergey Chugunov >Priority: Critical > > If you try to enable/disable WAL on unstable topology, you will get to state > when WAL status is undefined, nodes might have different wall status and the > only way to fix it is to restart the cluster, which will lead to data loss > because ignite removes data if WAL is disabled on restart. > See the reproducer in PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12033:
Comment: was deleted
(was: {panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=5929811]]
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929778]]
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929757]]
* IgniteBasicTestSuite: StopNodeOrHaltFailureHandlerTest.testJvmHalted - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}JDBC Driver{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5929740]]
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testBigIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=EternalExpiryPolicy, backups=2,
evictionFactory=null, onheapCacheEnabled=false, writeSyncMode=FULL_SYNC,
persistenceEnabled=false] - Test has low fail rate in base branch 0,0% and is
not flaky
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testCharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929786]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 4 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5929793]]
* dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- History for base branch is absent.
* dll: CachePartitionedNearEnabledTest.TestCacheConfigurationExpiryPolicy -
Test has low fail rate in base branch 0,0% and is not flaky
* dll: CancellationTest.TestClosures - Test has low fail rate in base branch
0,8% and is not flaky
* dll: ComputeApiTestFullFooter.TestAffinityRun - Test has low fail rate in
base branch 1,7% and is not flaky
{color:#d04437}Web Sessions{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929749]]
{color:#d04437}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5929792]]
* exe: CancellationTest.TestClosures - Test has low fail rate in base branch
0,0% and is not flaky
* exe: ComputeApiTest.TestRunActionAsyncCancel - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929788]]
* IgnitePdsTestSuite:
DistributedConfigurationPersistentTest.testReadLocalValueOnInactiveGrid - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5929773]]
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationExecutesSynchronously -
PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=5929793]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
ComputeTestAsyncAwait.TestComputeAffinityRunAsyncContinuation - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#8b}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- FAILED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5929819buildTypeId=IgniteTests24Java8_RunAll])
> Callbacks from striped pool due to async/await may hang cluster
>
[jira] [Commented] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306956#comment-17306956
]
Ignite TC Bot commented on IGNITE-12033:
{panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=5929811]]
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929778]]
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929757]]
* IgniteBasicTestSuite: StopNodeOrHaltFailureHandlerTest.testJvmHalted - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}JDBC Driver{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5929740]]
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testBigIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=EternalExpiryPolicy, backups=2,
evictionFactory=null, onheapCacheEnabled=false, writeSyncMode=FULL_SYNC,
persistenceEnabled=false] - Test has low fail rate in base branch 0,0% and is
not flaky
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testCharDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=1, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929786]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 4 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5929793]]
* dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- History for base branch is absent.
* dll: CachePartitionedNearEnabledTest.TestCacheConfigurationExpiryPolicy -
Test has low fail rate in base branch 0,0% and is not flaky
* dll: CancellationTest.TestClosures - Test has low fail rate in base branch
0,8% and is not flaky
* dll: ComputeApiTestFullFooter.TestAffinityRun - Test has low fail rate in
base branch 1,7% and is not flaky
{color:#d04437}Web Sessions{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929749]]
{color:#d04437}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5929792]]
* exe: CancellationTest.TestClosures - Test has low fail rate in base branch
0,0% and is not flaky
* exe: ComputeApiTest.TestRunActionAsyncCancel - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929788]]
* IgnitePdsTestSuite:
DistributedConfigurationPersistentTest.testReadLocalValueOnInactiveGrid - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5929773]]
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationExecutesSynchronously -
PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=5929793]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
ComputeTestAsyncAwait.TestComputeAffinityRunAsyncContinuation - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#8b}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- FAILED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5929819buildTypeId=IgniteTests24Java8_RunAll]
> Callbacks from striped pool due to async/await may hang cluster
>
[jira] [Updated] (IGNITE-14348) Use classes with different version
[ https://issues.apache.org/jira/browse/IGNITE-14348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surkov Aleksandr updated IGNITE-14348: -- Attachment: use-different-classes.zip > Use classes with different version > -- > > Key: IGNITE-14348 > URL: https://issues.apache.org/jira/browse/IGNITE-14348 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Surkov Aleksandr >Priority: Major > Attachments: use-different-classes.zip > > > There may be a situation when the user saves objects with one version of the > class, and receives with another version. > For example, after adding or removing a field in the class, the value of the > serialVersionUID field may changed. > After that, two situations can occur: > # if user save object as value(key - SomeObject) or map(key - Map SomeObject>) then there will be no errors; > # if for value used list of SomeObject then there will be error; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14348) Use classes with different version
[ https://issues.apache.org/jira/browse/IGNITE-14348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surkov Aleksandr updated IGNITE-14348: -- Attachment: (was: use-different-classes.zip) > Use classes with different version > -- > > Key: IGNITE-14348 > URL: https://issues.apache.org/jira/browse/IGNITE-14348 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Surkov Aleksandr >Priority: Major > > There may be a situation when the user saves objects with one version of the > class, and receives with another version. > For example, after adding or removing a field in the class, the value of the > serialVersionUID field may changed. > After that, two situations can occur: > # if user save object as value(key - SomeObject) or map(key - Map SomeObject>) then there will be no errors; > # if for value used list of SomeObject then there will be error; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306918#comment-17306918 ] Ilya Kasnacheev commented on IGNITE-13976: -- [~sergey-chugunov] your fix seems to fix my reproducers. Can you please convert WalDisableTest to JUnit test? Also, can you re-check my own changes in that branch, especially ClusterCachesInfo one? > WAL disable/enable with node restarts results in mismatching state, data loss > - > > Key: IGNITE-13976 > URL: https://issues.apache.org/jira/browse/IGNITE-13976 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Sergey Chugunov >Priority: Critical > > If you try to enable/disable WAL on unstable topology, you will get to state > when WAL status is undefined, nodes might have different wall status and the > only way to fix it is to restart the cluster, which will lead to data loss > because ignite removes data if WAL is disabled on restart. > See the reproducer in PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14381) Failed to initialize DB connection- Unsupported connection setting "MULTI_THREADED"
[ https://issues.apache.org/jira/browse/IGNITE-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devansh Arora updated IGNITE-14381: --- Description: Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* fails to start with error org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] was: Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* fails to start with error |org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200]Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] > Failed to initialize DB connection- Unsupported connection setting > "MULTI_THREADED" > > > Key: IGNITE-14381 > URL: https://issues.apache.org/jira/browse/IGNITE-14381 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Devansh Arora >Priority: Major > > Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* > fails to start with error > > org.apache.ignite.internal.IgniteKernal:?|?|Exception during start > processors, node will be stopped and close connections > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > initialize DB connection: > jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported > connection setting "MULTI_THREADED" [90113-200] > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported > connection setting "MULTI_THREADED" [90113-200] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at > org.h2.message.DbException.getJdbcSQLException(DbException.java:429) > If we revert *h2* version to *1.4.197* it works. But this version has some > security vulnerabilities associated to it. > > [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14381) Failed to initialize DB connection- Unsupported connection setting "MULTI_THREADED"
[ https://issues.apache.org/jira/browse/IGNITE-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devansh Arora updated IGNITE-14381: --- Description: Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* fails to start with error |org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200]Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] was: Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* fails to start with error 2021-03-23 07:56:47.506Z|proxy-agent|DIPUPTWIN201204|[main]|ERROR|||1|org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200]Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] > Failed to initialize DB connection- Unsupported connection setting > "MULTI_THREADED" > > > Key: IGNITE-14381 > URL: https://issues.apache.org/jira/browse/IGNITE-14381 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Devansh Arora >Priority: Major > > Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* > fails to start with error > |org.apache.ignite.internal.IgniteKernal:?|?|Exception during start > processors, node will be stopped and close connections > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > initialize DB connection: > jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported > connection setting "MULTI_THREADED" [90113-200]Caused by: > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection > setting "MULTI_THREADED" [90113-200] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at > org.h2.message.DbException.getJdbcSQLException(DbException.java:429) > If we revert *h2* version to *1.4.197* it works. But this version has some > security vulnerabilities associated to it. > > [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] -- This message was sent by Atlassian Jira
[jira] [Updated] (IGNITE-14381) Failed to initialize DB connection- Unsupported connection setting "MULTI_THREADED"
[ https://issues.apache.org/jira/browse/IGNITE-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devansh Arora updated IGNITE-14381: --- Priority: Major (was: Blocker) > Failed to initialize DB connection- Unsupported connection setting > "MULTI_THREADED" > > > Key: IGNITE-14381 > URL: https://issues.apache.org/jira/browse/IGNITE-14381 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Devansh Arora >Priority: Major > > Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* > fails to start with error > 2021-03-23 > 07:56:47.506Z|proxy-agent|DIPUPTWIN201204|[main]|ERROR|||1|org.apache.ignite.internal.IgniteKernal:?|?|Exception > during start processors, node will be stopped and close connections > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > initialize DB connection: > jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported > connection setting "MULTI_THREADED" [90113-200]Caused by: > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection > setting "MULTI_THREADED" [90113-200] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at > org.h2.message.DbException.getJdbcSQLException(DbException.java:429) > If we revert *h2* version to *1.4.197* it works. But this version has some > security vulnerabilities associated to it. > > [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14381) Failed to initialize DB connection- Unsupported connection setting "MULTI_THREADED"
[ https://issues.apache.org/jira/browse/IGNITE-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devansh Arora updated IGNITE-14381: --- Description: Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* fails to start with error 2021-03-23 07:56:47.506Z|proxy-agent|DIPUPTWIN201204|[main]|ERROR|||1|org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200]Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] was: Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* application fails to start with error 2021-03-23 07:56:47.506Z|proxy-agent|DIPUPTWIN201204|[main]|ERROR|||1|org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200]Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] > Failed to initialize DB connection- Unsupported connection setting > "MULTI_THREADED" > > > Key: IGNITE-14381 > URL: https://issues.apache.org/jira/browse/IGNITE-14381 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.10 >Reporter: Devansh Arora >Priority: Blocker > > Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* > fails to start with error > 2021-03-23 > 07:56:47.506Z|proxy-agent|DIPUPTWIN201204|[main]|ERROR|||1|org.apache.ignite.internal.IgniteKernal:?|?|Exception > during start processors, node will be stopped and close connections > org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to > initialize DB connection: > jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine > Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported > connection setting "MULTI_THREADED" [90113-200]Caused by: > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection > setting "MULTI_THREADED" [90113-200] at > org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at > org.h2.message.DbException.getJdbcSQLException(DbException.java:429) > If we revert *h2* version to *1.4.197* it works. But this version has some > security vulnerabilities associated to it. > >
[jira] [Created] (IGNITE-14381) Failed to initialize DB connection- Unsupported connection setting "MULTI_THREADED"
Devansh Arora created IGNITE-14381: -- Summary: Failed to initialize DB connection- Unsupported connection setting "MULTI_THREADED" Key: IGNITE-14381 URL: https://issues.apache.org/jira/browse/IGNITE-14381 Project: Ignite Issue Type: Bug Affects Versions: 2.10 Reporter: Devansh Arora Our Application with dependency to *ignite spring 2.10.0* and *h2 1.4.200* application fails to start with error 2021-03-23 07:56:47.506Z|proxy-agent|DIPUPTWIN201204|[main]|ERROR|||1|org.apache.ignite.internal.IgniteKernal:?|?|Exception during start processors, node will be stopped and close connections org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem:9feea9ed-f89e-4818-b9d7-638749a474d2;LOCK_MODE=3;MULTI_THREADED=1;DB_CLOSE_ON_EXIT=FALSE;DEFAULT_LOCK_TIMEOUT=1;FUNCTIONS_IN_SCHEMA=true;OPTIMIZE_REUSE_RESULTS=0;QUERY_CACHE_SIZE=0;MAX_OPERATION_MEMORY=0;BATCH_JOINS=1;ROW_FACTORY="org.apache.ignite.internal.processors.query.h2.opt.H2PlainRowFactory";DEFAULT_TABLE_ENGINE=org.apache.ignite.internal.processors.query.h2.opt.GridH2DefaultTableEngine Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200]Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported connection setting "MULTI_THREADED" [90113-200] at org.h2.message.DbException.getJdbcSQLException(DbException.java:622) at org.h2.message.DbException.getJdbcSQLException(DbException.java:429) If we revert *h2* version to *1.4.197* it works. But this version has some security vulnerabilities associated to it. [https://www.cvedetails.com/vulnerability-list/vendor_id-17893/product_id-45580/version_id-243447/H2database-H2-1.4.197.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14380) Move certificates for ducktape tests to a separate directory
Mikhail Filatov created IGNITE-14380: Summary: Move certificates for ducktape tests to a separate directory Key: IGNITE-14380 URL: https://issues.apache.org/jira/browse/IGNITE-14380 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Looking for certificates in directory install_root/ignite-dev/modules/ducktests/tests/certs/ seems a bit strange. If you run a ducktests not using run_tests.sh (for example: in AWS, or Vagrand env.), certificates are generates in separate step, and have no connection with Ignite sources. Seeam more universal if we place them in install_root/certs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[ https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306894#comment-17306894 ] Ilya Kasnacheev commented on IGNITE-14379: -- [~antkr] please review this fix. > Fix vulnerability of commons-codec <1.13 > > > Key: IGNITE-14379 > URL: https://issues.apache.org/jira/browse/IGNITE-14379 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0379 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[ https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14379: - Reviewer: Anton Kurbanov > Fix vulnerability of commons-codec <1.13 > > > Key: IGNITE-14379 > URL: https://issues.apache.org/jira/browse/IGNITE-14379 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0379 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[
https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14379:
-
Comment: was deleted
(was: {panel:title=Branch: [pull/8915/head] Base: [master] : Possible Blockers
(110)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5928170]]
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServersFail1_8 - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 1{color} [[tests 19 TIMEOUT , Out Of Memory Error , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=5928149]]
* IgniteBasicTestSuite: GridMbeansMiscTest.testMbeansSet1 - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: GridMbeansMiscTest.testMbeansSet2 - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressInvalidHost - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: OdbcConfigurationValidationSelfTest.testThreadPoolSize
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: OdbcConfigurationValidationSelfTest.testAddressHostOnly
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testConnectionParams - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressHostAndPort - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressInvalidFormat - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite: OdbcConfigurationValidationSelfTest.testAddressDefault
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcConfigurationValidationSelfTest.testAddressHostAndPortRange - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteBasicTestSuite:
OdbcEscapeSequenceSelfTest.testTimeEscapeSequenceWithWhitespaces - Test has low
fail rate in base branch 0,0% and is not flaky
... and 8 tests blockers
{color:#d04437}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5928178]]
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsBinaryMetadataAsyncWritingTest.testParallelUpdatesToBinaryMetadata -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 1{color} [[tests 86 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=5928180]]
* org.apache.ignite.testsuites.IgnitePdsTestSuite:
org.apache.ignite.internal.processors.diagnostic.DiagnosticProcessorTest. -
History for base branch is absent.
* org.apache.ignite.testsuites.IgnitePdsTestSuite:
org.apache.ignite.internal.processors.metastorage.DistributedMetaStoragePersistentTest.
- History for base branch is absent.
* IgnitePdsTestSuite:
PageMemoryLazyAllocationWithPDSTest.testCreateCacheFailsInHugeMemoryRegion -
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
PageMemoryLazyAllocationWithPDSTest.testCreateCacheFromClientFailsInHugeMemoryRegion
- Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite: ActiveOnStartPropertyTest.testInMemoryInactive - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite: ActiveOnStartPropertyTest.testInMemoryActive - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testInactiveInactiveOnStartInMemory - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testActiveDisableAutoActivation - Test has low
fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testReadOnlyInactiveOnStartInMemory - Test has
low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite: ClusterStateOnStartPropertyTest.testInactiveInMemory -
Test has low fail rate in base branch 0,0% and is not flaky
* IgnitePdsTestSuite:
ClusterStateOnStartPropertyTest.testInactiveActiveOnStartInMemory - Test has
low fail rate in base branch 0,0% and is not flaky
... and 75 tests blockers
{color:#d04437}Platform C++ CMake (Linux Clang){color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=5928201]]
{panel}
{panel:title=Branch: [pull/8915/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}PDS 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5928180]]
* {color:#8b}org.apache.ignite.testsuites.IgnitePdsTestSuite:
org.apache.ignite.internal.processors.diagnostic.DiagnosticProcessorTest. -
FAILED{color}
*
[jira] [Commented] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[
https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306889#comment-17306889
]
Ignite TC Bot commented on IGNITE-14379:
{panel:title=Branch: [pull/8915/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8915/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5928211buildTypeId=IgniteTests24Java8_RunAll]
> Fix vulnerability of commons-codec <1.13
>
>
> Key: IGNITE-14379
> URL: https://issues.apache.org/jira/browse/IGNITE-14379
> Project: Ignite
> Issue Type: Bug
> Components: build
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0379
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-12033) Callbacks from striped pool due to async/await may hang cluster
[
https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12033:
Comment: was deleted
(was: {panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929185]]
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiThreadedSelfTest.testPessimisticReadCommittedCommitMultithreaded
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929158]]
* IgniteSpiTestSuite:
GridTcpCommunicationSpiSkipWaitHandshakeOnClientTest.clientCanNotSendHandshakeWaitMessage
- Test has low fail rate in base branch 1,3% and is not flaky
{color:#d04437}Platform .NET (Long Running){color} [[tests 0 Exit Code ,
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=5929207]]
{color:#d04437}JDBC Driver{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929151]]
* IgniteJdbcDriverTestSuite:
JdbcThinJdbcToCacheDataTypesCoverageTest.testIntDataType[atomicityMode=ATOMIC,
cacheMode=PARTITIONED, ttlFactory=null, backups=0, evictionFactory=null,
onheapCacheEnabled=false, writeSyncMode=FULL_SYNC, persistenceEnabled=false] -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929184]]
* IgniteBinaryCacheTestSuite:
GridCacheBalancingStoreSelfTest.testConcurrentLoadAllCustomThreshold - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5929197]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 2 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5929204]]
* dll: ComputeApiTest.TestRunActionAsyncCancel - Test has low fail rate in base
branch 0,0% and is not flaky
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET{color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=5929203]]
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5929199]]
* IgnitePdsTestSuite:
IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateSimple_5_Servers_5_Clients_FromClient
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (NuGet)*{color} [[tests 0 Exit Code , Compilation
Error |https://ci.ignite.apache.org/viewLog.html?buildId=5929208]]
{color:#d04437}Platform .NET (Integrations){color} [[tests 0 Exit Code ,
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=5929206]]
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Exit Code ,
Compilation Error , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=5929205]]
{panel}
{panel:title=Branch: [pull/8870/head] Base: [master] : New Tests
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5929184]]
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testLocalOperationExecutesSynchronously
- PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationExecutorTest.testLocalOperationExecutesSynchronously -
PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
CacheAsyncContinuationSynchronousExecutorTest.testRemoteOperationContinuesOnDefaultExecutor
- PASSED{color}
{color:#8b}Platform .NET (Core Linux){color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=5929204]]
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeExecuteAsyncContinuation
- PASSED{color}
* {color:#013220}dll: ComputeTestAsyncAwait.TestComputeRunAsyncContinuation -
PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestSynchronousExecutorRunsContinuationsOnStripedPool -
PASSED{color}
* {color:#013220}dll:
ComputeTestAsyncAwait.TestComputeAffinityRunAsyncContinuation - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestInvalidExecutorConfigurationFailsOnStart - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestLocalOperationExecutesSynchronously - PASSED{color}
* {color:#013220}dll:
CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5929230buildTypeId=IgniteTests24Java8_RunAll])
>
