[jira] [Updated] (IGNITE-12699) .NET: Remove TypeCaster
[
https://issues.apache.org/jira/browse/IGNITE-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12699:
Fix Version/s: 2.10
> .NET: Remove TypeCaster
> ---
>
> Key: IGNITE-12699
> URL: https://issues.apache.org/jira/browse/IGNITE-12699
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.10
>
>
> TypeCaster class is used in Ignite.NET for non-boxing, faster casts.
> Benchmarks on .NET 4.0 displayed clear advantage of this solution.
> However, this is no longer true on .NET Core due to improvements in the
> framework:
> {code}
> | Method | Runtime | Mean | Error |StdDev |
> |--- |-- |--:|--:|--:|
> | TypeCaster | .NET Core 2.2 | 3.4615 ns | 0.0325 ns | 0.0304 ns |
> | ObjectCast | .NET Core 2.2 | 1.0936 ns | 0.0040 ns | 0.0036 ns |
> | UnsafeCast | .NET Core 2.2 | 4.1921 ns | 0.0125 ns | 0.0111 ns |
> | TypeCaster | .NET Core 3.1 | 1.5306 ns | 0.0042 ns | 0.0037 ns |
> | ObjectCast | .NET Core 3.1 | 0.0229 ns | 0.0029 ns | 0.0024 ns |
> | UnsafeCast | .NET Core 3.1 | 2.1868 ns | 0.0052 ns | 0.0043 ns |
> {code}
> (See benchmark code in https://github.com/ptupitsyn/IgniteNetBenchmarks)
> Remove TypeCaster class and use regular cast instead.
> Run Ignite deserialization benchmarks to confirm the effect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13520) Сlient node with a static encrypted cache configuration can generate an encryption key when joining.
[ https://issues.apache.org/jira/browse/IGNITE-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229017#comment-17229017 ] Pavel Pereslegin edited comment on IGNITE-13520 at 11/10/20, 7:27 AM: -- [~nizhikov], take a look at these changes, please. was (Author: xtern): [~nizhikov], take a look at these changes. > Сlient node with a static encrypted cache configuration can generate an > encryption key when joining. > > > Key: IGNITE-13520 > URL: https://issues.apache.org/jira/browse/IGNITE-13520 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: encryption > Fix For: 2.10 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently, when a client node joins a cluster with a static encrypted cache > configuration, it generates an encryption key for that cache and sends it to > the cluster (just like the server node does). > _SpringEncryptedCacheRestartClientTest_ reproduces this behavior and it is > unexpected, it happens due to IGNITE-13567 (see > _GridEncryptionManager#collectJoiningNodeData_). > The client node should not generate encryption keys and should be able to > start without configuring EncryptionSPI. > After doing some research on possible solutions, we decided to reject node > joining in such a situation, because there is no clean and simple way to > distribute the same encryption key between server nodes that are already in > the cluster (we have to either add discovery overhead, block the exchange, or > add an additional exchange to be able to distribute keys between server nodes > that are already in the cluster). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13520) Сlient node with a static encrypted cache configuration can generate an encryption key when joining.
[ https://issues.apache.org/jira/browse/IGNITE-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229017#comment-17229017 ] Pavel Pereslegin commented on IGNITE-13520: --- [~nizhikov], take a look at these changes. > Сlient node with a static encrypted cache configuration can generate an > encryption key when joining. > > > Key: IGNITE-13520 > URL: https://issues.apache.org/jira/browse/IGNITE-13520 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: encryption > Fix For: 2.10 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently, when a client node joins a cluster with a static encrypted cache > configuration, it generates an encryption key for that cache and sends it to > the cluster (just like the server node does). > _SpringEncryptedCacheRestartClientTest_ reproduces this behavior and it is > unexpected, it happens due to IGNITE-13567 (see > _GridEncryptionManager#collectJoiningNodeData_). > The client node should not generate encryption keys and should be able to > start without configuring EncryptionSPI. > After doing some research on possible solutions, we decided to reject node > joining in such a situation, because there is no clean and simple way to > distribute the same encryption key between server nodes that are already in > the cluster (we have to either add discovery overhead, block the exchange, or > add an additional exchange to be able to distribute keys between server nodes > that are already in the cluster). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13686) Compression test become failed after IGNITE-13658.
[
https://issues.apache.org/jira/browse/IGNITE-13686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228990#comment-17228990
]
Stanilovsky Evgeny commented on IGNITE-13686:
-
got it, thanks, TC in progress.
> Compression test become failed after IGNITE-13658.
> --
>
> Key: IGNITE-13686
> URL: https://issues.apache.org/jira/browse/IGNITE-13686
> Project: Ignite
> Issue Type: Improvement
> Components: data structures
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [1] was merged persistent check become fail to pass
> {noformat}
> if (diskPageCompression != DiskPageCompression.DISABLED) {
> if (!cctx.dataRegion().config().isPersistenceEnabled())
> throw new IgniteCheckedException("Disk page compression makes
> sense only with enabled persistence.");
> {noformat} I suggest to remove failed smoke tests :
> IgnitePersistentStoreDataStructuresTest
> [1] https://issues.apache.org/jira/browse/IGNITE-13658
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13689) Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean
[ https://issues.apache.org/jira/browse/IGNITE-13689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228942#comment-17228942 ] Alexand Polyakov commented on IGNITE-13689: --- Run TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll/5726883 > Extend test coverage [IGNITE-11512] Add counter left partition for index > rebuild in CacheGroupMetricsMXBean > --- > > Key: IGNITE-13689 > URL: https://issues.apache.org/jira/browse/IGNITE-13689 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Labels: test > Time Spent: 10m > Remaining Estimate: 0h > > New test: > Partial rebuild > # Start cluster, load data with indexes > # Kill single node, create new index, start node. > # Make sure that index rebuild count is in range of total new index size and > 0 and decreasing > # Wait until rebuild finished, assert that no index errors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13689) Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean
[ https://issues.apache.org/jira/browse/IGNITE-13689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228940#comment-17228940 ] Alexand Polyakov commented on IGNITE-13689: --- Create branch https://github.com/gridgain/apache-ignite/tree/ignite-13689 > Extend test coverage [IGNITE-11512] Add counter left partition for index > rebuild in CacheGroupMetricsMXBean > --- > > Key: IGNITE-13689 > URL: https://issues.apache.org/jira/browse/IGNITE-13689 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Labels: test > Time Spent: 10m > Remaining Estimate: 0h > > New test: > Partial rebuild > # Start cluster, load data with indexes > # Kill single node, create new index, start node. > # Make sure that index rebuild count is in range of total new index size and > 0 and decreasing > # Wait until rebuild finished, assert that no index errors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13689) Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean
[ https://issues.apache.org/jira/browse/IGNITE-13689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228941#comment-17228941 ] Alexand Polyakov commented on IGNITE-13689: --- Create pull request https://github.com/apache/ignite/pull/8444 > Extend test coverage [IGNITE-11512] Add counter left partition for index > rebuild in CacheGroupMetricsMXBean > --- > > Key: IGNITE-13689 > URL: https://issues.apache.org/jira/browse/IGNITE-13689 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Labels: test > Time Spent: 10m > Remaining Estimate: 0h > > New test: > Partial rebuild > # Start cluster, load data with indexes > # Kill single node, create new index, start node. > # Make sure that index rebuild count is in range of total new index size and > 0 and decreasing > # Wait until rebuild finished, assert that no index errors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13689) Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean
Alexand Polyakov created IGNITE-13689: - Summary: Extend test coverage [IGNITE-11512] Add counter left partition for index rebuild in CacheGroupMetricsMXBean Key: IGNITE-13689 URL: https://issues.apache.org/jira/browse/IGNITE-13689 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.9 Reporter: Alexand Polyakov Assignee: Alexand Polyakov New test: Partial rebuild # Start cluster, load data with indexes # Kill single node, create new index, start node. # Make sure that index rebuild count is in range of total new index size and 0 and decreasing # Wait until rebuild finished, assert that no index errors -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228884#comment-17228884 ] Alexand Polyakov commented on IGNITE-13687: --- Link TC bot https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/8441/head=Latest > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228883#comment-17228883 ] Alexand Polyakov edited comment on IGNITE-13687 at 11/10/20, 12:48 AM: --- Run TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll/5726394 was (Author: a-polyakov): Run TC Run TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll/5726394 > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228883#comment-17228883 ] Alexand Polyakov commented on IGNITE-13687: --- Run TC Run TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll/5726394 > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13357) .NET: Add includeExpired to ContinuousQuery
[
https://issues.apache.org/jira/browse/IGNITE-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228806#comment-17228806
]
Ignite TC Bot commented on IGNITE-13357:
{panel:title=Branch: [pull/8443/head] Base: [master] : Possible Blockers
(69)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 0 Exit Code ,
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=5724653]]
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE
|https://ci.ignite.apache.org/viewLog.html?buildId=5724650]]
* dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5724657]]
* ZookeeperDiscoverySpiTestSuite3:
GridCacheReplicatedNodeRestartSelfTest.testRestart - Test has low fail rate in
base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite3:
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict
- Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testMasterNodeLeave
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5724655]]
{color:#d04437}Platform C++ (Win x64 / Release){color} [[tests 14
BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=5724606]]
* IgniteCoreTest: ContinuousQueryTestSuite: TestBasic - Test has low fail rate
in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScan - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQuerySql - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryText - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestBasicNoExcept - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScanNoExcept - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQuerySqlNoExcept - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryTextNoExcept - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestExpiredQuery - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestSetGetLocal - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestGetSetBufferSize - Test has low
fail rate in base branch 0,0% and is not flaky
... and 3 tests blockers
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests 14 Exit
Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=5724684]]
* IgniteCoreTest: ContinuousQueryTestSuite: TestBasic - Test has low fail rate
in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScan - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQuerySql - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryText - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestBasicNoExcept - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScanNoExcept - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQuerySqlNoExcept - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryTextNoExcept - Test
has low fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestExpiredQuery - Test has low
fail rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestSetGetLocal - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteCoreTest: ContinuousQueryTestSuite: TestGetSetBufferSize - Test has low
fail rate in base branch 0,0% and is not flaky
... and 3 tests blockers
{color:#d04437}Platform .NET{color} [[tests 0 Exit Code , Compilation Error
|https://ci.ignite.apache.org/viewLog.html?buildId=5724649]]
{color:#d04437}Platform C++ CMake (Linux){color} [[tests 14 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5724681]]
*
[jira] [Updated] (IGNITE-13678) Extend test coverage for persistence files directory
[ https://issues.apache.org/jira/browse/IGNITE-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13678: - Fix Version/s: (was: 2.9.1) 2.10 > Extend test coverage for persistence files directory > > > Key: IGNITE-13678 > URL: https://issues.apache.org/jira/browse/IGNITE-13678 > Project: Ignite > Issue Type: Test >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Minor > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > I think it would be nice to additionally test the change introduced by > IGNITE-12057. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13678) Extend test coverage for persistence files directory
[ https://issues.apache.org/jira/browse/IGNITE-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13678: - Description: I think it would be nice to additionally test the change introduced by IGNITE-12057. > Extend test coverage for persistence files directory > > > Key: IGNITE-13678 > URL: https://issues.apache.org/jira/browse/IGNITE-13678 > Project: Ignite > Issue Type: Test >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Minor > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > > I think it would be nice to additionally test the change introduced by > IGNITE-12057. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13678) Extend test coverage for persistence files directory
[ https://issues.apache.org/jira/browse/IGNITE-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13678: - Ignite Flags: (was: Docs Required,Release Notes Required) > Extend test coverage for persistence files directory > > > Key: IGNITE-13678 > URL: https://issues.apache.org/jira/browse/IGNITE-13678 > Project: Ignite > Issue Type: Test >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Minor > Fix For: 2.9.1 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
[
https://issues.apache.org/jira/browse/IGNITE-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228765#comment-17228765
]
Ivan Daschinskiy commented on IGNITE-13665:
---
[~ilyak] As for me, fix is ok, but could you please add some test? I suppose
it's quite easy (take one from my closed PR for example)
> Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
> --
>
> Key: IGNITE-13665
> URL: https://issues.apache.org/jira/browse/IGNITE-13665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: 2.9.1-rc
> Fix For: 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When failure handler catches an issue in striped pool, maybe in some other
> cases, thread dump is as folows:
> {code}
> [2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible
> failure suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]]
> org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:296)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:265)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core.jar]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> {code}
> when the actual stack trace from the relevant thread is hidden somewhere deep
> below. And may even be suppressed. This is a usability nightmare.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
[
https://issues.apache.org/jira/browse/IGNITE-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228764#comment-17228764
]
Ilya Kasnacheev commented on IGNITE-13665:
--
[~ivandasch] [~nizhikov] please review this quick and dirty fix to put it into
2.9.1
> Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
> --
>
> Key: IGNITE-13665
> URL: https://issues.apache.org/jira/browse/IGNITE-13665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: 2.9.1-rc
> Fix For: 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When failure handler catches an issue in striped pool, maybe in some other
> cases, thread dump is as folows:
> {code}
> [2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible
> failure suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]]
> org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:296)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:265)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core.jar]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> {code}
> when the actual stack trace from the relevant thread is hidden somewhere deep
> below. And may even be suppressed. This is a usability nightmare.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
[
https://issues.apache.org/jira/browse/IGNITE-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-13665:
-
Comment: was deleted
(was: {panel:title=Branch: [pull/8442/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests 0
BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=5724443]]
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724364]]
* ZookeeperDiscoverySpiTestSuite2:
IgniteClientReconnectCacheTest.testReconnectMultinode - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}Cache (Failover) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724380]]
* IgniteCacheFailoverTestSuite2:
GridCachePartitionedFailoverSelfTest.testOptimisticRepeatableReadTxTopologyChange
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8442/head] Base: [master] : New Tests
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724391]]
* {color:#013220}IgniteCacheTestSuite5:
GridCacheHashMapPutAllWarningsTest.testHashMapAtomic - PASSED{color}
{color:#8b}Cache 1{color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=5724387]]
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=LOCAL,
writeThrough=false, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=REPLICATED,
writeThrough=true, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=LOCAL,
writeThrough=true, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=PARTITIONED,
writeThrough=true, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=PARTITIONED,
writeThrough=false, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=REPLICATED,
writeThrough=false, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=PARTITIONED,
writeThrough=false, near=true] - PASSED{color}
{color:#8b}MVCC Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724426]]
* {color:#013220}IgniteCacheMvccTestSuite5:
GridCacheHashMapPutAllWarningsTest.testHashMapAtomic - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=572buildTypeId=IgniteTests24Java8_RunAll])
> Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
> --
>
> Key: IGNITE-13665
> URL: https://issues.apache.org/jira/browse/IGNITE-13665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: 2.9.1-rc
> Fix For: 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When failure handler catches an issue in striped pool, maybe in some other
> cases, thread dump is as folows:
> {code}
> [2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible
> failure suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]]
> org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> [ignite-core.jar]
> at
>
[jira] [Commented] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
[
https://issues.apache.org/jira/browse/IGNITE-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228761#comment-17228761
]
Ignite TC Bot commented on IGNITE-13665:
{panel:title=Branch: [pull/8442/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8442/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724391]]
* {color:#013220}IgniteCacheTestSuite5:
GridCacheHashMapPutAllWarningsTest.testHashMapAtomic - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=572buildTypeId=IgniteTests24Java8_RunAll]
> Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
> --
>
> Key: IGNITE-13665
> URL: https://issues.apache.org/jira/browse/IGNITE-13665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: 2.9.1-rc
> Fix For: 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When failure handler catches an issue in striped pool, maybe in some other
> cases, thread dump is as folows:
> {code}
> [2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible
> failure suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]]
> org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:296)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:265)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core.jar]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> {code}
> when the actual stack trace from the relevant thread is hidden somewhere deep
> below. And may even be suppressed. This is a usability nightmare.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
[ https://issues.apache.org/jira/browse/IGNITE-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13244: - Ignite Flags: (was: Docs Required,Release Notes Required) > Transaction commit completes successfully if partition is lost on commit phase > -- > > Key: IGNITE-13244 > URL: https://issues.apache.org/jira/browse/IGNITE-13244 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Attachments: tx_commit_partition_loss.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Reproducer is attached. > Steps: > 1) Run startNode() > 2) Run poorTransaction() in a separate JVM > 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint > 4) kill -9 first node while hanging on breakpoint > 5) Result: tx.commit() succeeds, data is commited in partition 1 and not > commited in partition 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
[ https://issues.apache.org/jira/browse/IGNITE-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13244: - Fix Version/s: 2.10 > Transaction commit completes successfully if partition is lost on commit phase > -- > > Key: IGNITE-13244 > URL: https://issues.apache.org/jira/browse/IGNITE-13244 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Fix For: 2.10 > > Attachments: tx_commit_partition_loss.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Reproducer is attached. > Steps: > 1) Run startNode() > 2) Run poorTransaction() in a separate JVM > 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint > 4) kill -9 first node while hanging on breakpoint > 5) Result: tx.commit() succeeds, data is commited in partition 1 and not > commited in partition 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13209) JavaIgniteCatalogExample doesn't work with a standalone Spark cluster
[
https://issues.apache.org/jira/browse/IGNITE-13209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-13209:
Assignee: (was: Valentin Kulichenko)
> JavaIgniteCatalogExample doesn't work with a standalone Spark cluster
> -
>
> Key: IGNITE-13209
> URL: https://issues.apache.org/jira/browse/IGNITE-13209
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.8.1
>Reporter: Valentin Kulichenko
>Priority: Major
>
> To reproduce the issue:
> # Start Spark master and slave as described here:
> [http://spark.apache.org/docs/latest/spark-standalone.html]
> # Change the master URL in the {{JavaIgniteCatalogExample}} from "local" to
> the one just started.
> # Run the example.
> Updated code that creates the {{IgniteSparkSession}}:
> {code:java}
> String libs =
> "/Users/vkulichenko/GridGain/releases/apache-ignite-2.8.1-bin/libs";
>
> IgniteSparkSession igniteSession = IgniteSparkSession.builder()
> .appName("Spark Ignite catalog example")
> .master("spark://Valentin-Kulichenko-MacBook-Pro-1772.local:7077")
> .config("spark.executor.instances", "2")
> .config("spark.executor.extraClassPath", libs + "/*" + ":" + libs +
> "/ignite-spark/*:" + libs + "/ignite-spring/*")
> .igniteConfig(CONFIG)
> .getOrCreate();
> {code}
> Execution fails with this exception:
> {noformat}
> [2020-07-02 15:50:27,627][ERROR][task-result-getter-3][TaskSetManager] Task 0
> in stage 0.0 failed 4 times; aborting job
> Exception in thread "main" org.apache.spark.SparkException: Job aborted due
> to stage failure: Task 0 in stage 0.0 failed 4 times, most recent failure:
> Lost task 0.3 in stage 0.0 (TID 3, 10.0.0.11, executor 0): class
> org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided
> name doesn't exist. Did you call Ignition.start(..) to start an Ignite
> instance? [name=testing]
> at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1351)
> at org.apache.ignite.Ignition.ignite(Ignition.java:528)
> at org.apache.ignite.spark.impl.package$.ignite(package.scala:65)
> at
> org.apache.ignite.spark.impl.IgniteRelationProvider$$anonfun$configProvider$1$2.apply(IgniteRelationProvider.scala:238)
> at
> org.apache.ignite.spark.impl.IgniteRelationProvider$$anonfun$configProvider$1$2.apply(IgniteRelationProvider.scala:235)
> at org.apache.ignite.spark.Once.apply(IgniteContext.scala:222)
> at org.apache.ignite.spark.IgniteContext.ignite(IgniteContext.scala:144)
> at
> org.apache.ignite.spark.impl.IgniteSQLDataFrameRDD.compute(IgniteSQLDataFrameRDD.scala:65)
> at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324)
> at org.apache.spark.rdd.RDD.iterator(RDD.scala:288)
> at
> org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
> at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324)
> at org.apache.spark.rdd.RDD.iterator(RDD.scala:288)
> at
> org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
> at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324)
> at org.apache.spark.rdd.RDD.iterator(RDD.scala:288)
> at
> org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
> at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324)
> at org.apache.spark.rdd.RDD.iterator(RDD.scala:288)
> at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
> at org.apache.spark.scheduler.Task.run(Task.scala:109)
> at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:345)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13662) Describe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228735#comment-17228735 ] Denis A. Magda commented on IGNITE-13662: - Thanks for looping me in. Please check the feedback in git. > Describe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Denis A. Magda >Priority: Minor > Fix For: 2.10 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase
[ https://issues.apache.org/jira/browse/IGNITE-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228727#comment-17228727 ] Alexey Scherbakov commented on IGNITE-13244: [~Sergey Uttsel] LGTM. Merged to master #f6ba904a3fcb6cbaacc19001eaa2a7b71836fbce > Transaction commit completes successfully if partition is lost on commit phase > -- > > Key: IGNITE-13244 > URL: https://issues.apache.org/jira/browse/IGNITE-13244 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Attachments: tx_commit_partition_loss.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Reproducer is attached. > Steps: > 1) Run startNode() > 2) Run poorTransaction() in a separate JVM > 3) Hang first node in GridCacheMapEntry#innerSet with a breakpoint > 4) kill -9 first node while hanging on breakpoint > 5) Result: tx.commit() succeeds, data is commited in partition 1 and not > commited in partition 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
[
https://issues.apache.org/jira/browse/IGNITE-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228712#comment-17228712
]
Ignite TC Bot commented on IGNITE-13665:
{panel:title=Branch: [pull/8442/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ CMake (Win x64 / Release){color} [[tests 0
BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=5724443]]
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724364]]
* ZookeeperDiscoverySpiTestSuite2:
IgniteClientReconnectCacheTest.testReconnectMultinode - Test has low fail rate
in base branch 0,0% and is not flaky
{color:#d04437}Cache (Failover) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724380]]
* IgniteCacheFailoverTestSuite2:
GridCachePartitionedFailoverSelfTest.testOptimisticRepeatableReadTxTopologyChange
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8442/head] Base: [master] : New Tests
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724391]]
* {color:#013220}IgniteCacheTestSuite5:
GridCacheHashMapPutAllWarningsTest.testHashMapAtomic - PASSED{color}
{color:#8b}Cache 1{color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=5724387]]
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=LOCAL,
writeThrough=false, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=REPLICATED,
writeThrough=true, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=LOCAL,
writeThrough=true, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=PARTITIONED,
writeThrough=true, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=PARTITIONED,
writeThrough=false, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=REPLICATED,
writeThrough=false, near=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheTestSuite:
IgniteCacheAtomicConcurrentUnorderedUpdateAllTest.testConcurrentUpdateAll[cacheMode=PARTITIONED,
writeThrough=false, near=true] - PASSED{color}
{color:#8b}MVCC Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5724426]]
* {color:#013220}IgniteCacheMvccTestSuite5:
GridCacheHashMapPutAllWarningsTest.testHashMapAtomic - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=572buildTypeId=IgniteTests24Java8_RunAll]
> Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
> --
>
> Key: IGNITE-13665
> URL: https://issues.apache.org/jira/browse/IGNITE-13665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: 2.9.1-rc
> Fix For: 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When failure handler catches an issue in striped pool, maybe in some other
> cases, thread dump is as folows:
> {code}
> [2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible
> failure suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]]
> org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> [ignite-core.jar]
> at
>
[jira] [Updated] (IGNITE-13653) Don't print warning if unordered map used for bulk update operation on atomic cache
[ https://issues.apache.org/jira/browse/IGNITE-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-13653: - Fix Version/s: 2.9.1 > Don't print warning if unordered map used for bulk update operation on atomic > cache > --- > > Key: IGNITE-13653 > URL: https://issues.apache.org/jira/browse/IGNITE-13653 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: 2.9.1-rc > Fix For: 2.10, 2.9.1 > > Time Spent: 40m > Remaining Estimate: 0h > > Since IGNITE-12451 is resolved there no more deadlock possible for atomic > caches and it's safe to use HashMap and other unordered maps as argument of > putAll/removeAll/invokeAll operations on atomic caches. Warning, introduced > by IGNITE-6804, is not required anymore. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13357) .NET: Add includeExpired to ContinuousQuery
[ https://issues.apache.org/jira/browse/IGNITE-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228692#comment-17228692 ] Igor Sapego commented on IGNITE-13357: -- [~ptupitsyn] looks good to me. > .NET: Add includeExpired to ContinuousQuery > --- > > Key: IGNITE-13357 > URL: https://issues.apache.org/jira/browse/IGNITE-13357 > Project: Ignite > Issue Type: Improvement > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Original Estimate: 6h > Time Spent: 2h 10m > Remaining Estimate: 1h > > Add includeExpired flag to ContinuousQuery (thick and thin modes) to track > entry expiration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13665) Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
[
https://issues.apache.org/jira/browse/IGNITE-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-13665:
-
Labels: 2.9.1-rc (was: )
> Useless failure trace "IgnitionEx$IgniteNamedInstance$2.apply"
> --
>
> Key: IGNITE-13665
> URL: https://issues.apache.org/jira/browse/IGNITE-13665
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Critical
> Labels: 2.9.1-rc
> Fix For: 2.9.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When failure handler catches an issue in striped pool, maybe in some other
> cases, thread dump is as folows:
> {code}
> [2020-10-10T10:10:10,100][WARN ][grid-timeout-worker-#22%cluster%][] Possible
> failure suppressed accordingly to a configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
> o.a.i.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]]]
> org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-0,
> igniteInstanceName=instance, finished=false, heartbeatTs=1601234567890]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1859)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1854)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:296)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:265)
> [ignite-core.jar]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> [ignite-core.jar]
> at java.lang.Thread.run(Thread.java:834) [?:?]
> {code}
> when the actual stack trace from the relevant thread is hidden somewhere deep
> below. And may even be suppressed. This is a usability nightmare.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13519) Add thin client support for Spring Data.
[ https://issues.apache.org/jira/browse/IGNITE-13519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228671#comment-17228671 ] Mikhail Petrov commented on IGNITE-13519: - [~alex_pl] Thanks a lot for the review. > Add thin client support for Spring Data. > > > Key: IGNITE-13519 > URL: https://issues.apache.org/jira/browse/IGNITE-13519 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It's needed to add thin client support for Spring Data. > To work with a thin client it proposed: > 1. Configure the bean of IgniteClient type > 2. Pass the bean name from step 1 to the Spring Data repository > configuration via the @RepositoryConfig annotation(igniteInstance = " name for accessing the Ignite cluster"). > At the moment, the repository configuration which uses node to access the > cluster is performed in the same way. > When using a node to access a cluster, you can configure TextQuery execution. > This functionality does not support the thin client - if repository is > configures to use TextQuery and thin client is used to access the cluster, > repository method for TextQuery will fail with an error in runtime. > All other operations implemented for the node are supported in the case of > using the thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13519) Add thin client support for Spring Data.
[ https://issues.apache.org/jira/browse/IGNITE-13519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-13519: Description: It's needed to add thin client support for Spring Data. To work with a thin client it proposed: 1. Configure the bean of IgniteClient type 2. Pass the bean name from step 1 to the Spring Data repository configuration via the @RepositoryConfig annotation(igniteInstance = " Add thin client support for Spring Data. > > > Key: IGNITE-13519 > URL: https://issues.apache.org/jira/browse/IGNITE-13519 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It's needed to add thin client support for Spring Data. > To work with a thin client it proposed: > 1. Configure the bean of IgniteClient type > 2. Pass the bean name from step 1 to the Spring Data repository > configuration via the @RepositoryConfig annotation(igniteInstance = " name for accessing the Ignite cluster"). > At the moment, the repository configuration which uses node to access the > cluster is performed in the same way. > When using a node to access a cluster, you can configure TextQuery execution. > This functionality does not support the thin client - if repository is > configures to use TextQuery and thin client is used to access the cluster, > repository method for TextQuery will fail with an error in runtime. > All other operations implemented for the node are supported in the case of > using the thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13688) Ignite Docs: Port Checkpointing Mapping from readme.io
YuJue Li created IGNITE-13688: - Summary: Ignite Docs: Port Checkpointing Mapping from readme.io Key: IGNITE-13688 URL: https://issues.apache.org/jira/browse/IGNITE-13688 Project: Ignite Issue Type: Task Components: documentation Affects Versions: 2.9 Reporter: YuJue Li Fix For: 2.9.1 The content in the link below is missing from the new version of the document: [https://apacheignite.readme.io/docs/continuous-mapping] [https://apacheignite.readme.io/docs/checkpointing] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228656#comment-17228656 ] Alexand Polyakov commented on IGNITE-13687: --- Run TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll/5724563 > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228644#comment-17228644 ] Alexand Polyakov commented on IGNITE-13687: --- Create pull request https://github.com/apache/ignite/pull/8441 > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
[ https://issues.apache.org/jira/browse/IGNITE-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228643#comment-17228643 ] Alexand Polyakov commented on IGNITE-13687: --- Create branch https://github.com/gridgain/apache-ignite/tree/ignite-13687 > Improvement of human-readable format of WAL records > (StandaloneWalRecordsIterator) > -- > > Key: IGNITE-13687 > URL: https://issues.apache.org/jira/browse/IGNITE-13687 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.9 >Reporter: Alexand Polyakov >Assignee: Alexand Polyakov >Priority: Major > > StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader > utility for printing WAL records in human-readable format. We should add > abilities for this iterator and options for IgniteWalIteratorFactory: > to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) > to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13683) Added MVCC validation to ValidateIndexesClosure
[ https://issues.apache.org/jira/browse/IGNITE-13683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228577#comment-17228577 ] Sergey Chugunov commented on IGNITE-13683: -- [~sdanilov], I think we can optimize the code a little bit. If my understanding is correct we added iteration over all caches from cache group only because we can request MVCC session for a separate cache, not a cache group. But if caches in the group don't have MVCC enabled, we can use good old iteration over all keys in partition, without separating them by cache. It should be more effective. > Added MVCC validation to ValidateIndexesClosure > --- > > Key: IGNITE-13683 > URL: https://issues.apache.org/jira/browse/IGNITE-13683 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.9 >Reporter: Anton Kalashnikov >Assignee: Semyon Danilov >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > MVCC indexes validation should be added to ValidateIndexesClosure -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[ https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228558#comment-17228558 ] Anton Vinogradov commented on IGNITE-13643: --- Merged to master branch. Thanks for your contribution. > Disable socket linger dy default in Tcp Discovery Spi > - > > Key: IGNITE-13643 > URL: https://issues.apache.org/jira/browse/IGNITE-13643 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: IEP-56, iep-45 > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to > close socket. This violates node detection failure. Despite we set > failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in > average. > This time gap was unearther by a discovery integration test on ducktape [1]. > Failure detection timeout is set to 1000ms. > Typical results before the fix for 1 node: > "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):": > "[6140]", "Nodes failed": 1} > Typical results after the fix for 1 node: > "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):": > "[1034]", "Nodes failed": 1} > There is note that 'graceful' socket closing was made to workaround bag in > OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues > like [3] and [4]. > There are various fixes in modern versions of various JDK, supporting TLS 1.3 > ([6]). OpenJDK11 works well as far as I know. > I believe, SSL in discovery is rare in usage. This slows down performance. > With the issues, one could just enable soLiger or update the JDK. There is no > reason to affect all users by default. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py > [2] https://bugs.openjdk.java.net/browse/JDK-8219658 > [3] https://issues.apache.org/jira/browse/IGNITE-12818 > [4] https://issues.apache.org/jira/browse/IGNITE-11288 > [5] https://bugs.openjdk.java.net/browse/JDK-8245468 > [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13643) Disable socket linger dy default in Tcp Discovery Spi
[ https://issues.apache.org/jira/browse/IGNITE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13643: -- Labels: IEP-56 iep-45 (was: ) > Disable socket linger dy default in Tcp Discovery Spi > - > > Key: IGNITE-13643 > URL: https://issues.apache.org/jira/browse/IGNITE-13643 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: IEP-56, iep-45 > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > Current IgniteUtils.closeQuiet(@Nullable Socket sock) can take about 5sec to > close socket. This violates node detection failure. Despite we set > failureDetectionTiemout == 1000, node failure is detected within 6.5 secs in > average. > This time gap was unearther by a discovery integration test on ducktape [1]. > Failure detection timeout is set to 1000ms. > Typical results before the fix for 1 node: > "Detection of node(s) failure (ms)": 6140, "All detection delays (ms):": > "[6140]", "Nodes failed": 1} > Typical results after the fix for 1 node: > "Detection of node(s) failure (ms)": 1034, "All detection delays (ms):": > "[1034]", "Nodes failed": 1} > There is note that 'graceful' socket closing was made to workaround bag in > OpenJDK12 [2]. But as I see it has been fixed. Also, there were SSL issues > like [3] and [4]. > There are various fixes in modern versions of various JDK, supporting TLS 1.3 > ([6]). OpenJDK11 works well as far as I know. > I believe, SSL in discovery is rare in usage. This slows down performance. > With the issues, one could just enable soLiger or update the JDK. There is no > reason to affect all users by default. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py > [2] https://bugs.openjdk.java.net/browse/JDK-8219658 > [3] https://issues.apache.org/jira/browse/IGNITE-12818 > [4] https://issues.apache.org/jira/browse/IGNITE-11288 > [5] https://bugs.openjdk.java.net/browse/JDK-8245468 > [6] https://www.oracle.com/java/technologies/javase/8u261-relnotes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13624) Extend tracing of communication socket write with number of sent bytes.
[ https://issues.apache.org/jira/browse/IGNITE-13624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228549#comment-17228549 ] Amelchev Nikita commented on IGNITE-13624: -- [~PetrovMikhail], Looks good to me. > Extend tracing of communication socket write with number of sent bytes. > --- > > Key: IGNITE-13624 > URL: https://issues.apache.org/jira/browse/IGNITE-13624 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to extend tracing of communication socket write with number of > sent bytes for each message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13687) Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator)
Alexand Polyakov created IGNITE-13687: - Summary: Improvement of human-readable format of WAL records (StandaloneWalRecordsIterator) Key: IGNITE-13687 URL: https://issues.apache.org/jira/browse/IGNITE-13687 Project: Ignite Issue Type: Improvement Components: persistence Affects Versions: 2.9 Reporter: Alexand Polyakov Assignee: Alexand Polyakov StandaloneWalRecordsIterator is used for PageHistoryDiagnoster and wal-reader utility for printing WAL records in human-readable format. We should add abilities for this iterator and options for IgniteWalIteratorFactory: to print DataRecord entries keys in hex/base64 (see UnwrapDataEntry) to print all records existing in WAL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13653) Don't print warning if unordered map used for bulk update operation on atomic cache
[ https://issues.apache.org/jira/browse/IGNITE-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-13653: - Labels: 2.9.1-rc (was: ) > Don't print warning if unordered map used for bulk update operation on atomic > cache > --- > > Key: IGNITE-13653 > URL: https://issues.apache.org/jira/browse/IGNITE-13653 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: 2.9.1-rc > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Since IGNITE-12451 is resolved there no more deadlock possible for atomic > caches and it's safe to use HashMap and other unordered maps as argument of > putAll/removeAll/invokeAll operations on atomic caches. Warning, introduced > by IGNITE-6804, is not required anymore. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13686) Compression test become failed after IGNITE-13658.
[
https://issues.apache.org/jira/browse/IGNITE-13686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-13686:
-
Affects Version/s: 2.9
> Compression test become failed after IGNITE-13658.
> --
>
> Key: IGNITE-13686
> URL: https://issues.apache.org/jira/browse/IGNITE-13686
> Project: Ignite
> Issue Type: Improvement
> Components: data structures
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [1] was merged persistent check become fail to pass
> {noformat}
> if (diskPageCompression != DiskPageCompression.DISABLED) {
> if (!cctx.dataRegion().config().isPersistenceEnabled())
> throw new IgniteCheckedException("Disk page compression makes
> sense only with enabled persistence.");
> {noformat} I suggest to remove failed smoke tests :
> IgnitePersistentStoreDataStructuresTest
> [1] https://issues.apache.org/jira/browse/IGNITE-13658
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13686) Compression test become failed after IGNITE-13658.
[
https://issues.apache.org/jira/browse/IGNITE-13686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228540#comment-17228540
]
Ilya Kasnacheev edited comment on IGNITE-13686 at 11/9/20, 12:01 PM:
-
No, I do not think we should remove this test. It is a good test. It caught a
bug.
There is a bug in Disk Page Compression feature: when
IGNITE_DEFAULT_DISK_PAGE_COMPRESSION is specified, it is applied to
non-persistent regions and fails their usage.
The bug needs to be fixed. Possibly in this ticket. The only thing we could do
right now is mark these tests as ignored, but it's hard to do since they're in
a suite that only fails with specific parameters.
was (Author: ilyak):
No, I do not think we should remove this test. It is a good test. It caught a
bug.
There is a bug in Disk Page Compression feature: when
IGNITE_DEFAULT_DISK_PAGE_COMPRESSION is specified, it is applied to
non-persistent regions and fail their usage.
The bug needs to be fixed. Possibly in this ticket. The only thing we could do
right now is mark these tests as ignored, but it's hard to do since they're in
a suite that only fails with specific parameters.
> Compression test become failed after IGNITE-13658.
> --
>
> Key: IGNITE-13686
> URL: https://issues.apache.org/jira/browse/IGNITE-13686
> Project: Ignite
> Issue Type: Improvement
> Components: data structures
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [1] was merged persistent check become fail to pass
> {noformat}
> if (diskPageCompression != DiskPageCompression.DISABLED) {
> if (!cctx.dataRegion().config().isPersistenceEnabled())
> throw new IgniteCheckedException("Disk page compression makes
> sense only with enabled persistence.");
> {noformat} I suggest to remove failed smoke tests :
> IgnitePersistentStoreDataStructuresTest
> [1] https://issues.apache.org/jira/browse/IGNITE-13658
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13686) Compression test become failed after IGNITE-13658.
[
https://issues.apache.org/jira/browse/IGNITE-13686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228540#comment-17228540
]
Ilya Kasnacheev commented on IGNITE-13686:
--
No, I do not think we should remove this test. It is a good test. It caught a
bug.
There is a bug in Disk Page Compression feature: when
IGNITE_DEFAULT_DISK_PAGE_COMPRESSION is specified, it is applied to
non-persistent regions and fail their usage.
The bug needs to be fixed. Possibly in this ticket. The only thing we could do
right now is mark these tests as ignored, but it's hard to do since they're in
a suite that only fails with specific parameters.
> Compression test become failed after IGNITE-13658.
> --
>
> Key: IGNITE-13686
> URL: https://issues.apache.org/jira/browse/IGNITE-13686
> Project: Ignite
> Issue Type: Improvement
> Components: data structures
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [1] was merged persistent check become fail to pass
> {noformat}
> if (diskPageCompression != DiskPageCompression.DISABLED) {
> if (!cctx.dataRegion().config().isPersistenceEnabled())
> throw new IgniteCheckedException("Disk page compression makes
> sense only with enabled persistence.");
> {noformat} I suggest to remove failed smoke tests :
> IgnitePersistentStoreDataStructuresTest
> [1] https://issues.apache.org/jira/browse/IGNITE-13658
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13684) Rewrite PageIo resolver from static to explicit dependency
[
https://issues.apache.org/jira/browse/IGNITE-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228534#comment-17228534
]
Ignite TC Bot commented on IGNITE-13684:
{panel:title=Branch: [pull/8435/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8435/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=5719166buildTypeId=IgniteTests24Java8_RunAll]
> Rewrite PageIo resolver from static to explicit dependency
> --
>
> Key: IGNITE-13684
> URL: https://issues.apache.org/jira/browse/IGNITE-13684
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Kalashnikov
>Assignee: Ivan Bessonov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, ignite has a static pageIo resolver which not allow substituting
> the different implementation if needed. So it is needed to rewrite the
> current implementation in order of this target.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13682) Add generic to maintenance mode feature
[ https://issues.apache.org/jira/browse/IGNITE-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13682: - Fix Version/s: 2.10 > Add generic to maintenance mode feature > --- > > Key: IGNITE-13682 > URL: https://issues.apache.org/jira/browse/IGNITE-13682 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > MaintenanceAction has no generic right now which lead to parametirezed problem -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13662) Describe soLinger setting in TCP Discovery and SSL issues.
[ https://issues.apache.org/jira/browse/IGNITE-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228526#comment-17228526 ] Anton Vinogradov commented on IGNITE-13662: --- Pull Request #8430 merged to master. [~vladsz83], Thanks for your contribution. [~dmagda], do we need some additional steps here? > Describe soLinger setting in TCP Discovery and SSL issues. > -- > > Key: IGNITE-13662 > URL: https://issues.apache.org/jira/browse/IGNITE-13662 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9, 2.8.1 >Reporter: Vladimir Steshin >Assignee: Denis A. Magda >Priority: Minor > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > Discribe soLinger setting in TCP Discovery and SSL issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-4818) .NET DayOfWeek does not work as a LINQ parameter
[
https://issues.apache.org/jira/browse/IGNITE-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4818:
---
Labels: .NET LINQ newbie (was: .NET LINQ)
> .NET DayOfWeek does not work as a LINQ parameter
>
>
> Key: IGNITE-4818
> URL: https://issues.apache.org/jira/browse/IGNITE-4818
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET, LINQ, newbie
>
> IGNITE-4359 added support for {{DateTime.DayOfWeek}}, but it can't be used in
> Where clause:
> {code}
> var res = persons.AsCacheQueryable().Where(x => x.Value.BirthDay.DayOfWeek ==
> DayOfWeek.Monday);
> {code}
> This fails because {{DayOfWeek.Monday}} is written as a serializable enum.
> Workaround is to cast to an int:
> {code}
> var res = persons.AsCacheQueryable().Where(x =>
> (int)x.Value.BirthDay.DayOfWeek == (int)DayOfWeek.Monday);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13682) Add generic to maintenance mode feature
[ https://issues.apache.org/jira/browse/IGNITE-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228459#comment-17228459 ] Anton Kalashnikov commented on IGNITE-13682: [~sergey-chugunov] Can you please take a review and merge this? > Add generic to maintenance mode feature > --- > > Key: IGNITE-13682 > URL: https://issues.apache.org/jira/browse/IGNITE-13682 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > MaintenanceAction has no generic right now which lead to parametirezed problem -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13682) Add generic to maintenance mode feature
[ https://issues.apache.org/jira/browse/IGNITE-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kalashnikov updated IGNITE-13682: --- Summary: Add generic to maintenance mode feature (was: Added generic to maintenance mode feature) > Add generic to maintenance mode feature > --- > > Key: IGNITE-13682 > URL: https://issues.apache.org/jira/browse/IGNITE-13682 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > MaintenanceAction has no generic right now which lead to parametirezed problem -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13682) Added generic to maintenance mode feature
[
https://issues.apache.org/jira/browse/IGNITE-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228457#comment-17228457
]
Ignite TC Bot commented on IGNITE-13682:
{panel:title=Branch: [pull/8434/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8434/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=5719043buildTypeId=IgniteTests24Java8_RunAll]
> Added generic to maintenance mode feature
> -
>
> Key: IGNITE-13682
> URL: https://issues.apache.org/jira/browse/IGNITE-13682
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> MaintenanceAction has no generic right now which lead to parametirezed problem
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13635) .NET: OOM due to integer overflow in PlatformOutputStream
[
https://issues.apache.org/jira/browse/IGNITE-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13635:
Priority: Minor (was: Major)
> .NET: OOM due to integer overflow in PlatformOutputStream
> -
>
> Key: IGNITE-13635
> URL: https://issues.apache.org/jira/browse/IGNITE-13635
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.4, 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.10, 2.9.1
>
>
> {{PlatformOutputStreamImpl.unsafeEnsure}} causes integer overflow, then
> passes a negative value to {{PlatformCallbackGateway.memoryReallocate}} from
> there it is passed to {{Marshal.ReAllocHGlobal}}, which throws an
> OutOfMemoryException.
> Reproducer:
> {code}
> var val = new byte[100_000_000];
> var ignite = Ignition.Start();
> var cache = ignite.CreateCache("c");
> for (int i = 0; i < 30; i++) // ~3GB of cache data
> cache[i] = val;
> cache.Query(new ScanQuery()).GetAll();
> {code}
> We should handle this condition gracefully: detect stream size limit and
> throw an exception explaining how to fix the problem (use smaller pageSize
> for queries, for example).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13684) Rewrite PageIo resolver from static to explicit dependency
[ https://issues.apache.org/jira/browse/IGNITE-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17228442#comment-17228442 ] Ivan Bessonov commented on IGNITE-13684: I think I should add an explanation. This ticket contains refactoring elements necessary for defragmentation. Given that defragmentation patch is huge, we decided to split it. This way it's going to be easier to review and to track history. Changes are: * static constant for cache group meta page; * PageStore allocation tracker replaced with a more generic LongConsumer do decouple it from metrics framework; * PageReadWriteManager added to basically allow having same cache group in different data regions; * several methods and fields exposed as internally public/protected API; * several inner classes refactored so that they become static classes; * PageIOResolver interface created and used to make data structure more flexible; * InsertLast interface for B+Tree added that will optimize comparisons on inserts. Unused for now; All this code doesn't affect existing behavior. > Rewrite PageIo resolver from static to explicit dependency > -- > > Key: IGNITE-13684 > URL: https://issues.apache.org/jira/browse/IGNITE-13684 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Right now, ignite has a static pageIo resolver which not allow substituting > the different implementation if needed. So it is needed to rewrite the > current implementation in order of this target. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups
[ https://issues.apache.org/jira/browse/IGNITE-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaroslav Molochkov updated IGNITE-13572: Fix Version/s: 2.9.1 > Duplicates in select query during partition eviction for caches with 0 backups > -- > > Key: IGNITE-13572 > URL: https://issues.apache.org/jira/browse/IGNITE-13572 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ivan Daschinskiy >Assignee: Konstantin Sirotkin >Priority: Major > Fix For: 2.9.1 > > Attachments: SqlPartitionEvictionTest.java > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Scenario: > # Start 2 nodes with indexed atomic partitioned cache with 0 backups. > # Load sufficient amout of data (or emulate slow removal from idx) > # Start another node. > # Perform SELECT * FROM . > Query result contains duplicates, result size is significantly bigger than > expected cache size. > Reproducer is attached. > Reproduced on 2.8.1, ongoing 2.9 and master -- This message was sent by Atlassian Jira (v8.3.4#803005)
