[jira] [Commented] (IGNITE-18832) Option to assign specific name to thin client and capturing the name in sys.client_connections
[
https://issues.apache.org/jira/browse/IGNITE-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723461#comment-17723461
]
Ignite TC Bot commented on IGNITE-18832:
{panel:title=Branch: [pull/10719/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10719/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 3 (lazy=true){color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7177795]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
SqlSystemViewsSelfTest.testClientConnectionViews - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
SystemViewSelfTest.testClientConnectionAttributes - PASSED{color}
{color:#8b}Queries 3{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7177794]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
SqlSystemViewsSelfTest.testClientConnectionViews - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
SystemViewSelfTest.testClientConnectionAttributes - PASSED{color}
{color:#8b}Cache 13{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7177720]]
* {color:#013220}IgniteCacheTestSuite13:
SystemViewSelfTest.testClientConnectionAttributes - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7177822&buildTypeId=IgniteTests24Java8_RunAll]
> Option to assign specific name to thin client and capturing the name in
> sys.client_connections
> --
>
> Key: IGNITE-18832
> URL: https://issues.apache.org/jira/browse/IGNITE-18832
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.12, 2.13, 2.11.1, 2.14
>Reporter: Gangaiah
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: IEP-35
>
>
> System view client_connections doesn't have name column to capture client
> name, it should have the column to track the thin client connections.. It's
> difficult to pin point the client where remote address same for multiple
> clients in production scenarios.
> https://lists.apache.org/thread/joy6vjopq2zovkj768hnhfvmd44vhs4b
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19495) SQL onheap cache stores row on per-cache basis, but access these rows on per-index basis
[
https://issues.apache.org/jira/browse/IGNITE-19495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723848#comment-17723848
]
Ignite TC Bot commented on IGNITE-19495:
{panel:title=Branch: [pull/10722/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10722/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7178894&buildTypeId=IgniteTests24Java8_RunAll]
> SQL onheap cache stores row on per-cache basis, but access these rows on
> per-index basis
>
>
> Key: IGNITE-19495
> URL: https://issues.apache.org/jira/browse/IGNITE-19495
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: ise
>
> If there are two indexes on the same cache and sqlOnHeapCache property is
> enabled there can be node failures such as:
> {noformat}
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-917681634, pageIds=[844420635164678],
> cacheId=-917681634, cacheName=..., indexName=_key_PK, msg=Runtime failure on
> row: Row@71aeb1b9[ ... ][ ]]
> ...
> Caused by: org.apache.ignite.IgniteException: Failed to store new index row.
> ...
> Caused by: java.lang.UnsupportedOperationException: 13 cannot be used for
> inline type 19
> {noformat}
> Root cause: {{IndexRowCache}} is created per cache group (see
> {{IndexRowCacheRegistry#onCacheRegistered}}), but stores {{IndexRowImpl}}
> binded to particular index (see {{InlineIndexTree#createIndexRow}}). In case,
> when another index requires the same data row, it gets row from the onheap
> cache with the wrong index row handler.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19359) .NET: Thin client: 'Affinity keys are not supported exception' on put
[
https://issues.apache.org/jira/browse/IGNITE-19359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723872#comment-17723872
]
Ignite TC Bot commented on IGNITE-19359:
{panel:title=Branch: [pull/10727/head] Base: [master] : Possible Blockers
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Snapshots{color} [[tests 0 Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7237801]]
{color:#d04437}[Check Code Style Ducktests]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=7237743]]
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7237721]]
{color:#d04437}Disk Page Compressions 1{color} [[tests 1 Exit Code , Failure on
metric |https://ci.ignite.apache.org/viewLog.html?buildId=7237819]]
* IgnitePdsCompressionTestSuite:
WalRecoveryWithPageCompressionAndTdeTest.testRecoveryLargeNoCheckpoint - Test
has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}PDS 2{color} [[tests 0 TIMEOUT , Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7237775]]
{color:#d04437}Disk Page Compressions 2{color} [[tests 0 TIMEOUT , Exit Code ,
Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=7237820]]
{color:#d04437}Basic 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7237714]]
* IgniteBasicTestSuite2: IgniteDiagnosticMessagesTest.testSeveralLongRunningTxs
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7237794]]
* IgniteBinaryCacheQueryTestSuite3: BasicSqlTypesIndexTest.testSqlTimeTypeIndex
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Continuous Query 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7237750]]
* IgniteCacheQuerySelfTestSuite5:
GridCacheContinuousQueryConcurrentTest.testRestartReplicated - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7237790]]
* IgniteBinaryCacheQueryTestSuite:
BasicIndexTest.testDynamicIdxOnStaticCacheWithIdxWithoutPersistence - Test has
low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10727/head] Base: [master] : New Tests
(80)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
40|https://ci.ignite.apache.org/viewLog.html?buildId=7237788]]
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(6,2)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_SkipKey_LogsWarningAndBypassesPartitionAwareness
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithUserTypeAffinityKey_RequestIsRoutedToPrimaryNode(1,0)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithUserTypeAffinityKey_RequestIsRoutedToPrimaryNode(2,0)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(2,0)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(3,0)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(4,1)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(5,1)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKey_RequestIsRoutedToPrimaryNode(4,1)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKey_RequestIsRoutedToPrimaryNode(5,1)
- PASSED{color}
* {color:#013220}DotNetCore:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKey_RequestIsRoutedToPrimaryNode(6,2)
- PASSED{color}
... and 29 new tests
{color:#8b}Platform .NET (Windows){color} [[tests
40|https://ci.ignite.apache.org/viewLog.html?buildId=7237789]]
* {color:#013220}exe:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(4,1)
- PASSED{color}
* {color:#013220}exe:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(5,1)
- PASSED{color}
* {color:#013220}exe:
PartitionAwarenessTest.CachePut_UserDefinedTypeWithAffinityKeyBinarizable_RequestIsRoutedToPrimaryNode(6,2)
- PASSED{color}
* {color:#
[jira] [Commented] (IGNITE-19389) Make lock acquiring timeout message more certain.
[
https://issues.apache.org/jira/browse/IGNITE-19389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724352#comment-17724352
]
Ignite TC Bot commented on IGNITE-19389:
{panel:title=Branch: [pull/10726/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10726/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7181278&buildTypeId=IgniteTests24Java8_RunAll]
> Make lock acquiring timeout message more certain.
> -
>
> Key: IGNITE-19389
> URL: https://issues.apache.org/jira/browse/IGNITE-19389
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.12
>Reporter: Vladimir Steshin
>Priority: Minor
>
> Suggestion: make text of lock acquiring timeout message more certain if there
> is no attempt to acquire like: "_Didn't try to take lock for transaction ...
> because tx has already timeouted_" instead of common "_Failed to acquire lock
> within provided timeout for transaction_"
> We've met a case when user sees lock acquiring timeout in transaction but is
> confused in researching the cause. He expected and tried to find concurrent
> transaction, deadlocks, hanging locks, etc. Actually, lock attempt hasn't
> even launched. The timeout has already happened. Stacktrace indicates the
> problem, but it is not the best solution to a user.
> The stacktrace:
> {code:java}
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction
> [timeout=3,
> tx=GridDhtTxLocal[xid=f5c28b36881--10c7-fe43--0016,
> xidVersion=GridCacheVersion [topVer=281542211, order=1685300194399,
> nodeOrder=22, dataCenterId=0], nearXidVersion=GridCacheVersion
> [topVer=281542211, order=1685300194398, nodeOrder=552, dataCenterId=0],
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=ACTIVE,
> invalidate=false, rollbackOnly=false,
> nodeId=0693b588-3677-45d8-b1a2-06aa03fa4ed8, timeout=3,
> startTime=1673243469168, duration=30255]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.timeoutException(IgniteTxAdapter.java:785)
> ~[ignite-core-2.12.0-p6.jar:2.12.0-p6]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.obtainLockAsync(GridDhtTxLocalAdapter.java:710)
> ~[ignite-core-2.12.0-p6.jar:2.12.0-p6]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.lockAllAsync(GridDhtTxLocalAdapter.java:660)
> ~[ignite-core-2.12.0-p6.jar:2.12.0-p6]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.lockAllAsync(GridDhtTransactionalCacheAdapter.java:1239)
> [ignite-core-2.12.0-p6.jar:2.12.0-p6]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest0(GridDhtTransactionalCacheAdapter.java:824)
> [ignite-core-2.12.0-p6.jar:2.12.0-p6]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest(GridDhtTransactionalCacheAdapter.java:802)
> [ignite-core-2.12.0-p6.jar:2.12.0-p6]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19445) NPE during transaction recovery
[
https://issues.apache.org/jira/browse/IGNITE-19445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724690#comment-17724690
]
Ignite TC Bot commented on IGNITE-19445:
{panel:title=Branch: [pull/10728/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10728/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7181392&buildTypeId=IgniteTests24Java8_RunAll]
> NPE during transaction recovery
> ---
>
> Key: IGNITE-19445
> URL: https://issues.apache.org/jira/browse/IGNITE-19445
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikita Amelchev
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Attachments: reproducer-19445.patch
>
>
> The transaction can be enlisted during recovery(two different threads). The
> {{GridIntList}} used in the {{IgniteTxStateImpl}} is not thread safe - it
> produces NPE:
> {noformat}
> [2023-05-10T12:23:32,438][ERROR][sys-#129%dht.TxRecoveryStoreEnabledTest1%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: null]]
> org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7929)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:659)
> [classes/:?]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> [classes/:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_352]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_352]
> at java.lang.Thread.run(Thread.java:750) [?:1.8.0_352]
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxStateImpl.storeWriteThrough(IgniteTxStateImpl.java:342)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.storeWriteThrough(IgniteTxAdapter.java:517)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxRecoveryInitRunnable.run(IgniteTxManager.java:3341)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7487)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:649)
> ~[classes/:?]
> ... 4 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19164) Improve message about requested partitions during snapshot restore
[
https://issues.apache.org/jira/browse/IGNITE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725847#comment-17725847
]
Ignite TC Bot commented on IGNITE-19164:
{panel:title=Branch: [pull/10638/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10638/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7188479&buildTypeId=IgniteTests24Java8_RunAll]
> Improve message about requested partitions during snapshot restore
> --
>
> Key: IGNITE-19164
> URL: https://issues.apache.org/jira/browse/IGNITE-19164
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: iep-43, ise
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently, during snapshot restore message is logged before requesting
> partitions from remote nodes:
> {quote}
> [2023-03-24T18:06:59,910][INFO
> ]\[disco-notifier-worker-#792%node%|#792%node%][SnapshotRestoreProcess]
> Trying to request partitions from remote nodes
> [reqId=ff682204-9554-4fbb-804c-38a79c0b286a, snapshot=snapshot_name,
> map={*{color:#FF}76e22ef5-3c76-4987-bebd-9a6222a0{color}*={*{color:#FF}-903566235{color}*=[0,2,4,6,11,12,18,98,100,170,190,194,1015],
>
> *{color:#FF}1544803905{color}*=[1,11,17,18,22,25,27,35,37,42,45,51,62,64,67,68,73,76,1017]}}]
> {quote}
> It is necessary to make this output "human readable":
> # Print messages per node instead of one message for all nodes.
> # Print consistent id and address of remote node, suppling partitions.
> # Print cache / group name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19410) Node failure in case multiple nodes join and leave a cluster simultaneously with security is enabled.
[
https://issues.apache.org/jira/browse/IGNITE-19410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725933#comment-17725933
]
Ignite TC Bot commented on IGNITE-19410:
{panel:title=Branch: [pull/10701/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10701/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Security{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7188616]]
* {color:#013220}SecurityTestSuite:
NodeSecurityContextPropagationTest.testProcessCustomDiscoveryMessageFromLeftNode
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7186616&buildTypeId=IgniteTests24Java8_RunAll]
> Node failure in case multiple nodes join and leave a cluster simultaneously
> with security is enabled.
> --
>
> Key: IGNITE-19410
> URL: https://issues.apache.org/jira/browse/IGNITE-19410
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Petrov
>Priority: Major
> Labels: ise
> Attachments: NodeSecurityContextTest.java
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The case when nodes with security enabled join and leave the cluster
> simultaneously can cause the joining nodes to fail with the following
> exception:
> {code:java}
> [2023-05-03T14:54:31,208][ERROR][disco-notifier-worker-#332%ignite.NodeSecurityContextTest2%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
> err=java.lang.IllegalStateException: Failed to find security context for
> subject with given ID : 4725544a-f144-4486-a705-46b2ac200011]]
> java.lang.IllegalStateException: Failed to find security context for subject
> with given ID : 4725544a-f144-4486-a705-46b2ac200011
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.withContext(IgniteSecurityProcessor.java:164)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$3$SecurityAwareNotificationTask.run(GridDiscoveryManager.java:949)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2822)
> ~[classes/:?]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2860)
> [classes/:?]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
> [classes/:?]
> at java.lang.Thread.run(Thread.java:750) [?:1.8.0_351] {code}
> Reproducer is attached.
> Simplified steps that leads to the failure:
> 1. The client node sends an arbitrary discovery message which produces an
> acknowledgement message when it processed by the all cluster nodes .
> 2. The client node gracefully leaves the cluster.
> 3. The new node joins the cluster and receives a topology snapshot that does
> not include the left client node.
> 4. The new node receives an acknowledgment for the message from the step 1
> and fails during its processing because message originator node is not listed
> in the current discovery cache or discovery cache history (see
> IgniteSecurityProcessor#withContext(java.util.UUID)) . This is because
> currently the GridDiscoveryManager#historicalNode method only aware of the
> topology history that occurs after a node has joined the cluster. The
> complete cluster topology history that exists at the time a new node joined
> the cluster is stored in GridDiscoveryManager#topHist and is not taken into
> account by the GridDiscoveryManager#historicalNode method.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19585) Calcite engine. Performance statistics
[
https://issues.apache.org/jira/browse/IGNITE-19585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727437#comment-17727437
]
Ignite TC Bot commented on IGNITE-19585:
{panel:title=Branch: [pull/10751/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10751/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7194843]]
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testPerformanceStatistics - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7194924&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Performance statistics
> --
>
> Key: IGNITE-19585
> URL: https://issues.apache.org/jira/browse/IGNITE-19585
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, only root query event are written to performance statistics for
> Calcite-based SQL engine.
> We should fix it and implement physical/logical reads events for Calcite
> engine as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19564) Snapshot restoration metric is not always assigned when an error occurs.
[
https://issues.apache.org/jira/browse/IGNITE-19564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727880#comment-17727880
]
Ignite TC Bot commented on IGNITE-19564:
{panel:title=Branch: [pull/10735/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10735/head] Base: [master] : New Tests
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Disk Page Compressions 1{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7196128]]
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteClusterSnapshotMetricsTest.testUnableToRestoreSnapshotError[encryption=false,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteClusterSnapshotMetricsTest.testUnableToRestoreSnapshotError[encryption=false,
onlyPrimay=false] - PASSED{color}
{color:#8b}Snapshots With Indexes{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7196086]]
* {color:#013220}IgniteSnapshotWithIndexingTestSuite:
IgniteClusterSnapshotMetricsTest.testUnableToRestoreSnapshotError[encryption=false,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgniteSnapshotWithIndexingTestSuite:
IgniteClusterSnapshotMetricsTest.testUnableToRestoreSnapshotError[encryption=false,
onlyPrimay=false] - PASSED{color}
* {color:#013220}IgniteSnapshotWithIndexingTestSuite:
IgniteClusterSnapshotMetricsTest.testUnableToRestoreSnapshotError[encryption=true,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgniteSnapshotWithIndexingTestSuite:
IgniteClusterSnapshotMetricsTest.testUnableToRestoreSnapshotError[encryption=true,
onlyPrimay=false] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7196106&buildTypeId=IgniteTests24Java8_RunAll]
> Snapshot restoration metric is not always assigned when an error occurs.
>
>
> Key: IGNITE-19564
> URL: https://issues.apache.org/jira/browse/IGNITE-19564
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Priority: Minor
> Attachments: IgniteClusterSnapshotMetricsTest.java
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The metric of last snapshot process might not be assigned in case of failed
> snapshot restoration. Happens when an error occurs on the process
> preparation, before launching. The cause is that we assign the holder of last
> process context after some checks which can raise an exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19586) Calcite engine. Events
[
https://issues.apache.org/jira/browse/IGNITE-19586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728238#comment-17728238
]
Ignite TC Bot commented on IGNITE-19586:
{panel:title=Branch: [pull/10756/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10756/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7197097]]
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testSqlEvents - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7197178&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Events
> --
>
> Key: IGNITE-19586
> URL: https://issues.apache.org/jira/browse/IGNITE-19586
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, for Calcite-based SQL enginge only EVT_CACHE_QUERY_EXECUTED event
> is fired, but H2-based SQL engine fires also EVT_CACHE_QUERY_OBJECT_READ and
> EVT_SQL_QUERY_EXECUTION. Calcite engine should fire these events as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19607) Flaky test fix - testStreamingIntoInMemoryDoesntAffectSnapshot()
[
https://issues.apache.org/jira/browse/IGNITE-19607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728299#comment-17728299
]
Ignite TC Bot commented on IGNITE-19607:
{panel:title=Branch: [pull/10755/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10755/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7197064&buildTypeId=IgniteTests24Java8_RunAll]
> Flaky test fix - testStreamingIntoInMemoryDoesntAffectSnapshot()
>
>
> Key: IGNITE-19607
> URL: https://issues.apache.org/jira/browse/IGNITE-19607
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> +
> {code:java}
> awaitPartitionMapExchange();
> {code}
> after
> {code:java}
> destroyCache()
> {code}
> to avoid
> {code:java}
> IgniteCheckedException: Unable to restore cache group - directory is not
> empty.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19590) Calcite engine. Hide sensitive information in diagnostic tools
[
https://issues.apache.org/jira/browse/IGNITE-19590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728788#comment-17728788
]
Ignite TC Bot commented on IGNITE-19590:
{panel:title=Branch: [pull/10760/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10760/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7199360]]
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testSensitiveInformationHiding - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7199441&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Hide sensitive information in diagnostic tools
> --
>
> Key: IGNITE-19590
> URL: https://issues.apache.org/jira/browse/IGNITE-19590
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We need to hide sensitive information in queries exposed to diagnostic tools
> for the Calcite-based SQL engine, if flag IGNITE_TO_STRING_INCLUDE_SENSITIVE
> is not set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19620) Provide ability to configure metric exporter filter from Spring XML
[
https://issues.apache.org/jira/browse/IGNITE-19620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728854#comment-17728854
]
Ignite TC Bot commented on IGNITE-19620:
{panel:title=Branch: [pull/10757/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10757/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Spring{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7199653]]
* {color:#013220}IgniteSpringTestSuite: RegexpMetricFilterTest.testFilter -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7199669&buildTypeId=IgniteTests24Java8_RunAll]
> Provide ability to configure metric exporter filter from Spring XML
> ---
>
> Key: IGNITE-19620
> URL: https://issues.apache.org/jira/browse/IGNITE-19620
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Minor
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Provide ability to configure metric exporter filter from Spring XML
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19628) Add IndexQuery to performance statistics
[
https://issues.apache.org/jira/browse/IGNITE-19628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729212#comment-17729212
]
Ignite TC Bot commented on IGNITE-19628:
{panel:title=Branch: [pull/10758/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10758/head] Base: [master] : New Tests
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Continuous Query 4{color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7199925]]
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
PerformanceStatisticsQueryTest.testIndexQuery[pageSize=100, clientType=SERVER]
- PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
PerformanceStatisticsQueryTest.testIndexQuery[pageSize=100, clientType=CLIENT]
- PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
PerformanceStatisticsQueryTest.testIndexQuery[pageSize=100,
clientType=THIN_CLIENT] - PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
PerformanceStatisticsQueryTest.testIndexQuery[pageSize=10, clientType=SERVER] -
PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
PerformanceStatisticsQueryTest.testIndexQuery[pageSize=10, clientType=CLIENT] -
PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
PerformanceStatisticsQueryTest.testIndexQuery[pageSize=10,
clientType=THIN_CLIENT] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7199555&buildTypeId=IgniteTests24Java8_RunAll]
> Add IndexQuery to performance statistics
>
>
> Key: IGNITE-19628
> URL: https://issues.apache.org/jira/browse/IGNITE-19628
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Add IndexQuery to performance statistics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-15629) Cluster Management API
[
https://issues.apache.org/jira/browse/IGNITE-15629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730126#comment-17730126
]
Ignite TC Bot commented on IGNITE-15629:
{panel:title=Branch: [pull/10675/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10675/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7205057]]
* {color:#013220}IgniteBasicTestSuite: CommandUtilsSelfTest.testCommandName -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite: CommandUtilsSelfTest.testAsOptional -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite: CommandUtilsSelfTest.testFromCommandName
- PASSED{color}
* {color:#013220}IgniteBasicTestSuite: CommandUtilsSelfTest.testToFormatted -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7205027&buildTypeId=IgniteTests24Java8_RunAll]
> Cluster Management API
> --
>
> Key: IGNITE-15629
> URL: https://issues.apache.org/jira/browse/IGNITE-15629
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-81, important, ise
> Time Spent: 44h 40m
> Remaining Estimate: 0h
>
> Ignite must provide cluster management internal API in that way the other
> available user APIs like REST, CLI or JMX won't require the source code
> changes.
> The following features must be available out of the box:
> - man pages and documentation autogeneration
> - registering new commands from plugins
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19650) Broken serialization of communication messages due to incorrect GridCacheQueryRequest class marshalling.
[
https://issues.apache.org/jira/browse/IGNITE-19650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730229#comment-17730229
]
Ignite TC Bot commented on IGNITE-19650:
{panel:title=Branch: [pull/10768/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10768/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 3 (lazy=true){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7206206]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
H2CommunicationMessageSerializationTest.testMessageSerializationAndDeserializationConsistency
- PASSED{color}
{color:#8b}Queries 3{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7206205]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
H2CommunicationMessageSerializationTest.testMessageSerializationAndDeserializationConsistency
- PASSED{color}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7206152]]
* {color:#013220}IgniteCalciteTestSuite:
CalciteCommunicationMessageSerializationTest.testMessageSerializationAndDeserializationConsistency
- PASSED{color}
{color:#8b}Cache 10{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7206128]]
* {color:#013220}IgniteCacheTestSuite10:
IgniteIoCommunicationMessageSerializationTest.testMessageSerializationAndDeserializationConsistency
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7206233&buildTypeId=IgniteTests24Java8_RunAll]
> Broken serialization of communication messages due to incorrect
> GridCacheQueryRequest class marshalling.
>
>
> Key: IGNITE-19650
> URL: https://issues.apache.org/jira/browse/IGNITE-19650
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.14, 2.15
>Reporter: Mikhail Petrov
>Priority: Blocker
> Labels: ise
> Time Spent: 1h
> Remaining Estimate: 0h
>
> GridCacheQueryRequest class writeTo/readForm methods does not increment
> message writer/reader state sequentially. Currently idxQryDescBytes field
> corresponds message reader/writer state with number 27. But state number 26
> is skipped. This can lead to the following situation:
> We write on sender node all fields preceding idxQryDescBytes to byte buffer.
> But no space remains for idxQryDescBytes. So we save the state with number
> 26 and returns.
> When enough free space become available - we do not find any field that
> corresponds 26 state and complete serialization without idxQryDescBytes field
> being recorded.
> Receiver node tries to read all fields including idxQryDescBytes which was
> not recorded in the byte buffer by the sender node. As a result receiver node
> can read a part of the next message stored in the byte buffer while trying to
> read skipped idxQryDescBytes field. This results in corrupted serialization
> of communication messages.
> User can face the following exceptions in this case. The concrete exception
> depends on the message that come after GridCacheQueryRequest.
> {code:java}
> 2023-05-31 14:49:02.249
> [ERROR][grid-nio-worker-tcp-comm-15-#134%TcpCommunicationSpi%][org.apache.ignite.internal.util.nio.GridDirectParser]
> Failed to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1,
> ordered=false, timeout=0, skipOnTimeout=false, msg=null],
> buf=java.nio.DirectByteBuffer[pos=2 lim=16384 cap=132678],
> reader=DirectMessageReader [state=DirectMessageState [pos=0, stack=[StateItem
> [stream=DirectByteBufferStreamImplV2 [baseOff=139878897874032, arrOff=-1,
> tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true,
> msg=GridDhtAtomicNearResponse [partId=0, futId=0, primaryId=null, errs=null,
> flags=], mapIt=null, it=null, arrPos=-1, keyDone=false, readSize=-1,
> readItems=0, prim=0, primShift=0, uuidState=0, uuidMost=0, uuidLeast=0,
> uuidLocId=0], state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=139878897874032, arrOff=-1, tmpArrOff=0, valReadBytes=0,
> tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1,
> keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0,
> uuidMost=0, uuidLeast=0, uuidLocId=0], state=0], StateItem
> [stream=DirectByteBufferStreamImplV2 [baseOff=16, arrOff=-1, tmpArrOff=0,
> valReadBytes=0, tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null,
> it=null, arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0,
> primShift=0, uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0], state=0],
> StateItem [stream=DirectByteBufferStreamImplV2 [baseOff=16, arrOff=
[jira] [Commented] (IGNITE-19588) Calcite engine. Long running queries warning
[
https://issues.apache.org/jira/browse/IGNITE-19588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732078#comment-17732078
]
Ignite TC Bot commented on IGNITE-19588:
{panel:title=Branch: [pull/10769/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10769/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
5|https://ci2.ignite.apache.org/viewLog.html?buildId=7208272]]
* {color:#013220}IgniteCalciteTestSuite:
TimeCalculationExecutionTest.testTime[Execution strategy = FIFO] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TimeCalculationExecutionTest.testTime[Execution strategy = LIFO] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TimeCalculationExecutionTest.testTime[Execution strategy = RANDOM] -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testBigResultSet - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testLongRunningQueries - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7208353&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Long running queries warning
>
>
> Key: IGNITE-19588
> URL: https://issues.apache.org/jira/browse/IGNITE-19588
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For H2-based SQL engine we have warnings in the log files, if query executed
> for too long time (see
> {{IgniteConfiguration#setLongQueryWarningTimeout(long)}})
> We need the same functionality for the Calcite-based SQL engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19164) Improve message about requested partitions during snapshot restore
[
https://issues.apache.org/jira/browse/IGNITE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732443#comment-17732443
]
Ignite TC Bot commented on IGNITE-19164:
{panel:title=Branch: [pull/10638/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10638/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7215017&buildTypeId=IgniteTests24Java8_RunAll]
> Improve message about requested partitions during snapshot restore
> --
>
> Key: IGNITE-19164
> URL: https://issues.apache.org/jira/browse/IGNITE-19164
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: iep-43, ise
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Currently, during snapshot restore message is logged before requesting
> partitions from remote nodes:
> {quote}[2023-03-24T18:06:59,910][INFO
> ][disco-notifier-worker-#792%node%|#792%node%][SnapshotRestoreProcess] Trying
> to request partitions from remote nodes
> [reqId=ff682204-9554-4fbb-804c-38a79c0b286a, snapshot=snapshot_name,
> map={{*}{color:#ff}76e22ef5-3c76-4987-bebd-9a6222a0{color}{*}={{*}{color:#ff}-903566235{color}{*}=[0,2,4,6,11,12,18,98,100,170,190,194,1015],
>
> {*}{color:#ff}1544803905{color}{*}=[1,11,17,18,22,25,27,35,37,42,45,51,62,64,67,68,73,76,1017]}}]
> {quote}
> It is necessary to make this output "human readable":
> # Print messages per node instead of one message for all nodes.
> # Print consistent id and address of remote node, suppling partitions.
> # Print cache / group name.
> _
> A new output example:
> {code:java}
> Trying to request partitions from remote node
> [reqId=9c78f302-9e75-43c6-bf58-3ec4d3c3bb59, snapshot=testSnapshot,
> nodeId=c53157d9-5429-4f09-a352-227f2d10,
> consistentId=snapshot.IgniteSnapshotRestoreFromRemoteTest0,
> grpParts={{grpId=-903566235,
> grpName=shared}=[1,2,3,6,7,8,9,11,12,18,19,20,27,29,34,38,39,40,41,42,43,45,46,48,53,56,58,59,62,64,65,66,67,69,70,72,73,76,77,78,79,80,89,90,94,95,97,99,100,102,108,110,112,113,114,115,117,120,121,122,123,126,131,134,135,136,137,138,139,140,145,149,156,157,158,160,162,163,167,170,173,175,178,181,182,183,187,189,195,196,198,199,201,202,203,204,206,207,208,209,211,212,217,220,221,223,224,225,226,228,230,232,234,235,240,241,242,243,244,246,251,252,255,256,258,259,260,261,264,269,271,272,273,275,276,277,280,281,282,283,284,287,288,295,297,298,300,301,302,303,306,308,311,312,315,317,322,324,325,327,330,331,342,344,346,348,349,352,353,354,355,358,360,363,364,365,367,368,369,370,371,373,374,376,379,380,381,382,383,384,386,387,388,389,395,396,397,403,404,405,408,409,411,412,413,417,419,421,423,424,426,430,431,432,433,435,436,437,438,439,440,442,445,447,452,453,454,455,461,462,463,464,466,467,468,470,471,472,473,474,475,476,477,480,481,482,485,487,488,490,491,493,494,497,499,501,502,506,507,516,517,519,526,527,532,534,536,537,539,543,544,546,547,550,551,553,557,559,562,566,569,570,572,573,574,576,580,582,584,586,587,588,590,591,593,595,596,598,601,602,606,611,612,613,619,623,625,628,630,632,634,638,640,643,644,646,650,651,653,654,660,661,662,663,664,665,666,667,668,670,675,678,679,680,683,684,685,686,689,690,691,693,694,701,702,703,706,710,713,714,715,717,719,723,728,729,730,733,737,738,739,743,744,751,753,754,755,758,759,760,762,763,764,765,767,770,773,775,776,778,779,780,781,782,783,785,787,788,789,792,794,797,798,799,801,803,804,806,809,811,812,813,814,818,819,821,822,824,826,827,828,829,831,832,834,835,838,839,840,842,843,845,847,848,849,850,851,852,854,855,856,857,859,860,861,862,864,866,868,869,870,871,872,873,874,876,880,882,885,888,890,891,892,893,896,899,900,901,904,906,909,911,916,917,918,919,924,925,927,928,929,930,932,935,936,945,946,949,950,953,955,957,958,963,965,969,974,975,977,982,983,984,987,988,990,991,992,993,994,999,1001,1004,1009,1010,1011,1013,1018,1019,1020,1021,1022,1023],
> {grpId=1544803905,
> grpName=default}=[1,2,8,9,11,12,18,20,27,29,34,38,40,41,42,43,45,46,48,53,56,58,59,62,64,65,69,70,72,73,76,78,79,80,89,90,95,99,100,108,110,112,114,115,120,122,123,126,131,134,137,138,139,149,156,158,160,163,173,178,181,182,189,196,198,199,201,202,203,204,207,208,211,212,217,220,221,224,225,226,230,242,246,258,259,260,264,269,271,272,275,277,281,282,283,284,287,288,295,297,298,301,302,303,306,308,311,312,315,317,322,330,331,342,344,346,348,352,353,355,358,363,364,365,367,368,369,370,371,373,379,380,381,382,383,384,386,387,388,389,395,396,397,403,404,408,409,413,417,419,421,423,424,426,430,431,433,435,
[jira] [Commented] (IGNITE-19715) Thin client operations can take a long time if PA is enabled and some cluster nodes are not network reachable.
[
https://issues.apache.org/jira/browse/IGNITE-19715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732532#comment-17732532
]
Ignite TC Bot commented on IGNITE-19715:
{panel:title=Branch: [pull/10770/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10770/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7216123&buildTypeId=IgniteTests24Java8_RunAll]
> Thin client operations can take a long time if PA is enabled and some cluster
> nodes are not network reachable.
> --
>
> Key: IGNITE-19715
> URL: https://issues.apache.org/jira/browse/IGNITE-19715
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Thin client operations can take a long time if PA is enabled and some cluster
> nodes are not reachable over network.
> Consider the following scenario:
> 1. The thin client have already sucessfully established connection to all
> configured node addresses.
> 2. A particular cluster node becomes unreachable over network. It can be
> reproduced with iptables -A INPUT -p tcp --dport for Linux.
> 3. The thin client periodically sends put request which is mapped by PA to
> the unreachable node.
> 4. Firstly all attempts to perform put will lead to `ClientException:
> Timeout was reached before computation completed.` exception. But eventually
> the connection to the unreachable node will be closed by OS (see
> tcp_keepalive_time for Linux).
> This will lead to reestablishing connection to the unreachable node during
> handling of the next put (see ReliableChannel.java:1012)
> We currently do not set a timeout for the open connection operation (see
> GridNioClientConnectionMultiplexer#open, here we use Integer.MAX_VALUE for
> Socket#connect(java.net.SocketAddress, int))
> As a result socket#connect operation (and hence put operation) hangs for a
> significant amount of time (it depends on OS parameters, usually it is couple
> of minutes). This is confusing for users because a single put may take much
> longer than the configured ClientConfiguration#setTimeout property.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19652) Ignite is not working on JDK 21
[
https://issues.apache.org/jira/browse/IGNITE-19652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732866#comment-17732866
]
Ignite TC Bot commented on IGNITE-19652:
{panel:title=Branch: [pull/10764/head] Base: [master] : Possible Blockers
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Snapshots{color} [[tests 0 Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7294598]]
{color:#d04437}[Check Code Style Ducktests]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=7294540]]
{color:#d04437}Disk Page Compressions 1{color} [[tests 0 Exit Code , Failure on
metric |https://ci.ignite.apache.org/viewLog.html?buildId=7294616]]
{color:#d04437}Disk Page Compressions 2{color} [[tests 0 TIMEOUT , Exit Code ,
Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=7294617]]
{color:#d04437}Platform .NET (Windows){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7294586]]
* exe: CachePartitionedAtomicNearEnabledTest.TestCacheConfigurationExpiryPolicy
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Queries 2 (lazy=true){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7294590]]
* IgniteBinaryCacheQueryLazyTestSuite2:
IgniteCacheQueryNodeRestartDistributedJoinSelfTest.testRestartsBroadcast - Test
has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10764/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=7294619&buildTypeId=IgniteTests24Java8_RunAll]
> Ignite is not working on JDK 21
> ---
>
> Key: IGNITE-19652
> URL: https://issues.apache.org/jira/browse/IGNITE-19652
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Mateusz Gajewski
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> ByteBuffer constructor in JDK 21 has different arguments:
> https://github.com/openjdk/jdk/commit/a56598f5a534cc9223367e7faa8433ea38661db9
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-16619) IndexQuery should support limit
[
https://issues.apache.org/jira/browse/IGNITE-16619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732922#comment-17732922
]
Ignite TC Bot commented on IGNITE-16619:
{panel:title=Branch: [pull/10767/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10767/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Index Query API{color} [[tests
5|https://ci2.ignite.apache.org/viewLog.html?buildId=7214343]]
* {color:#013220}IndexQueryTestSuite:
ThinClientIndexQueryTest.testIndexQueryLimitOnOlderProtocolVersion[keepBinary=false]
- PASSED{color}
* {color:#013220}IndexQueryTestSuite:
ThinClientIndexQueryTest.testIndexQueryLimitOnOlderProtocolVersion[keepBinary=true]
- PASSED{color}
* {color:#013220}IndexQueryTestSuite:
IndexQueryLimitTest.testRangeQueriesWithoutDuplicates - PASSED{color}
* {color:#013220}IndexQueryTestSuite:
IndexQueryLimitTest.testRangeQueriesWithDuplicates - PASSED{color}
* {color:#013220}IndexQueryTestSuite: IndexQueryLimitTest.testSetLimit -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7214407&buildTypeId=IgniteTests24Java8_RunAll]
> IndexQuery should support limit
> ---
>
> Key: IGNITE-16619
> URL: https://issues.apache.org/jira/browse/IGNITE-16619
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maksim Timonin
>Assignee: Yuri Naryshkin
>Priority: Major
> Labels: IEP-71
> Fix For: 2.16
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> IndexQuery should provide functionality to limit result rows (by analogue
> with TextQuery).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19742) Disable Spring expressions in the cache create command.
[
https://issues.apache.org/jira/browse/IGNITE-19742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733430#comment-17733430
]
Ignite TC Bot commented on IGNITE-19742:
{panel:title=Branch: [pull/10776/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10776/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7217605&buildTypeId=IgniteTests24Java8_RunAll]
> Disable Spring expressions in the cache create command.
> ---
>
> Key: IGNITE-19742
> URL: https://issues.apache.org/jira/browse/IGNITE-19742
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Disable Spring expressions in the cache create command to prevent injections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19767) Update Ignite dependency: Jetty
[
https://issues.apache.org/jira/browse/IGNITE-19767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733932#comment-17733932
]
Ignite TC Bot commented on IGNITE-19767:
{panel:title=Branch: [pull/10784/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10784/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7220180&buildTypeId=IgniteTests24Java8_RunAll]
> Update Ignite dependency: Jetty
> ---
>
> Key: IGNITE-19767
> URL: https://issues.apache.org/jira/browse/IGNITE-19767
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Nikolaev
>Assignee: Aleksandr Nikolaev
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Update Jetty dependency 9.4.43.v20210629 to 9.4.51.v20230217
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19584) Calcite engine. SQL metrics
[
https://issues.apache.org/jira/browse/IGNITE-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734045#comment-17734045
]
Ignite TC Bot commented on IGNITE-19584:
{panel:title=Branch: [pull/10777/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10777/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
3|https://ci2.ignite.apache.org/viewLog.html?buildId=7217288]]
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testBatchParserMetrics - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testParserMetrics - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
SqlDiagnosticIntegrationTest.testUserQueriesMetrics - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7217369&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. SQL metrics
> ---
>
> Key: IGNITE-19584
> URL: https://issues.apache.org/jira/browse/IGNITE-19584
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, we have two groups (registries) of metrics for SQL:
> * "sql.parser.cache" - shows count of hits/misses during SQL queries parsing
> * "sql.queries.user" - shows count of succesfully executed and failed metrics
> Parser metrics are not affected by Calcite-based engine and execution metrics
> count all metrics as succesfully executed.
> We need to implement parser metrics and fix execution metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19766) Add topology snapshot to the services system view
[
https://issues.apache.org/jira/browse/IGNITE-19766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736074#comment-17736074
]
Ignite TC Bot commented on IGNITE-19766:
{panel:title=Branch: [pull/10783/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10783/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7225031&buildTypeId=IgniteTests24Java8_RunAll]
> Add topology snapshot to the services system view
> -
>
> Key: IGNITE-19766
> URL: https://issues.apache.org/jira/browse/IGNITE-19766
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Add topology snapshot info to the services system view
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19753) Move task and command class to the same packages
[
https://issues.apache.org/jira/browse/IGNITE-19753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736131#comment-17736131
]
Ignite TC Bot commented on IGNITE-19753:
{panel:title=Branch: [pull/10797/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10797/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7226736&buildTypeId=IgniteTests24Java8_RunAll]
> Move task and command class to the same packages
>
>
> Key: IGNITE-19753
> URL: https://issues.apache.org/jira/browse/IGNITE-19753
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Major
> Labels: IEP-81
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Right now command of Management API in
> {{org.apache.ignite.internal.management}} package and tasks that implements
> command logic in {{org.apache.ignite.internal.visor}} package.
> Visor not existing anymore in Ignite so it's seems logical to move tasks and
> their dependencies to commands.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19676) JMX Commands invoker
[
https://issues.apache.org/jira/browse/IGNITE-19676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736468#comment-17736468
]
Ignite TC Bot commented on IGNITE-19676:
{panel:title=Branch: [pull/10775/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility 2{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7227952]]
* IgniteControlUtilityTestSuite2:
GridCommandHandlerDefragmentationTest.testDefragmentationStatus[cmdHnd=jmx] -
History for base branch is absent.
{panel}
{panel:title=Branch: [pull/10775/head] Base: [master] : New Tests
(1599)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Control Utility 2{color} [[tests
609|https://ci2.ignite.apache.org/viewLog.html?buildId=7227952]]
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testList[cmdHnd=cli] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testPropertyDisabledSqlFunctions[cmdHnd=cli] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testPropertyWalRebalanceThreshold[cmdHnd=cli]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testPropertyCheckpointDeviation[cmdHnd=cli] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testPropertyDefaultQueryTimeout[cmdHnd=jmx] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testPropertySnapshotTransferRate[cmdHnd=jmx] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testGet[cmdHnd=cli] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerPropertiesTest.testHelp[cmdHnd=cli] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerDefragmentationTest.testDefragmentationCancelInProgress[cmdHnd=jmx]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerDefragmentationTest.testDefragmentationSchedule[cmdHnd=jmx] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerDefragmentationTest.testDefragmentationCancel[cmdHnd=cli] -
PASSED{color}
... and 598 new tests
{color:#8b}Control Utility 1{color} [[tests
770|https://ci2.ignite.apache.org/viewLog.html?buildId=7226933]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testDataRecordMissed[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.atomicCachesAreSkippedDuringTheCheck[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testRollbackDoesNotMatterIfMissed[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testSuccessfullCheckEmptySnapshots[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testSingleNodeMissed[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testDataAndTransactionMissed[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testSingleTransactionMissed[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerCheckIncrementalSnapshotTest.testSuccessfullCheckSnapshots[cmdHnd=cli,nodesCnt=3,primNodesCnt=1,backupsCnt=2]
- PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelUnknownService[cmdHnd=jmx] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelUnknownComputeTask[cmdHnd=jmx] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testCancelComputeTask[cmdHnd=jmx] - PASSED{color}
... and 759 new tests
{color:#8b}Control Utility (Zookeeper){color} [[tests
220|https://ci2.ignite.apache.org/viewLog.html?buildId=7226934]]
* {color:#013220}ZookeeperIgniteControlUtilityTestSuite:
GridCommandHandlerTest.testBaselineAutoAdjustmentAutoRemoveNode[cmdHnd=jmx] -
PASSED{color}
* {color:#013220}ZookeeperIgniteControlUtilityTestSuite:
GridCommandHandlerTest.testCacheIdleVerifyCrcWithCorruptedPartition[cmdHnd=jmx]
- PASSED{color}
* {color:#013220}ZookeeperIgniteContro
[jira] [Commented] (IGNITE-19725) Calcite-2. Add local flag support
[
https://issues.apache.org/jira/browse/IGNITE-19725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736839#comment-17736839
]
Ignite TC Bot commented on IGNITE-19725:
{panel:title=Branch: [pull/10788/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10788/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7224836]]
* {color:#013220}IgniteCalciteTestSuite:
LocalQueryIntegrationTest.testReplicated - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: LocalQueryIntegrationTest.testJoin -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
LocalQueryIntegrationTest.testJoinReplicated - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: LocalQueryIntegrationTest.testSingle -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7224917&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite-2. Add local flag support
> -
>
> Key: IGNITE-19725
> URL: https://issues.apache.org/jira/browse/IGNITE-19725
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite2-required, ise
> Fix For: 2.16
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19845) IgniteTxLocalAdapter.sndTransformedVals field removal
[
https://issues.apache.org/jira/browse/IGNITE-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737564#comment-17737564
]
Ignite TC Bot commented on IGNITE-19845:
{panel:title=Branch: [pull/10805/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10805/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7232098&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxLocalAdapter.sndTransformedVals field removal
> -
>
> Key: IGNITE-19845
> URL: https://issues.apache.org/jira/browse/IGNITE-19845
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19158) Improve message about received partition file during snapshot restore
[
https://issues.apache.org/jira/browse/IGNITE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737631#comment-17737631
]
Ignite TC Bot commented on IGNITE-19158:
{panel:title=Branch: [pull/10762/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10762/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7199897&buildTypeId=IgniteTests24Java8_RunAll]
> Improve message about received partition file during snapshot restore
> -
>
> Key: IGNITE-19158
> URL: https://issues.apache.org/jira/browse/IGNITE-19158
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: iep-43, ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, GridIoManager prints only name of a file and node id:
> {quote}
> [2023-03-24T18:07:00,747][INFO ]pub-#871%node1%[GridIoManager] File has been
> received [name={color:red}part-233.bin{color}, transferred=53248, time=0.0
> sec, {color:red}rmtId=76e22ef5-3c76-4987-bebd-9a6222a0{color}]
> {quote}
> This meager information does not allow to determine in a simple way which
> file is received and from which node.
> For example, such message would be more informative:
> {quote}
> [2023-03-29T17:09:42,230][INFO ][pub-#869%node0%][GridIoManager] File has
> been received
> [{color:red}path=/ignite/db/node0/_tmp_snp_restore_cache-default/part-647.bin{color},
> transferred=45056, time=0.0 sec, rmtId=de43d2e8-a1ab-4d7c-9cea-72615371,
> {color:red}rmdAddr=/127.0.0.1:51773{color}]
> {quote}
> _Other ways might be investigated_ in order to improve logging of receiving
> partition files during snapshot restore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19753) Move task and command class to the same packages
[
https://issues.apache.org/jira/browse/IGNITE-19753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737721#comment-17737721
]
Ignite TC Bot commented on IGNITE-19753:
{panel:title=Branch: [pull/10797/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility 2{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7233987]]
* IgniteControlUtilityTestSuite2:
GridCommandHandlerDefragmentationTest.testDefragmentationStatus[cmdHnd=cli] -
History for base branch is absent.
{panel}
{panel:title=Branch: [pull/10797/head] Base: [master] : New Tests
(372)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Control Utility 2{color} [[tests
276|https://ci2.ignite.apache.org/viewLog.html?buildId=7233987]]
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testAtomicAndTxValueAndVersion[cmdHnd=cli,
strategy=LWW, explicitGrp=false, callByGrp=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testRepairNonExistentCache[cmdHnd=cli,
strategy=LWW, explicitGrp=false, callByGrp=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testCacheFilter[cmdHnd=jmx, strategy=LWW,
explicitGrp=true, callByGrp=true] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testAtomicAndTxVersionOnly[cmdHnd=jmx,
strategy=LWW, explicitGrp=true, callByGrp=true] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testAtomicAndTxValueAndVersion[cmdHnd=cli,
strategy=LWW, explicitGrp=true, callByGrp=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testRepairNonExistentCache[cmdHnd=cli,
strategy=LWW, explicitGrp=true, callByGrp=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testCacheFilter[cmdHnd=cli, strategy=LWW,
explicitGrp=false, callByGrp=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testAtomicAndTxVersionOnly[cmdHnd=cli,
strategy=LWW, explicitGrp=false, callByGrp=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testAtomicAndTxValueAndVersion[cmdHnd=jmx,
strategy=LWW, explicitGrp=true, callByGrp=true] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testRepairNonExistentCache[cmdHnd=jmx,
strategy=LWW, explicitGrp=true, callByGrp=true] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite2:
GridCommandHandlerConsistencyTest.testCacheFilter[cmdHnd=jmx, strategy=PRIMARY,
explicitGrp=false, callByGrp=false] - PASSED{color}
... and 265 new tests
{color:#8b}Control Utility 1{color} [[tests
96|https://ci2.ignite.apache.org/viewLog.html?buildId=7233901]]
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testCachesRepair[cmdHnd=cli,
misses=false, nulls=false, strategy=LWW, parallel=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testGroupRepairBySingleCacheName[cmdHnd=cli,
misses=false, nulls=false, strategy=LWW, parallel=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testGroupRepairByCacheNames[cmdHnd=jmx,
misses=false, nulls=false, strategy=PRIMARY, parallel=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testGroupRepairByItsName[cmdHnd=jmx,
misses=false, nulls=false, strategy=PRIMARY, parallel=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testCachesRepair[cmdHnd=cli,
misses=false, nulls=false, strategy=RELATIVE_MAJORITY, parallel=false] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testGroupRepairBySingleCacheName[cmdHnd=cli,
misses=false, nulls=false, strategy=RELATIVE_MAJORITY, parallel=false] -
PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testGroupRepairByCacheNames[cmdHnd=cli,
misses=false, nulls=false, strategy=LWW, parallel=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
GridCommandHandlerConsistencyRepairCorrectnessTransactionalTest.testGroupRepairByItsName[cmdHnd=cli,
misses=false, nulls=false, strategy=LWW, parallel=false] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
Gr
[jira] [Commented] (IGNITE-19847) IgniteTxAdapter.TxShadow removal
[
https://issues.apache.org/jira/browse/IGNITE-19847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737807#comment-17737807
]
Ignite TC Bot commented on IGNITE-19847:
{panel:title=Branch: [pull/10807/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10807/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7232332&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxAdapter.TxShadow removal
>
>
> Key: IGNITE-19847
> URL: https://issues.apache.org/jira/browse/IGNITE-19847
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Seems, it never used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19846) IgniteTxAdapter initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738206#comment-17738206
]
Ignite TC Bot commented on IGNITE-19846:
{panel:title=Branch: [pull/10806/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10806/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7235073&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxAdapter initial cleanup
> ---
>
> Key: IGNITE-19846
> URL: https://issues.apache.org/jira/browse/IGNITE-19846
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Fields finalization
> Unused fields/methods removal
> Code simplification
> Methods relocation
> Code deduplication
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19818) Calcite engine. Query planning failed when cache size is too big
[
https://issues.apache.org/jira/browse/IGNITE-19818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738245#comment-17738245
]
Ignite TC Bot commented on IGNITE-19818:
{panel:title=Branch: [pull/10804/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10804/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7231903]]
* {color:#013220}IgniteCalciteTestSuite:
ServerStatisticsIntegrationTest.testSizeIntOverflow - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7231984&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Query planning failed when cache size is too big
>
>
> Key: IGNITE-19818
> URL: https://issues.apache.org/jira/browse/IGNITE-19818
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We use cache size as estimation for row count while planning, but use
> {{cache.size()}} method, that returns int value. But if cache size is more
> than {{Integer.MAX_VALUE}} we get an wrong size or even negative sometimes,
> which cause assertion errors during planning.
> We should fix it to {{cache.sizeLong()}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19753) Move task and command class to the same packages
[
https://issues.apache.org/jira/browse/IGNITE-19753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738398#comment-17738398
]
Ignite TC Bot commented on IGNITE-19753:
{panel:title=Branch: [pull/10797/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10797/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7236159&buildTypeId=IgniteTests24Java8_RunAll]
> Move task and command class to the same packages
>
>
> Key: IGNITE-19753
> URL: https://issues.apache.org/jira/browse/IGNITE-19753
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.16
>Reporter: Nikolay Izhikov
>Assignee: Valery Shorin
>Priority: Major
> Labels: IEP-81
> Fix For: 2.16
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Right now command of Management API in
> {{org.apache.ignite.internal.management}} package and tasks that implements
> command logic in {{org.apache.ignite.internal.visor}} package.
> Visor not existing anymore in Ignite so it's seems logical to move tasks and
> their dependencies to commands.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19872) IgniteTxLocalAdapter initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-19872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738483#comment-17738483
]
Ignite TC Bot commented on IGNITE-19872:
{panel:title=Branch: [pull/10812/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10812/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7235189&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxLocalAdapter initial cleanup
>
>
> Key: IGNITE-19872
> URL: https://issues.apache.org/jira/browse/IGNITE-19872
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19873) GridNearTxLocal initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738520#comment-17738520
]
Ignite TC Bot commented on IGNITE-19873:
{panel:title=Branch: [pull/10813/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10813/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7235303&buildTypeId=IgniteTests24Java8_RunAll]
> GridNearTxLocal initial cleanup
> ---
>
> Key: IGNITE-19873
> URL: https://issues.apache.org/jira/browse/IGNITE-19873
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19874) GridDhtTxLocal initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-19874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738529#comment-17738529
]
Ignite TC Bot commented on IGNITE-19874:
{panel:title=Branch: [pull/10814/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10814/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7235417&buildTypeId=IgniteTests24Java8_RunAll]
> GridDhtTxLocal initial cleanup
> --
>
> Key: IGNITE-19874
> URL: https://issues.apache.org/jira/browse/IGNITE-19874
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19875) GridDhtTxLocalAdapter initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-19875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738548#comment-17738548
]
Ignite TC Bot commented on IGNITE-19875:
{panel:title=Branch: [pull/10815/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10815/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7235531&buildTypeId=IgniteTests24Java8_RunAll]
> GridDhtTxLocalAdapter initial cleanup
> -
>
> Key: IGNITE-19875
> URL: https://issues.apache.org/jira/browse/IGNITE-19875
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19830) Add a description check if the command argument is enum type.
[
https://issues.apache.org/jira/browse/IGNITE-19830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738784#comment-17738784
]
Ignite TC Bot commented on IGNITE-19830:
{panel:title=Branch: [pull/10818/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10818/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Control Utility 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7237831]]
* {color:#013220}IgniteControlUtilityTestSuite:
CommandHandlerParsingTest.testEnumParameterDescription - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7237537&buildTypeId=IgniteTests24Java8_RunAll]
> Add a description check if the command argument is enum type.
> -
>
> Key: IGNITE-19830
> URL: https://issues.apache.org/jira/browse/IGNITE-19830
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Major
> Labels: IEP-81, ise
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Add a check for the presence of a enum description ({{@EnumDescription}}) if
> the parameter ({{@Argument}}) is an enum type.
> Example of an uncovered argument: {{ShutdownPolicyCommandArg#shutdownPolicy}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19878) Restrict possibility to create two caches with the same schema and index name
[
https://issues.apache.org/jira/browse/IGNITE-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739023#comment-17739023
]
Ignite TC Bot commented on IGNITE-19878:
{panel:title=Branch: [pull/10817/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10817/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7237759]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= true] - PASSED{color}
{color:#8b}Queries 1 (lazy=true){color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7237760]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= false] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7237791&buildTypeId=IgniteTests24Java8_RunAll]
> Restrict possibility to create two caches with the same schema and index name
> -
>
> Key: IGNITE-19878
> URL: https://issues.apache.org/jira/browse/IGNITE-19878
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.15
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It’s possible to create two different caches with the same schema and index
> name inside it from a client and after that get a failing of the server node
> during start-up with the error "Duplicate index name... " during start caches.
> scenario:
> start at least two server nodes
> start client node which creates two different caches during start-up (via
> setting cache configs to config of client node) with the same schema name and
> index name, it leads to crushing the cluster
> then try to start the cluster and get the error "Duplicate index name..."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19811) Continuous qieries backup acknowledge message sending fails for expired entries
[
https://issues.apache.org/jira/browse/IGNITE-19811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739469#comment-17739469
]
Ignite TC Bot commented on IGNITE-19811:
{panel:title=Branch: [pull/10816/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10816/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Continuous Query 4{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7236628]]
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
CacheContinuousQueryEntriesExpireTest.testBackupQOnEntriesExpire - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7236699&buildTypeId=IgniteTests24Java8_RunAll]
> Continuous qieries backup acknowledge message sending fails for expired
> entries
> ---
>
> Key: IGNITE-19811
> URL: https://issues.apache.org/jira/browse/IGNITE-19811
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Expire entry event has {{null}} in topology version field (see
> {{CacheContinuousQueryEntry}} constructor in the
> {{CacheContinuousQueryManager#onEntryExpired}} method). When Backup
> acknowledge is sending for such a message it silently (without warnings to
> log) fails with NPE on {{GridDiscoveryManager#cacheGroupAffinityNodes}} ->
> {{GridDiscoveryManager#resolveDiscoCache}} for {{null}} topology version (see
> {{CacheContinuousQueryHandler#sendBackupAcknowledge}}).
> This can lead to leaks in query entries buffer
> ({{CacheContinuousQueryEventBuffer#backupQ}}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19814) Calcite engine uses 0 as an inlineSize for index created by INT column
[
https://issues.apache.org/jira/browse/IGNITE-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739467#comment-17739467
]
Ignite TC Bot commented on IGNITE-19814:
{panel:title=Branch: [pull/10819/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10819/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7237570]]
* {color:#013220}IgniteCalciteTestSuite:
TableDdlIntegrationTest.testPrimaryKeyInlineSize - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7237651&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine uses 0 as an inlineSize for index created by INT column
> --
>
> Key: IGNITE-19814
> URL: https://issues.apache.org/jira/browse/IGNITE-19814
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Korotkov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite
> Attachments:
> 0001-IGNITE-19814-Add-calcite-test-for-integer-column-ind.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Using the Calcite query engine the following SQL statement
> {code:sql}
> CREATE TABLE TEST (id INT, name VARCHAR, PRIMARY KEY(id))
> {code}
> creates index for INT id column with the inlineSize = 0.
> If the _key_type_ is specified in the WITH clause index is created correctly
> with the inlineSize = 5:
> {code:sql}
> CREATE TABLE TEST (id INT, name VARCHAR, PRIMARY KEY(id))
> WITH "key_type=Integer"
> {code}
> For H2 engine in both cases inlineSize is 5.
> Reproducer is attached as a unit test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19878) Restrict possibility to create two caches with the same schema and index name
[
https://issues.apache.org/jira/browse/IGNITE-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739495#comment-17739495
]
Ignite TC Bot commented on IGNITE-19878:
{panel:title=Branch: [pull/10817/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10817/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7239045]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= true] - PASSED{color}
{color:#8b}Queries 1 (lazy=true){color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7239046]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= false] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7239077&buildTypeId=IgniteTests24Java8_RunAll]
> Restrict possibility to create two caches with the same schema and index name
> -
>
> Key: IGNITE-19878
> URL: https://issues.apache.org/jira/browse/IGNITE-19878
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.15
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> It’s possible to create two different caches with the same schema and index
> name inside it from a client and after that get a failing of the server node
> during start-up with the error "Duplicate index name... " during start caches.
> scenario:
> start at least two server nodes
> start client node which creates two different caches during start-up (via
> setting cache configs to config of client node) with the same schema name and
> index name, it leads to crushing the cluster
> then try to start the cluster and get the error "Duplicate index name..."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19878) Restrict possibility to create two caches with the same schema and index name
[
https://issues.apache.org/jira/browse/IGNITE-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739794#comment-17739794
]
Ignite TC Bot commented on IGNITE-19878:
{panel:title=Branch: [pull/10817/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10817/head] Base: [master] : New Tests
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1{color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7243335]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= true] - PASSED{color}
{color:#8b}Queries 1 (lazy=true){color} [[tests
6|https://ci2.ignite.apache.org/viewLog.html?buildId=7243336]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.teststartErroneousCacheConfigThroughDynamicCaches[persistent
= false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testErroneousCacheConfigFromClientNode[persistent
= true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
ErroneousQueryEntityConfigurationTest.testEqualIndexAreConfiguredOnServerAndJoinedNode[persistent
= false] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7243367&buildTypeId=IgniteTests24Java8_RunAll]
> Restrict possibility to create two caches with the same schema and index name
> -
>
> Key: IGNITE-19878
> URL: https://issues.apache.org/jira/browse/IGNITE-19878
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.15
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> It’s possible to create two different caches with the same schema and index
> name inside it from a client and after that get a failing of the server node
> during start-up with the error "Duplicate index name... " during start caches.
> scenario:
> start at least two server nodes
> start client node which creates two different caches during start-up (via
> setting cache configs to config of client node) with the same schema name and
> index name, it leads to crushing the cluster
> then try to start the cluster and get the error "Duplicate index name..."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19878) Restrict possibility to create two caches with the same schema and index name
[
https://issues.apache.org/jira/browse/IGNITE-19878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740146#comment-17740146
]
Ignite TC Bot commented on IGNITE-19878:
{panel:title=Branch: [pull/10817/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10817/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7243367&buildTypeId=IgniteTests24Java8_RunAll]
> Restrict possibility to create two caches with the same schema and index name
> -
>
> Key: IGNITE-19878
> URL: https://issues.apache.org/jira/browse/IGNITE-19878
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.15
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It’s possible to create two different caches with the same schema and index
> name inside it from a client and after that get a failing of the server node
> during start-up with the error "Duplicate index name... " during start caches.
> scenario:
> start at least two server nodes
> start client node which creates two different caches during start-up (via
> setting cache configs to config of client node) with the same schema name and
> index name, it leads to crushing the cluster
> then try to start the cluster and get the error "Duplicate index name..."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19912) Duplicated index creation using SQL leads to node start-up failure
[
https://issues.apache.org/jira/browse/IGNITE-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740545#comment-17740545
]
Ignite TC Bot commented on IGNITE-19912:
{panel:title=Branch: [pull/10822/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10822/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 1 (lazy=true){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7245335]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite:
DuplicateIndexCreationTest.testIndexCreation - PASSED{color}
{color:#8b}Queries 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7245334]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
DuplicateIndexCreationTest.testIndexCreation - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7245366&buildTypeId=IgniteTests24Java8_RunAll]
> Duplicated index creation using SQL leads to node start-up failure
> --
>
> Key: IGNITE-19912
> URL: https://issues.apache.org/jira/browse/IGNITE-19912
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Attachments: DuplicateIndexCreationTest.java
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In case an index for the field is specified using QuerySqlFields(index=true)
> annotation, it's possible to create multiple additional indices for the same
> field using CREATE INDEX IF NOT EXISTS statement without explicit index name
> specification. As a result, all indices that were created via SQL have the
> same name, which leads to node failure on the next restart due to Index with
> name 'person_name_asc_idx' already exists. exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19915) Remove obsolete IgniteCacheSnapshotManager
[
https://issues.apache.org/jira/browse/IGNITE-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740549#comment-17740549
]
Ignite TC Bot commented on IGNITE-19915:
{panel:title=Branch: [pull/10824/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 TIMEOUT , Exit Code
, TC_SERVICE_MESSAGE
|https://ci2.ignite.apache.org/viewLog.html?buildId=7246626]]
{panel}
{panel:title=Branch: [pull/10824/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7246200&buildTypeId=IgniteTests24Java8_RunAll]
> Remove obsolete IgniteCacheSnapshotManager
> --
>
> Key: IGNITE-19915
> URL: https://issues.apache.org/jira/browse/IGNITE-19915
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-80, iep-43
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> IgniteSnapshotManager implements snapshotting features.
> IgniteCacheSnapshotManager is obsolete and can be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19915) Remove obsolete IgniteCacheSnapshotManager
[
https://issues.apache.org/jira/browse/IGNITE-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740778#comment-17740778
]
Ignite TC Bot commented on IGNITE-19915:
{panel:title=Branch: [pull/10824/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10824/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7246200&buildTypeId=IgniteTests24Java8_RunAll]
> Remove obsolete IgniteCacheSnapshotManager
> --
>
> Key: IGNITE-19915
> URL: https://issues.apache.org/jira/browse/IGNITE-19915
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-80, iep-43
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> IgniteSnapshotManager implements snapshotting features.
> IgniteCacheSnapshotManager is obsolete and can be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19748) Calcite engine. Support queries timeout
[
https://issues.apache.org/jira/browse/IGNITE-19748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740946#comment-17740946
]
Ignite TC Bot commented on IGNITE-19748:
{panel:title=Branch: [pull/10827/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10827/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7246715]]
* {color:#013220}IgniteCalciteTestSuite:
TimeoutIntegrationTest.testRemoteTimeoutSetByFieldsQuery - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TimeoutIntegrationTest.testLocalTimeoutSetByDistributedProperty - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TimeoutIntegrationTest.testLocalTimeoutSetByFieldsQuery - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
TimeoutIntegrationTest.testRemoteTimeoutSetByDistributedProperty - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7246796&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Support queries timeout
> ---
>
> Key: IGNITE-19748
> URL: https://issues.apache.org/jira/browse/IGNITE-19748
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We can set timeout for SQL queries:
> * Using {{SqlFieldsQuery.timeout}} property (for certain query)
> * Using "sql.defaultQueryTimeout" distributed property (default for all
> queries)
> But Calcite-based SQL query engine ignore these timeouts. Only possible
> timeout supported by the new engine is planning timeout. We should support
> execution timeouts too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19918) idle_verify compactFooter info
[
https://issues.apache.org/jira/browse/IGNITE-19918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741093#comment-17741093
]
Ignite TC Bot commented on IGNITE-19918:
{panel:title=Branch: [pull/10829/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10829/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7247888&buildTypeId=IgniteTests24Java8_RunAll]
> idle_verify compactFooter info
> --
>
> Key: IGNITE-19918
> URL: https://issues.apache.org/jira/browse/IGNITE-19918
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Ignite has issues with default value of compactFooter parameter on nodes and
> thin client.
> Default has been changed lately IGNITE-16038 which break compatibility of pre
> 2.14 and >= 2.14 thin clients.
> For debug and operations purposes it will be convenient to have information
> about entry compactFooter values in PDS.
> Such information must be included in idle_verify report.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19977) Defragmentation can't use 1 thread.
[
https://issues.apache.org/jira/browse/IGNITE-19977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743036#comment-17743036
]
Ignite TC Bot commented on IGNITE-19977:
{panel:title=Branch: [pull/10842/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10842/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7255446]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testSuccessfulDefragmentationOneThread -
PASSED{color}
{color:#8b}PDS 8{color} [[tests
3|https://ci2.ignite.apache.org/viewLog.html?buildId=7255444]]
* {color:#013220}IgnitePdsTestSuite8:
IgnitePdsDefragmentationTest.testSuccessfulDefragmentationOneThread -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite8:
IgnitePdsDefragmentationRandomLruEvictionTest.testSuccessfulDefragmentationOneThread
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite8:
IgnitePdsDefragmentationEncryptionTest.testSuccessfulDefragmentationOneThread -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7255485&buildTypeId=IgniteTests24Java8_RunAll]
> Defragmentation can't use 1 thread.
> ---
>
> Key: IGNITE-19977
> URL: https://issues.apache.org/jira/browse/IGNITE-19977
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.12
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code:java}
> /**
> * Sets maximum number of partitions which can be defragmented at the
> same time.
> *
> * @param defragmentationThreadPoolSize Maximum number of partitions
> which can be defragmented at the same time.
> * Default is {@link
> DataStorageConfiguration#DFLT_DEFRAGMENTATION_THREAD_POOL_SIZE}.
> * @return {@code this} for chaining.
> */
> public DataStorageConfiguration setDefragmentationThreadPoolSize(int
> defragmentationThreadPoolSize) {
> A.ensure(defragmentationThreadPoolSize > 1, "Defragmentation thread
> pool size must be greater or equal to 1.");
> this.defragmentationThreadPoolSize = defragmentationThreadPoolSize;
> return this;
> }
> {code}
> should compare with 0:
> {code:java}
> A.ensure(defragmentationThreadPoolSize > 0, "Defragmentation thread pool size
> must be greater or equal to 1.");
> {code}
> Defragmentation actually works with just 1 thread. Also, 1 thread seems to be
> a workaround for https://issues.apache.org/jira/browse/IGNITE-19904 . I
> couldn't detect the failure with one defragmentation worker.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19759) Calcite engine. Review list of reserved keywords
[
https://issues.apache.org/jira/browse/IGNITE-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743086#comment-17743086
]
Ignite TC Bot commented on IGNITE-19759:
{panel:title=Branch: [pull/10839/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10839/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=723]]
* {color:#013220}IgniteCalciteTestSuite: SqlReservedWordsTest.testReservedWords
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7254801&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Review list of reserved keywords
>
>
> Key: IGNITE-19759
> URL: https://issues.apache.org/jira/browse/IGNITE-19759
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> For the calcite engine we have too strict list of reserved keywords. For
> example, lexems such as "TYPE" and "OPTIONS" are reserved keywords and can't
> be used as columns or table names. But "TYPE" is frequently used by users as
> column name and we should exclude it from the list of reserved keywords (add
> it to non-reserved keywords, see {{config.fmpp}} file {{nonReservedKeywords}}
> section). Other vendors allow to use "TYPE" as column name.
> On the other hand Calcite-based SQL engine in Ignite now allows to use some
> keywords which should not be allowed as table or column names, for example,
> such query executes without any problem:
> {noformat}
> sql("create table true (like varchar, and int, as int)");
> sql("insert into true values ('1', 1, 1)");
> sql("select as as as from true where like like '%' and and between
> and and and");
> {noformat}
> Current list of reserved keywords copied from "Babel" dialect of Calcite.
> Calcite has "default" dialect with default list of reserved keywords (see
> [1]), this list is close to SQL stantard, but looks quite strict too.
> Other vendors lists are less restrictive. For example, in SQL standard
> build-in functions and all built-in types are reserved keywords, in MySQL
> built-in functions are not reserved, but build-in types are reserved, in
> PostgreeSQL only minimal amount of keywords required for correct parsing are
> reserved (built-in functions are not reserved, built-in types are not
> reserved). See comparison table [2]. Our old SQL engine based on H2 database
> and H2 reserved keywords (see [3]). H2 approach is close to PostgreeSQL
> approach (minimal amount of keywords are reserved). I propose to use such an
> approach for Ignite too, to maximaze compatibility between our SQL engines.
> [1] https://calcite.apache.org/docs/reference.html#keywords
> [2] https://en.wikipedia.org/wiki/List_of_SQL_reserved_words
> [3] https://www.h2database.com/html/advanced.html#keywords
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19975) Create abstract SSL context factory to make it possible to implement custom logic for trust/key managers creation.
[
https://issues.apache.org/jira/browse/IGNITE-19975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743386#comment-17743386
]
Ignite TC Bot commented on IGNITE-19975:
{panel:title=Branch: [pull/10841/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10841/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7257356&buildTypeId=IgniteTests24Java8_RunAll]
> Create abstract SSL context factory to make it possible to implement custom
> logic for trust/key managers creation.
> --
>
> Key: IGNITE-19975
> URL: https://issues.apache.org/jira/browse/IGNITE-19975
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Petrov
>Priority: Minor
> Fix For: 2.16
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> SslContextFactory currently provides implementations of a trust/key manager
> loading mechanism based on getting key material from files only.
> In some cases, the key material can be obtained through some external storage
> that has nothing to do with file paths. Let's create an abstract
> implementation of SslContextFactory that will allow the user to implement
> their own approach for creating key/trust managers.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19725) Calcite-2. Add local flag support
[
https://issues.apache.org/jira/browse/IGNITE-19725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743560#comment-17743560
]
Ignite TC Bot commented on IGNITE-19725:
{panel:title=Branch: [pull/10788/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10788/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
8|https://ci2.ignite.apache.org/viewLog.html?buildId=7257389]]
* {color:#013220}IgniteCalciteTestSuite:
LocalQueryIntegrationTest.testReplicated - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: LocalQueryIntegrationTest.testJoin -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
LocalQueryIntegrationTest.testJoinReplicated - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: LocalQueryIntegrationTest.testSingle -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
LocalQueryIntegrationTest.testCreateTableAsSelect - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: LocalQueryIntegrationTest.testDelete -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
LocalQueryIntegrationTest.testInsertFromSelect - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: LocalQueryIntegrationTest.testCount -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7257470&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite-2. Add local flag support
> -
>
> Key: IGNITE-19725
> URL: https://issues.apache.org/jira/browse/IGNITE-19725
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite2-required, ise
> Fix For: 2.16
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19980) NPE within OOM exception during defragmentation.
[
https://issues.apache.org/jira/browse/IGNITE-19980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743954#comment-17743954
]
Ignite TC Bot commented on IGNITE-19980:
{panel:title=Branch: [pull/10844/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10844/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7261634&buildTypeId=IgniteTests24Java8_RunAll]
> NPE within OOM exception during defragmentation.
>
>
> Key: IGNITE-19980
> URL: https://issues.apache.org/jira/browse/IGNITE-19980
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.12
>Reporter: Vladimir Steshin
>Priority: Minor
> Attachments: IgnitePdsDefragmentationTest.java
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When defragmentating a partition, we can run out of the defragmentation
> region. Then, a OOM exception arises by
> {code:java}
> IgniteOutOfMemoryException PageMemoryImpl#oomException(String reason) {
> DataRegionConfiguration dataRegionCfg =
> getDataRegionConfiguration();
> return new IgniteOutOfMemoryException("Failed to find a page for
> eviction (" + reason + ") [" +
> "segmentCapacity=" + loadedPages.capacity() +
> ", loaded=" + loadedPages.size() +
> ", maxDirtyPages=" + maxDirtyPages +
> ", dirtyPages=" + dirtyPagesCntr +
> ", cpPages=" + (checkpointPages() == null ? 0 :
> checkpointPages().size()) +
> ", pinned=" + acquiredPages() +
> ']' + U.nl() + "Out of memory in data region [" +
> "name=" + dataRegionCfg.getName() +
> ", initSize=" +
> U.readableSize(dataRegionCfg.getInitialSize(), false) +
> ", maxSize=" + U.readableSize(dataRegionCfg.getMaxSize(),
> false) +
> ", persistenceEnabled=" +
> dataRegionCfg.isPersistenceEnabled() + "] Try the following:" + U.nl() +
> " ^-- Increase maximum off-heap memory size
> (DataRegionConfiguration.maxSize)" + U.nl() +
> " ^-- Enable eviction or expiration policies"
> );
> }
> {code}
> The problem is that
> {code:java}
> DataRegionConfiguration dataRegionCfg = getDataRegionConfiguration();
> {code}
> is actually null. @see `PageMemoryImpl#getDataRegionConfiguration()`.
> Stacktrace:
> {code:java}
> [defragmentation-thread][CachePartitionDefragmentationManager]
> Defragmentation process failed.
>
> org.apache.ignite.internal.processors.cache.persistence.freelist.CorruptedFreeListException:
> Failed to insert data row
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.insertDataRow(AbstractFreeList.java:600)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.CacheFreeList.insertDataRow(CacheFreeList.java:74)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.CacheFreeList.insertDataRow(CacheFreeList.java:35)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.defragmentation.CachePartitionDefragmentationManager.lambda$copyPartitionData$4(CachePartitionDefragmentationManager.java:741)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.defragmentation.TreeIterator.iterate(TreeIterator.java:83)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.defragmentation.CachePartitionDefragmentationManager.copyPartitionData(CachePartitionDefragmentationManager.java:718)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.defragmentation.CachePartitionDefragmentationManager.defragmentOnePartition(CachePartitionDefragmentationManager.java:565)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.defragmentation.CachePartitionDefragmentationManager.lambda$executeDefragmentation$66155109$1(CachePartitionDefragmentationManager.java:382)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.IgniteUtils.lambda$doInParallel$3(IgniteUtils.java:11661)
> ~[classes/:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]
> Suppressed:
> org.apache.ignite.internal.processors.cach
[jira] [Commented] (IGNITE-19746) control.sh --performance-statistics status doesn't not print actual status
[
https://issues.apache.org/jira/browse/IGNITE-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744906#comment-17744906
]
Ignite TC Bot commented on IGNITE-19746:
{panel:title=Branch: [pull/10847/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10847/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7263727&buildTypeId=IgniteTests24Java8_RunAll]
> control.sh --performance-statistics status doesn't not print actual status
> --
>
> Key: IGNITE-19746
> URL: https://issues.apache.org/jira/browse/IGNITE-19746
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Korotkov
>Assignee: Sergey Korotkov
>Priority: Major
> Labels: IEP-81, ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The status sub-command of the control.sh --performance-statistics doesn't not
> print the actual status to console.
> Previously it was like (note the *Disabled.* word):
> {noformat}
> Control utility [ver. 15.0.0-SNAPSHOT#20230422-sha1:7f80003d]
> 2023 Copyright(C) Apache Software Foundation
> User: ducker
> Time: 2023-04-23T22:17:12.489
> Command [PERFORMANCE-STATISTICS] started
> Arguments: --host x.x.x.x --performance-statistics status --user admin
> --password *
>
> Disabled.
> Command [PERFORMANCE-STATISTICS] finished with code: 0
> Control utility has completed execution at: 2023-04-23T22:17:13.271
> Execution time: 782 ms
> {noformat}
>
> Now it's like (note the absence of the *Disabled.* word):
> {noformat}
> Control utility [ver. 15.0.0-SNAPSHOT#20230613-sha1:cacee58d]
> 2023 Copyright(C) Apache Software Foundation
> User: ducker
> Time: 2023-06-15T15:46:41.586
> Command [PERFORMANCE-STATISTICS] started
> Arguments: --host x.x.x.x --performance-statistics status --user admin
> --password *
>
> Command [PERFORMANCE-STATISTICS] finished with code: 0
> Control utility has completed execution at: 2023-06-15T15:46:42.523
> Execution time: 937 ms
> {noformat}
>
> Outputs of other sub-commands are also need to be checked.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20010) Calcite engine. Query leaks on remote fragment initialization phase failure
[
https://issues.apache.org/jira/browse/IGNITE-20010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745526#comment-17745526
]
Ignite TC Bot commented on IGNITE-20010:
{panel:title=Branch: [pull/10849/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10849/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7264731]]
* {color:#013220}IgniteCalciteTestSuite:
RunningQueriesIntegrationTest.testErrorOnRemoteFragment - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7264812&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Query leaks on remote fragment initialization phase failure
> ---
>
> Key: IGNITE-20010
> URL: https://issues.apache.org/jira/browse/IGNITE-20010
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If any error occurs on remote fragment initialization phase (for example,
> LogicalRelImplementor throws an exception), query doesn't removed from
> running query manager
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20026) Java thin client does not allow ports greater than 49151
[
https://issues.apache.org/jira/browse/IGNITE-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746992#comment-17746992
]
Ignite TC Bot commented on IGNITE-20026:
{panel:title=Branch: [pull/10856/head] Base: [master] : Possible Blockers
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Snapshots{color} [[tests 0 Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7382192]]
{color:#d04437}Disk Page Compressions 1{color} [[tests 0 Exit Code , Failure on
metric |https://ci.ignite.apache.org/viewLog.html?buildId=7382210]]
{color:#d04437}Cache 7{color} [[tests 0 Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7382117]]
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7382166]]
* IgnitePdsTestSuite2: CdcSelfTest.testMultiNodeConsumption[consistentId=false,
wal=FSYNC, persistence=false] - Test has low fail rate in base branch 0,0% and
is not flaky
{color:#d04437}SPI (Discovery){color} [[tests 0 TIMEOUT , Exit Code , Failure
on metric |https://ci.ignite.apache.org/viewLog.html?buildId=7382195]]
{color:#d04437}Cache 5{color} [[tests 0 TIMEOUT , Exit Code , Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=7382115]]
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=7382165]]
* IgnitePdsTestSuite:
IgniteClusterActivateDeactivateTestWithPersistence.testClientJoinsWhenActivationIsInProgress
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10856/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=7382213&buildTypeId=IgniteTests24Java8_RunAll]
> Java thin client does not allow ports greater than 49151
>
>
> Key: IGNITE-20026
> URL: https://issues.apache.org/jira/browse/IGNITE-20026
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.15
>Reporter: Pavel Tupitsyn
>Assignee: ZhangJian He
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> *TcpClientChannel.validateConfiguration* rejects ports outside of 1024 -
> 49151 range (https://en.wikipedia.org/wiki/Registered_port), for no good
> reason. Remove this limitation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20026) Java thin client does not allow ports greater than 49151
[
https://issues.apache.org/jira/browse/IGNITE-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747316#comment-17747316
]
Ignite TC Bot commented on IGNITE-20026:
{panel:title=Branch: [pull/10856/head] Base: [master] : Possible Blockers
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Snapshots{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=7383222]]
{color:#d04437}Disk Page Compressions 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=7383224]]
{color:#d04437}Cache 7{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=7383226]]
{panel}
{panel:title=Branch: [pull/10856/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=7382213&buildTypeId=IgniteTests24Java8_RunAll]
> Java thin client does not allow ports greater than 49151
>
>
> Key: IGNITE-20026
> URL: https://issues.apache.org/jira/browse/IGNITE-20026
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.15
>Reporter: Pavel Tupitsyn
>Assignee: ZhangJian He
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> *TcpClientChannel.validateConfiguration* rejects ports outside of 1024 -
> 49151 range (https://en.wikipedia.org/wiki/Registered_port), for no good
> reason. Remove this limitation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20038) [Thin Client] Cache operations with PA enabled can fail with BufferUnderflowException
[
https://issues.apache.org/jira/browse/IGNITE-20038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747606#comment-17747606
]
Ignite TC Bot commented on IGNITE-20038:
{panel:title=Branch: [pull/10854/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10854/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Thin Client: Java{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7271546]]
* {color:#013220}ClientTestSuite:
ThinClientPartitionAwarenessStableTopologyTest.testMultipleCacheGroupAffinityMappingRequest
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7271560&buildTypeId=IgniteTests24Java8_RunAll]
> [Thin Client] Cache operations with PA enabled can fail with
> BufferUnderflowException
> ---
>
> Key: IGNITE-20038
> URL: https://issues.apache.org/jira/browse/IGNITE-20038
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.14, 2.15
> Environment:
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Cache operations with PA enabled can fail on thin clients with
> BufferUnderflowException due to broken ClientCachePartitionAwarenessGroup
> serialization.
> Exception:
> {code:java}
> java.nio.BufferUnderflowException
> at java.nio.Buffer.nextGetIndex(Buffer.java:532)
> at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:366)
> at
> org.apache.ignite.internal.binary.streams.BinaryByteBufferInputStream.readInt(BinaryByteBufferInputStream.java:111)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readInt(BinaryReaderExImpl.java:746)
> at
> org.apache.ignite.internal.client.thin.ClientCacheAffinityMapping.readCacheKeyConfiguration(ClientCacheAffinityMapping.java:240)
> at
> org.apache.ignite.internal.client.thin.ClientCacheAffinityMapping.readResponse(ClientCacheAffinityMapping.java:197)
> at
> org.apache.ignite.internal.client.thin.ClientCacheAffinityContext.readPartitionsUpdateResponse(ClientCacheAffinityContext.java:154)
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.receive(TcpClientChannel.java:412)
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.service(TcpClientChannel.java:311)
> at
> org.apache.ignite.internal.client.thin.ThinClientAbstractPartitionAwarenessTest$TestTcpClientChannel.service(ThinClientAbstractPartitionAwarenessTest.java:345)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.lambda$affinityInfoIsUpToDate$6(ReliableChannel.java:423)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.applyOnNodeChannel(ReliableChannel.java:746)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.affinityInfoIsUpToDate(ReliableChannel.java:422)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.affinityService(ReliableChannel.java:316)
> at
> org.apache.ignite.internal.client.thin.TcpClientCache.txAwareService(TcpClientCache.java:1139)
> at
> org.apache.ignite.internal.client.thin.TcpClientCache.cacheSingleKeyOperation(TcpClientCache.java:1198)
> at
> org.apache.ignite.internal.client.thin.TcpClientCache.get(TcpClientCache.java:146)
> at
> org.apache.ignite.internal.client.thin.ThinClientPartitionAwarenessStableTopologyTest.lambda$testMultipleCacheGroupPartitionsRequest$8(ThinClientPartitionAwarenessStableTopologyTest.java:250)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$4(GridTestUtils.java:1229)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1570)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:88)
> {code}
> Reproducer:
> {code:java}
> /** */
> @Test
> public void test() throws Exception {
> Ignite ignite = startGrid(0);
> ignite.createCache(new
> CacheConfiguration<>("test-cache-0").setCacheMode(REPLICATED));
> ignite.createCache(new
> CacheConfiguration<>("test-cache-1").setCacheMode(PARTITIONED));
> try (IgniteClient cli = Ignition.startClient(new
> ClientConfiguration().setAddresses("127.0.0.1:10800"))) {
> ClientCacheAffinityContext affCtx =
> ((TcpIgniteClient)cli).reliableChannel().affinityContext();
> IgniteInternalFuture replCacheOpFut;
> IgniteInternalFuture partCacheOpFut;
> synchronized (affCtx.cacheKeyMapperFactoryMap) {
> partCacheOpFut = GridTestUtils.runAsync(() ->
> cli.cache("test-ca
[jira] [Commented] (IGNITE-20006) Calcite engine. Make table/index scan iterators yieldable
[
https://issues.apache.org/jira/browse/IGNITE-20006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748329#comment-17748329
]
Ignite TC Bot commented on IGNITE-20006:
{panel:title=Branch: [pull/10852/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10852/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7265886&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Make table/index scan iterators yieldable
> --
>
> Key: IGNITE-20006
> URL: https://issues.apache.org/jira/browse/IGNITE-20006
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, index/table iterators can scan unpredictable count of cache
> entries during one {{hasNext()}}/{{next()}} call. These iterators contain
> filter, which applyed to each entry and row produced only for entries that
> satisfy filter. If filter contains "always false" rule, one {{hasNext()}}
> call may scan entiry table uninterruptably, without timeouts and yields to
> make another queries do their job. We should fix this behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20085) GridNearTxRemote initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749129#comment-17749129
]
Ignite TC Bot commented on IGNITE-20085:
{panel:title=Branch: [pull/10861/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10861/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7273711&buildTypeId=IgniteTests24Java8_RunAll]
> GridNearTxRemote initial cleanup
>
>
> Key: IGNITE-20085
> URL: https://issues.apache.org/jira/browse/IGNITE-20085
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20093) GridCacheSharedManagerAdapter initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749157#comment-17749157
]
Ignite TC Bot commented on IGNITE-20093:
{panel:title=Branch: [pull/10863/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10863/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7273939&buildTypeId=IgniteTests24Java8_RunAll]
> GridCacheSharedManagerAdapter initial cleanup
> -
>
> Key: IGNITE-20093
> URL: https://issues.apache.org/jira/browse/IGNITE-20093
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20084) GridDistributedTxRemoteAdapter initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749176#comment-17749176
]
Ignite TC Bot commented on IGNITE-20084:
{panel:title=Branch: [pull/10860/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10860/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7273597&buildTypeId=IgniteTests24Java8_RunAll]
> GridDistributedTxRemoteAdapter initial cleanup
> --
>
> Key: IGNITE-20084
> URL: https://issues.apache.org/jira/browse/IGNITE-20084
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20088) GridDhtTxRemote initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749221#comment-17749221
]
Ignite TC Bot commented on IGNITE-20088:
{panel:title=Branch: [pull/10862/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10862/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7273825&buildTypeId=IgniteTests24Java8_RunAll]
> GridDhtTxRemote initial cleanup
> ---
>
> Key: IGNITE-20088
> URL: https://issues.apache.org/jira/browse/IGNITE-20088
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20094) IgniteTxManager initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749231#comment-17749231
]
Ignite TC Bot commented on IGNITE-20094:
{panel:title=Branch: [pull/10864/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10864/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7274053&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxManager initial cleanup
> ---
>
> Key: IGNITE-20094
> URL: https://issues.apache.org/jira/browse/IGNITE-20094
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20123) IgniteTxHandler initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750435#comment-17750435
]
Ignite TC Bot commented on IGNITE-20123:
{panel:title=Branch: [pull/10869/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10869/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7279555&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxHandler initial cleanup
> ---
>
> Key: IGNITE-20123
> URL: https://issues.apache.org/jira/browse/IGNITE-20123
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20112) IgniteTxImplicitSingleStateImpl initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750440#comment-17750440
]
Ignite TC Bot commented on IGNITE-20112:
{panel:title=Branch: [pull/10867/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10867/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7279783&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxImplicitSingleStateImpl initial cleanup
> ---
>
> Key: IGNITE-20112
> URL: https://issues.apache.org/jira/browse/IGNITE-20112
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19904) Assertion in defragmentation
[
https://issues.apache.org/jira/browse/IGNITE-19904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750461#comment-17750461
]
Ignite TC Bot commented on IGNITE-19904:
{panel:title=Branch: [pull/10866/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10866/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7280731&buildTypeId=IgniteTests24Java8_RunAll]
> Assertion in defragmentation
>
>
> Key: IGNITE-19904
> URL: https://issues.apache.org/jira/browse/IGNITE-19904
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.12
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Attachments: default-config.xml, failure2.16_with_thread_dump.log,
> failure_with_root_npe_cause.log, ignite.log, jvm.opts
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Defragmentaion fails with:
> {code:java}
> java.lang.AssertionError: Invalid state. Type is 0! pageId = 0001000d00024cbf
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1359)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.checkpointWritePage(PageMemoryImpl.java:1277)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointPagesWriter.writePages(CheckpointPagesWriter.java:208)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointPagesWriter.run(CheckpointPagesWriter.java:150)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> {code}
> Difficult to write a test. Can't reproduce on my computers :(. Flackly
> appears on a server (4 core x 4 cpu) with 100G of the test cache data and
> million+ pages to checkpoint during defragmentation. More often, this occurs
> with pageSize 1024 (to produce more pages).
> Regarding my diagnostic build, I suppose that a fresh, empty page is caught
> in defragmentation. Here is a page dump with test-expented PAGE_OVERHEAD
> (=64) and same error a bit before copyPageForCheckpoint():
> {code:java}
> org.apache.ignite.IgniteException: Wrong page type in checkpointWritePage1.
> Page: Data region = 'defragPartitionsDataRegion'.
> FullPageId [pageId=281878703760205, effectivePageId=403727049549,
> grpId=-1368047378].
> PageDump = page_id: 281878703760205, rel_id: 48603, cache_id: -1368047378,
> pin: 0, lock: 65536, tmp_buf: 72057594037927935, test_val: 1. data_hex:
> 0
[jira] [Commented] (IGNITE-19904) Assertion in defragmentation
[
https://issues.apache.org/jira/browse/IGNITE-19904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750481#comment-17750481
]
Ignite TC Bot commented on IGNITE-19904:
{panel:title=Branch: [pull/10866/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10866/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7280731&buildTypeId=IgniteTests24Java8_RunAll]
> Assertion in defragmentation
>
>
> Key: IGNITE-19904
> URL: https://issues.apache.org/jira/browse/IGNITE-19904
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.12
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Attachments: default-config.xml, failure2.16_with_thread_dump.log,
> failure_with_root_npe_cause.log, ignite.log, jvm.opts
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Defragmentaion fails with:
> {code:java}
> java.lang.AssertionError: Invalid state. Type is 0! pageId = 0001000d00024cbf
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1359)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.checkpointWritePage(PageMemoryImpl.java:1277)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointPagesWriter.writePages(CheckpointPagesWriter.java:208)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointPagesWriter.run(CheckpointPagesWriter.java:150)
> ~[ignite-core-2.16.0-SNAPSHOT.jar:2.16.0-SNAPSHOT]
> {code}
> Difficult to write a test. Can't reproduce on my computers :(. Flackly
> appears on a server (4 core x 4 cpu) with 100G of the test cache data and
> million+ pages to checkpoint during defragmentation. More often, this occurs
> with pageSize 1024 (to produce more pages).
> Regarding my diagnostic build, I suppose that a fresh, empty page is caught
> in defragmentation. Here is a page dump with test-expented PAGE_OVERHEAD
> (=64) and same error a bit before copyPageForCheckpoint():
> {code:java}
> org.apache.ignite.IgniteException: Wrong page type in checkpointWritePage1.
> Page: Data region = 'defragPartitionsDataRegion'.
> FullPageId [pageId=281878703760205, effectivePageId=403727049549,
> grpId=-1368047378].
> PageDump = page_id: 281878703760205, rel_id: 48603, cache_id: -1368047378,
> pin: 0, lock: 65536, tmp_buf: 72057594037927935, test_val: 1. data_hex:
> 0
[jira] [Commented] (IGNITE-20142) Introduce changes for JDK17 tests run
[
https://issues.apache.org/jira/browse/IGNITE-20142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750684#comment-17750684
]
Ignite TC Bot commented on IGNITE-20142:
{panel:title=Branch: [pull/10873/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=7280970]]
{color:#d04437}Cache 2{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7280902]]
* IgniteCacheTestSuite2:
GridCachePartitionedTxMultiThreadedSelfTest.testPessimisticReadCommittedCommitMultithreaded
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Disk Page Compressions 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7281000]]
* IgnitePdsCompressionTestSuite:
IgniteClusterActivateDeactivateTestWithPersistence.testInactiveTopologyChangesReadOnly
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Snapshots{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7280982]]
* IgniteSnapshotTestSuite:
IgniteSnapshotRestoreFromRemoteTest.testSnapshotCachesStoppedIfLoadingFailOnRemote[encryption=true,
onlyPrimay=false] - Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/10873/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7281003&buildTypeId=IgniteTests24Java8_RunAll]
> Introduce changes for JDK17 tests run
> -
>
> Key: IGNITE-20142
> URL: https://issues.apache.org/jira/browse/IGNITE-20142
> Project: Ignite
> Issue Type: Improvement
>Reporter: Petr Ivanov
>Assignee: Petr Ivanov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
>
> Introduce several changes and extend current WAs for ability to run tests
> under JDK17.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20113) IgniteTxStateImpl initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750736#comment-17750736
]
Ignite TC Bot commented on IGNITE-20113:
{panel:title=Branch: [pull/10868/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10868/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7279669&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxStateImpl initial cleanup
> -
>
> Key: IGNITE-20113
> URL: https://issues.apache.org/jira/browse/IGNITE-20113
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20141) Transaction will never become finished on timeout when deadlock detection is disabled.
[
https://issues.apache.org/jira/browse/IGNITE-20141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750753#comment-17750753
]
Ignite TC Bot commented on IGNITE-20141:
{panel:title=Branch: [pull/10872/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10872/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7280849&buildTypeId=IgniteTests24Java8_RunAll]
> Transaction will never become finished on timeout when deadlock detection is
> disabled.
> --
>
> Key: IGNITE-20141
> URL: https://issues.apache.org/jira/browse/IGNITE-20141
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> TxRollbackOnTimeoutNoDeadlockDetectionTest has no failures at CI because
> Ignite ignores IGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS property set after it
> already set by previous tests (static field).
> But, when you run this test separately it fails because transaction will
> never become finished on timeout when deadlockDetection is dissabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20094) IgniteTxManager initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750814#comment-17750814
]
Ignite TC Bot commented on IGNITE-20094:
{panel:title=Branch: [pull/10864/head] Base: [master] : Possible Blockers
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Deadlock Detection){color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7282522]]
* TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsPessimisticDetectionEnabled - New
test duration 121s is more that 1 minute
* TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsOptimisticDetectionDisabled - New
test duration 122s is more that 1 minute
* TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsOptimisticDetectionEnabled - New test
duration 121s is more that 1 minute
* TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsPessimisticDetectionDisabled - New
test duration 123s is more that 1 minute
{panel}
{panel:title=Branch: [pull/10864/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache (Deadlock Detection){color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7282522]]
* {color:#013220}TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsPessimisticDetectionEnabled -
PASSED{color}
* {color:#013220}TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsOptimisticDetectionDisabled -
PASSED{color}
* {color:#013220}TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsOptimisticDetectionEnabled -
PASSED{color}
* {color:#013220}TxDeadlockDetectionTestSuite:
TxDeadlockDetectionNoHangsTest.testNoHangsPessimisticDetectionDisabled -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7279392&buildTypeId=IgniteTests24Java8_RunAll]
> IgniteTxManager initial cleanup
> ---
>
> Key: IGNITE-20094
> URL: https://issues.apache.org/jira/browse/IGNITE-20094
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20142) Introduce changes for JDK17 tests run
[
https://issues.apache.org/jira/browse/IGNITE-20142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750826#comment-17750826
]
Ignite TC Bot commented on IGNITE-20142:
{panel:title=Branch: [pull/10873/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10873/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7282379&buildTypeId=IgniteTests24Java8_RunAll]
> Introduce changes for JDK17 tests run
> -
>
> Key: IGNITE-20142
> URL: https://issues.apache.org/jira/browse/IGNITE-20142
> Project: Ignite
> Issue Type: Improvement
>Reporter: Petr Ivanov
>Assignee: Petr Ivanov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
>
> Introduce several changes and extend current WAs for ability to run tests
> under JDK17.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19163) Add logging of snapshot check
[
https://issues.apache.org/jira/browse/IGNITE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750986#comment-17750986
]
Ignite TC Bot commented on IGNITE-19163:
{panel:title=Branch: [pull/10825/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10825/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7282501&buildTypeId=IgniteTests24Java8_RunAll]
> Add logging of snapshot check
> -
>
> Key: IGNITE-19163
> URL: https://issues.apache.org/jira/browse/IGNITE-19163
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: iep-43, ise
> Fix For: 2.16
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Server nodes do not log state of snapshot check process, but it is necessary
> for further analysis to print messages in log, when snapshot check procedure
> started and finished. Currently, snapshot check invoked at least by restore
> and check commands.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19160) Improve message about sent partition file during snapshot restore
[
https://issues.apache.org/jira/browse/IGNITE-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751059#comment-17751059
]
Ignite TC Bot commented on IGNITE-19160:
{panel:title=Branch: [pull/10871/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10871/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7283055&buildTypeId=IgniteTests24Java8_RunAll]
> Improve message about sent partition file during snapshot restore
> -
>
> Key: IGNITE-19160
> URL: https://issues.apache.org/jira/browse/IGNITE-19160
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: iep-43, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, message about partition is as below:
> {quote}
> [2023-03-29T18:31:44,773][INFO ][snapshot-runner-#863%node0%][SnapshotSender]
> Partition file has been send [part=part-645.bin,
> pair={color:red}GroupPartitionId [grpId=1544803905, partId=645]{color},
> length=45056]
> {quote}
> It does not tell us:
> # Receiver node id / address / consistent id.
> # Cache or cache group name which partition belongs to. Numerical group id is
> not convenient way to determine cache or cache group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20143) GridIntList & GridLongList initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751093#comment-17751093
]
Ignite TC Bot commented on IGNITE-20143:
{panel:title=Branch: [pull/10874/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10874/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7281117&buildTypeId=IgniteTests24Java8_RunAll]
> GridIntList & GridLongList initial cleanup
> --
>
> Key: IGNITE-20143
> URL: https://issues.apache.org/jira/browse/IGNITE-20143
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20141) Transaction will never become finished on timeout when deadlock detection is disabled.
[
https://issues.apache.org/jira/browse/IGNITE-20141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751134#comment-17751134
]
Ignite TC Bot commented on IGNITE-20141:
{panel:title=Branch: [pull/10872/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10872/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7284496&buildTypeId=IgniteTests24Java8_RunAll]
> Transaction will never become finished on timeout when deadlock detection is
> disabled.
> --
>
> Key: IGNITE-20141
> URL: https://issues.apache.org/jira/browse/IGNITE-20141
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> TxRollbackOnTimeoutNoDeadlockDetectionTest has no failures at CI because
> Ignite ignores IGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS property set after it
> already set by previous tests (static field).
> But, when you run this test separately it fails because transaction will
> never become finished on timeout when deadlockDetection is dissabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19998) Calcite-2. Add support of partitions in SqlFieldsQuery
[
https://issues.apache.org/jira/browse/IGNITE-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751231#comment-17751231
]
Ignite TC Bot commented on IGNITE-19998:
{panel:title=Branch: [pull/10870/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10870/head] Base: [master] : New Tests
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
14|https://ci2.ignite.apache.org/viewLog.html?buildId=7284797]]
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testJoinReplicated[local = true] -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testCreateTableAsSelect[local = true] -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testDelete[local = true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testInsertFromSelect[local = true] -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testReplicated[local = true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testJoin[local = true] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testCreateTableAsSelect[local = false] -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testDelete[local = false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testInsertFromSelect[local = false] -
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testSingle[local = false] - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite:
QueryWithPartitionsIntegrationTest.testSingle[local = true] - PASSED{color}
... and 3 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7284878&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite-2. Add support of partitions in SqlFieldsQuery
> --
>
> Key: IGNITE-19998
> URL: https://issues.apache.org/jira/browse/IGNITE-19998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite2-required, ise
> Fix For: 2.16
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20172) TX code cleanup scope #1 initial common cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751784#comment-17751784
]
Ignite TC Bot commented on IGNITE-20172:
{panel:title=Branch: [pull/10878/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10878/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7289281&buildTypeId=IgniteTests24Java8_RunAll]
> TX code cleanup scope #1 initial common cleanup
> ---
>
> Key: IGNITE-20172
> URL: https://issues.apache.org/jira/browse/IGNITE-20172
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20173) GridCacheCompoundIdentityFuture and it's ancestors initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751828#comment-17751828
]
Ignite TC Bot commented on IGNITE-20173:
{panel:title=Branch: [pull/10879/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10879/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7289509&buildTypeId=IgniteTests24Java8_RunAll]
> GridCacheCompoundIdentityFuture and it's ancestors initial cleanup
> --
>
> Key: IGNITE-20173
> URL: https://issues.apache.org/jira/browse/IGNITE-20173
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20176) GridNearTxAbstractEnlistFuture and it's descendants initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751904#comment-17751904
]
Ignite TC Bot commented on IGNITE-20176:
{panel:title=Branch: [pull/10882/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10882/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7289865&buildTypeId=IgniteTests24Java8_RunAll]
> GridNearTxAbstractEnlistFuture and it's descendants initial cleanup
> ---
>
> Key: IGNITE-20176
> URL: https://issues.apache.org/jira/browse/IGNITE-20176
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20174) CacheDistributedGetFutureAdapter and it's descendants initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752123#comment-17752123
]
Ignite TC Bot commented on IGNITE-20174:
{panel:title=Branch: [pull/10881/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10881/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7290990&buildTypeId=IgniteTests24Java8_RunAll]
> CacheDistributedGetFutureAdapter and it's descendants initial cleanup
> -
>
> Key: IGNITE-20174
> URL: https://issues.apache.org/jira/browse/IGNITE-20174
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20177) GridCacheCompoundIdentityFuture's child-free descendants initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752143#comment-17752143
]
Ignite TC Bot commented on IGNITE-20177:
{panel:title=Branch: [pull/10883/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10883/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7291501&buildTypeId=IgniteTests24Java8_RunAll]
> GridCacheCompoundIdentityFuture's child-free descendants initial cleanup
>
>
> Key: IGNITE-20177
> URL: https://issues.apache.org/jira/browse/IGNITE-20177
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19160) Improve message about sent partition file during snapshot restore
[
https://issues.apache.org/jira/browse/IGNITE-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752151#comment-17752151
]
Ignite TC Bot commented on IGNITE-19160:
{panel:title=Branch: [pull/10871/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10871/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7290876&buildTypeId=IgniteTests24Java8_RunAll]
> Improve message about sent partition file during snapshot restore
> -
>
> Key: IGNITE-19160
> URL: https://issues.apache.org/jira/browse/IGNITE-19160
> Project: Ignite
> Issue Type: Task
>Reporter: Ilya Shishkov
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: iep-43, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, message about partition is as below:
> {quote}
> [2023-03-29T18:31:44,773][INFO ][snapshot-runner-#863%node0%][SnapshotSender]
> Partition file has been send [part=part-645.bin,
> pair={color:red}GroupPartitionId [grpId=1544803905, partId=645]{color},
> length=45056]
> {quote}
> It does not tell us:
> # Receiver node id / address / consistent id.
> # Cache or cache group name which partition belongs to. Numerical group id is
> not convenient way to determine cache or cache group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20145) Update maven surefire version
[
https://issues.apache.org/jira/browse/IGNITE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752289#comment-17752289
]
Ignite TC Bot commented on IGNITE-20145:
{panel:title=Branch: [pull/10875/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper{color} [[tests 0 Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=7291651]]
{panel}
{panel:title=Branch: [pull/10875/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7291385&buildTypeId=IgniteTests24Java8_RunAll]
> Update maven surefire version
> -
>
> Key: IGNITE-20145
> URL: https://issues.apache.org/jira/browse/IGNITE-20145
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> There are many useful updates in new versions, such as
> [SUREFIRE-1426|https://issues.apache.org/jira/browse/SUREFIRE-1426]. This
> fixes the exit code in case of a fork failure and is needed for proper
> failure handling in CI tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20178) Introduce param-free IgniteInternalFuture.listen(() -> {}) in addition to .listen((fut) -> {}) to avoid ignored params
[
https://issues.apache.org/jira/browse/IGNITE-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753107#comment-17753107
]
Ignite TC Bot commented on IGNITE-20178:
{panel:title=Branch: [pull/10885/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10885/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7295033&buildTypeId=IgniteTests24Java8_RunAll]
> Introduce param-free IgniteInternalFuture.listen(() -> {}) in addition to
> .listen((fut) -> {}) to avoid ignored params
> --
>
> Key: IGNITE-20178
> URL: https://issues.apache.org/jira/browse/IGNITE-20178
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20194) Calcite engine. Dependency common-codec required for some functions
[
https://issues.apache.org/jira/browse/IGNITE-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753227#comment-17753227
]
Ignite TC Bot commented on IGNITE-20194:
{panel:title=Branch: [pull/10889/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10889/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7295200&buildTypeId=IgniteTests24Java8_RunAll]
> Calcite engine. Dependency common-codec required for some functions
> ---
>
> Key: IGNITE-20194
> URL: https://issues.apache.org/jira/browse/IGNITE-20194
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, ise
> Fix For: 2.16
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Some functions (md5, soundex) require common-codec dependency, but this
> dependency is not included explicitly to dependencies list and doesn't added
> to calcite library folder on build. Tests run with transitive dependencies
> and don't trigger the problem. Queries fail only when run on Ignite started
> from binary release package.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20145) Update maven surefire version
[
https://issues.apache.org/jira/browse/IGNITE-20145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753577#comment-17753577
]
Ignite TC Bot commented on IGNITE-20145:
{panel:title=Branch: [pull/10888/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10888/head] Base: [master] : New Tests
(256)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Snapshots{color} [[tests
256|https://ci2.ignite.apache.org/viewLog.html?buildId=7296957]]
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
... and 245 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7296533&buildTypeId=IgniteTests24Java8_RunAll]
> Update maven surefire version
> -
>
> Key: IGNITE-20145
> URL: https://issues.apache.org/jira/browse/IGNITE-20145
> Project: Ignite
> Issue Type: Task
>Reporter: Nikita Amelchev
>Assignee: Nikita Amelchev
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> There are many useful updates in new versions, such as
> [SUREFIRE-1426|https://issues.apache.org/jira/browse/SUREFIRE-1426]. This
> fixes the exit code in case of a fork failure and is needed for proper
> failure handling in CI tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20178) Introduce param-free IgniteInternalFuture.listen(() -> {}) in addition to .listen((fut) -> {}) to avoid ignored params
[
https://issues.apache.org/jira/browse/IGNITE-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753976#comment-17753976
]
Ignite TC Bot commented on IGNITE-20178:
{panel:title=Branch: [pull/10885/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10885/head] Base: [master] : New Tests
(42)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Snapshots{color} [[tests
42|https://ci2.ignite.apache.org/viewLog.html?buildId=7296412]]
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite: testsuites.IgniteSnapshotTestSuite -
PASSED{color}
... and 31 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7296273&buildTypeId=IgniteTests24Java8_RunAll]
> Introduce param-free IgniteInternalFuture.listen(() -> {}) in addition to
> .listen((fut) -> {}) to avoid ignored params
> --
>
> Key: IGNITE-20178
> URL: https://issues.apache.org/jira/browse/IGNITE-20178
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20216) Moving ML module to ignite-extensions
[
https://issues.apache.org/jira/browse/IGNITE-20216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755154#comment-17755154
]
Ignite TC Bot commented on IGNITE-20216:
{panel:title=Branch: [pull/10897/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7303635]]
* IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 - History for base
branch is absent.
* IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 - New test duration
121s is more that 1 minute
{panel}
{panel:title=Branch: [pull/10897/head] Base: [master] : New Tests
(151)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 5{color} [[tests
151|https://ci2.ignite.apache.org/viewLog.html?buildId=7303635]]
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: testsuites.IgniteCacheTestSuite5 -
PASSED{color}
... and 140 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7303474&buildTypeId=IgniteTests24Java8_RunAll]
> Moving ML module to ignite-extensions
> -
>
> Key: IGNITE-20216
> URL: https://issues.apache.org/jira/browse/IGNITE-20216
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It is time to move this module to ignite extensions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20228) Fix flaky test KillCommandsControlShTest
[
https://issues.apache.org/jira/browse/IGNITE-20228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755415#comment-17755415
]
Ignite TC Bot commented on IGNITE-20228:
{panel:title=Branch: [pull/10898/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10898/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7303599&buildTypeId=IgniteTests24Java8_RunAll]
> Fix flaky test KillCommandsControlShTest
>
>
> Key: IGNITE-20228
> URL: https://issues.apache.org/jira/browse/IGNITE-20228
> Project: Ignite
> Issue Type: Bug
>Reporter: Maksim Timonin
>Assignee: Maksim Timonin
>Priority: Major
> Labels: ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20217) GridCacheFutureAdapter and descendants initial cleanup
[
https://issues.apache.org/jira/browse/IGNITE-20217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755463#comment-17755463
]
Ignite TC Bot commented on IGNITE-20217:
{panel:title=Branch: [pull/10896/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10896/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7302409&buildTypeId=IgniteTests24Java8_RunAll]
> GridCacheFutureAdapter and descendants initial cleanup
> --
>
> Key: IGNITE-20217
> URL: https://issues.apache.org/jira/browse/IGNITE-20217
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.16
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20201) Node failure when incorrect names are used for hitrate and histogram metrics configuration
[
https://issues.apache.org/jira/browse/IGNITE-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756776#comment-17756776
]
Ignite TC Bot commented on IGNITE-20201:
{panel:title=Branch: [pull/10903/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10903/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 4{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7308626]]
* {color:#013220}IgniteBasicTestSuite2:
MetricConfigurationTest.testInvalidMetricConfigurationName - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7308733&buildTypeId=IgniteTests24Java8_RunAll]
> Node failure when incorrect names are used for hitrate and histogram metrics
> configuration
> --
>
> Key: IGNITE-20201
> URL: https://issues.apache.org/jira/browse/IGNITE-20201
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.15
>Reporter: Ilya Shishkov
>Assignee: Mikhail Petrov
>Priority: Critical
> Labels: ise
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> There are no metric name validation when we perform hitrate and historgam
> metrics configuration by means of control script. It can lead to
> impossibility to restart persistent cluster.
> *How to reproduce:*
> # Start persistent cluster.
> # Enter commands from instructions [1].
> {noformat}
> control.sh —metric —configure-histogram histogram-metric-name 1,2,3
> control.sh —metric —configure-hitrate hitrate-metric-name 1000
> {noformat}
> # Deactivate and restart cluster.
> # Start and activate cluster and nodes will fail with following error:
> {noformat}
> [19:47:26,981][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.ignite.internal.processors.metric.impl.MetricUtils.fromFullName(MetricUtils.java:72)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.find(GridMetricManager.java:502)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.onHistogramConfigChanged(GridMetricManager.java:480)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager.access$300(GridMetricManager.java:73)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager$1.lambda$onReadyForRead$1(GridMetricManager.java:272)
> at
> org.apache.ignite.internal.processors.metastorage.persistence.InMemoryCachedDistributedMetaStorageBridge.iterate(InMemoryCachedDistributedMetaStorageBridge.java:87)
> at
> org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl.iterate(DistributedMetaStorageImpl.java:542)
> at
> org.apache.ignite.internal.processors.metric.GridMetricManager$1.onReadyForRead(GridMetricManager.java:272)
> at
> org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl.notifyReadyForRead(DistributedMetaStorageImpl.java:355)
> at
> org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl.onMetaStorageReadyForRead(DistributedMetaStorageImpl.java:434)
> at
> org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl.access$200(DistributedMetaStorageImpl.java:116)
> at
> org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl$2.onReadyForRead(DistributedMetaStorageImpl.java:259)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:430)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:877)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:3094)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1120)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1725)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1647)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1089)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:983)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.jav
[jira] [Commented] (IGNITE-20253) Backport IGNITE-19096 Sql. Remove code that replaces placeholder values from ModifyNode
[
https://issues.apache.org/jira/browse/IGNITE-20253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756828#comment-17756828
]
Ignite TC Bot commented on IGNITE-20253:
{panel:title=Branch: [pull/10906/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0 TIMEOUT , Exit Code
|https://ci2.ignite.apache.org/viewLog.html?buildId=7310863]]
{panel}
{panel:title=Branch: [pull/10906/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=7310873]]
* {color:#013220}IgniteCalciteTestSuite:
TableDmlIntegrationTest.testInsertMultipleDefaults - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7306949&buildTypeId=IgniteTests24Java8_RunAll]
> Backport IGNITE-19096 Sql. Remove code that replaces placeholder values from
> ModifyNode
> ---
>
> Key: IGNITE-20253
> URL: https://issues.apache.org/jira/browse/IGNITE-20253
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: calcite, calcite2-required, ise
> Fix For: 2.16
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20245) MVCC test/suites removal
[
https://issues.apache.org/jira/browse/IGNITE-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757651#comment-17757651
]
Ignite TC Bot commented on IGNITE-20245:
{panel:title=Branch: [pull/10900/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10900/head] Base: [master] : New Tests
(21)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}JDBC Driver{color} [[tests
3|https://ci2.ignite.apache.org/viewLog.html?buildId=7312426]]
* {color:#013220}IgniteJdbcDriverTestSuite:
JdbcThinConnectionSelfTest.testRollbackIgnored - PASSED{color}
* {color:#013220}IgniteJdbcDriverTestSuite:
JdbcThinConnectionSelfTest.testBeginFails - PASSED{color}
* {color:#013220}IgniteJdbcDriverTestSuite:
JdbcThinConnectionSelfTest.testCommitIgnored - PASSED{color}
{color:#8b}Cache 6{color} [[tests
12|https://ci2.ignite.apache.org/viewLog.html?buildId=7312385]]
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[-1
true false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[0
true false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[2
true false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[-1
false true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[-1
false false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[0
false false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[2
false false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[2
true true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[0
false true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[2
false true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
CachePartitionLossWithRestartsTest.testPartitionLossDetectionOnClientTopology[-1
true true] - PASSED{color}
... and 1 new tests
{color:#8b}Queries 3 (lazy=true){color} [[tests
3|https://ci2.ignite.apache.org/viewLog.html?buildId=7312455]]
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
SqlTransactionCommandsSelfTest.testBeginWithMvccDisabled - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
SqlTransactionCommandsSelfTest.testRollbackWithMvccDisabled - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryLazyTestSuite3:
SqlTransactionCommandsSelfTest.testCommitWithMvccDisabled - PASSED{color}
{color:#8b}Queries 3{color} [[tests
3|https://ci2.ignite.apache.org/viewLog.html?buildId=7312454]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
SqlTransactionCommandsSelfTest.testRollbackWithMvccDisabled - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
SqlTransactionCommandsSelfTest.testCommitWithMvccDisabled - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite3:
SqlTransactionCommandsSelfTest.testBeginWithMvccDisabled - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7312481&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC test/suites removal
>
>
> Key: IGNITE-20245
> URL: https://issues.apache.org/jira/browse/IGNITE-20245
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20309) Snapshot creation returns OK even if check failed
[
https://issues.apache.org/jira/browse/IGNITE-20309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760510#comment-17760510
]
Ignite TC Bot commented on IGNITE-20309:
{panel:title=Branch: [pull/10913/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10913/head] Base: [master] : New Tests
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Disk Page Compressions 1{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7322534]]
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=false] - PASSED{color}
{color:#8b}Snapshots{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7322555]]
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=false] - PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=true,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=true,
onlyPrimay=false] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7321997&buildTypeId=IgniteTests24Java8_RunAll]
> Snapshot creation returns OK even if check failed
> -
>
> Key: IGNITE-20309
> URL: https://issues.apache.org/jira/browse/IGNITE-20309
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Currently, {{SnapshotPartitionsQuickVerifyHandler#complete}} don't fail
> snapshot even if {{invoke}} throws.
> Reproducer:
>
> {noformat}
> /**
> * Test ensures that snapshot fail if during check some files are absent.
> * @see SnapshotPartitionsQuickVerifyHandler
> */
> @Test
> public void testHandlerExceptionFailSnapshot() throws Exception {
> handlers.add(new SnapshotHandler() {
> @Override public SnapshotHandlerType type() {
> return SnapshotHandlerType.CREATE;
> }
> @Override public Void invoke(SnapshotHandlerContext ctx) {
> // Someone remove snapshot files during creation.
> // In this case snapshot must fail.
> U.delete(ctx.snapshotDirectory());
> return null;
> }
> });
> IgniteEx ignite = startGridsWithCache(1, CACHE_KEYS_RANGE,
> valueBuilder(), dfltCacheCfg);
> assertThrows(
> null,
> () -> snp(ignite).createSnapshot("must_fail", null, false,
> onlyPrimary).get(getTestTimeout()),
> IgniteException.class,
> "Snapshot data doesn't contain required cache group partition"
> );
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20309) Snapshot creation returns OK even if check failed
[
https://issues.apache.org/jira/browse/IGNITE-20309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760509#comment-17760509
]
Ignite TC Bot commented on IGNITE-20309:
{panel:title=Branch: [pull/10913/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10913/head] Base: [master] : New Tests
(6)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Disk Page Compressions 1{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=7322534]]
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgnitePdsCompressionTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=false] - PASSED{color}
{color:#8b}Snapshots{color} [[tests
4|https://ci2.ignite.apache.org/viewLog.html?buildId=7322555]]
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=false,
onlyPrimay=false] - PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=true,
onlyPrimay=true] - PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteClusterSnapshotHandlerTest.testHandlerExceptionFailSnapshot[encryption=true,
onlyPrimay=false] - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7321997&buildTypeId=IgniteTests24Java8_RunAll]
> Snapshot creation returns OK even if check failed
> -
>
> Key: IGNITE-20309
> URL: https://issues.apache.org/jira/browse/IGNITE-20309
> Project: Ignite
> Issue Type: Bug
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Currently, {{SnapshotPartitionsQuickVerifyHandler#complete}} don't fail
> snapshot even if {{invoke}} throws.
> Reproducer:
>
> {noformat}
> /**
> * Test ensures that snapshot fail if during check some files are absent.
> * @see SnapshotPartitionsQuickVerifyHandler
> */
> @Test
> public void testHandlerExceptionFailSnapshot() throws Exception {
> handlers.add(new SnapshotHandler() {
> @Override public SnapshotHandlerType type() {
> return SnapshotHandlerType.CREATE;
> }
> @Override public Void invoke(SnapshotHandlerContext ctx) {
> // Someone remove snapshot files during creation.
> // In this case snapshot must fail.
> U.delete(ctx.snapshotDirectory());
> return null;
> }
> });
> IgniteEx ignite = startGridsWithCache(1, CACHE_KEYS_RANGE,
> valueBuilder(), dfltCacheCfg);
> assertThrows(
> null,
> () -> snp(ignite).createSnapshot("must_fail", null, false,
> onlyPrimary).get(getTestTimeout()),
> IgniteException.class,
> "Snapshot data doesn't contain required cache group partition"
> );
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
