[jira] [Comment Edited] (IGNITE-22917) Remove GridDhtLockRequest#nearKeys
[
https://issues.apache.org/jira/browse/IGNITE-22917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873615#comment-17873615
]
Anton Vinogradov edited comment on IGNITE-22917 at 8/16/24 11:52 AM:
-
It seems we've lost near cache tx support, but even before first version was
released.
Should we reimplement it or get rid of it?
was (Author: av):
It seem's we've lost near cache tx support, but even before first version was
released.
Should we reimplement it or get rid of it?
> Remove GridDhtLockRequest#nearKeys
> --
>
> Key: IGNITE-22917
> URL: https://issues.apache.org/jira/browse/IGNITE-22917
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{GridDhtLockRequest#addNearKey(KeyCacheObject)}} does not have any usage,
> i.e. {{GridDhtLockRequest#nearKeys}} is not updated at all.
> So, {{nearKeys}} always returns empty collection and, moreover, some code
> becomes useless, eg. {{GridNearTransactionalCache#startRemoteTx(UUID,
> GridDhtLockRequest)}} [1], etc.
> We have to figure out whether this is redundant code or whether we have
> *_lost some useful functionality_*.
> #
> https://github.com/apache/ignite/blob/f4654f98607648252c5164c0fd1a81eff279ca26/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTransactionalCache.java#L285
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22917) Remove GridDhtLockRequest#nearKeys
[
https://issues.apache.org/jira/browse/IGNITE-22917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873615#comment-17873615
]
Anton Vinogradov commented on IGNITE-22917:
---
It seem's we've lost near cache tx support, but even before first version was
released.
Should we reimplement it or get rid of it?
> Remove GridDhtLockRequest#nearKeys
> --
>
> Key: IGNITE-22917
> URL: https://issues.apache.org/jira/browse/IGNITE-22917
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{GridDhtLockRequest#addNearKey(KeyCacheObject)}} does not have any usage,
> i.e. {{GridDhtLockRequest#nearKeys}} is not updated at all.
> So, {{nearKeys}} always returns empty collection and, moreover, some code
> becomes useless, eg. {{GridNearTransactionalCache#startRemoteTx(UUID,
> GridDhtLockRequest)}} [1], etc.
> We have to figure out whether this is redundant code or whether we have
> *_lost some useful functionality_*.
> #
> https://github.com/apache/ignite/blob/f4654f98607648252c5164c0fd1a81eff279ca26/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/near/GridNearTransactionalCache.java#L285
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-22790) Initial cleanup of Grid*Request and Grid*Response classes
[
https://issues.apache.org/jira/browse/IGNITE-22790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871375#comment-17871375
]
Anton Vinogradov commented on IGNITE-22790:
---
Merged to the master.
[~shishkovilja], thanks for your contribution!
> Initial cleanup of Grid*Request and Grid*Response classes
> -
>
> Key: IGNITE-22790
> URL: https://issues.apache.org/jira/browse/IGNITE-22790
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Attachments: scope5.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Cleanup of Grid*Request and Grid*Response classes:
> 1) Descendants of {{{}GridDistributedBaseMessage{}}}:
> !scope5.png!
> 2) Descendants of {{GridCacheMessage}} and {{{}GridCacheIdMessage{}}}:
> * TxLocksRequest
> * TxLocksResponse
> * GridDhtTxFinishResponse
> ** GridNearTxFinishResponse
> ** GridDistributedTxFinishResponse
> * GridNearSingleGetRequest
> * GridNearSingleGetResponse
> * GridNearGetRequest
> * GridNearGetResponse
> * GridDhtTxOnePhaseCommitAckRequest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-22089) Removal of MVCC benchmarks in Yardstick
[ https://issues.apache.org/jira/browse/IGNITE-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-22089: -- Fix Version/s: 2.17 > Removal of MVCC benchmarks in Yardstick > --- > > Key: IGNITE-22089 > URL: https://issues.apache.org/jira/browse/IGNITE-22089 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > Fix For: 2.17 > > Attachments: IgniteGetAndPutTxBenchmark.png, > IgniteInvokeTxBenchmark.png, IgnitePutGetTxBenchmark.png, > IgnitePutTxBenchmark.png, JdbcSqlInsertDeleteBenchmark.png, > JdbcSqlQueryRangeBenchmark.png, JdbcSqlUpdateBenchmark.png > > Time Spent: 20m > Remaining Estimate: 0h > > MVCC code has to be removed from Yardstick. Classes to delete: > - AbstractDistributedMvccBenchmark > - MvccProcessorBenchmark > - MvccUpdateContentionBenchmark > - NativeJavaApiPutRemoveBenchmark -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-22343) Better Tx engine!
[ https://issues.apache.org/jira/browse/IGNITE-22343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-22343: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Better Tx engine! > - > > Key: IGNITE-22343 > URL: https://issues.apache.org/jira/browse/IGNITE-22343 > Project: Ignite > Issue Type: Epic >Reporter: Anton Vinogradov >Priority: Major > > It's time to cleanup, refactor and requild TX engine! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19844) Tx code cleanup
[ https://issues.apache.org/jira/browse/IGNITE-19844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-19844: -- Summary: Tx code cleanup (was: TX code cleanup) > Tx code cleanup > --- > > Key: IGNITE-19844 > URL: https://issues.apache.org/jira/browse/IGNITE-19844 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Attachments: scope.png, scope2.png, scope3.png, scope4.png > > > It's an umbrella issue to keep all cleanup issues. > Scope: > #1 > !scope.png|width=800! > #2 > !scope2.png|width=800! > #3 > !scope3.png|width=800! > #4 > !scope4.png|width=800! > TODO #5 - Grid*Requests and Grid*Responses (like GridNearLockRequest) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22343) Better Tx engine!
Anton Vinogradov created IGNITE-22343: - Summary: Better Tx engine! Key: IGNITE-22343 URL: https://issues.apache.org/jira/browse/IGNITE-22343 Project: Ignite Issue Type: Epic Reporter: Anton Vinogradov It's time to cleanup, refactor and requild TX engine! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-22344) Tx counters refactoring
Anton Vinogradov created IGNITE-22344: - Summary: Tx counters refactoring Key: IGNITE-22344 URL: https://issues.apache.org/jira/browse/IGNITE-22344 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Tx counters (atomic and tx) must be simplified if possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19844) TX code cleanup
[ https://issues.apache.org/jira/browse/IGNITE-19844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-19844: -- Epic Link: IGNITE-22343 > TX code cleanup > --- > > Key: IGNITE-19844 > URL: https://issues.apache.org/jira/browse/IGNITE-19844 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Attachments: scope.png, scope2.png, scope3.png, scope4.png > > > It's an umbrella issue to keep all cleanup issues. > Scope: > #1 > !scope.png|width=800! > #2 > !scope2.png|width=800! > #3 > !scope3.png|width=800! > #4 > !scope4.png|width=800! > TODO #5 - Grid*Requests and Grid*Responses (like GridNearLockRequest) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13114) Off-by-one error in GridPortProcessor port number assertion
[ https://issues.apache.org/jira/browse/IGNITE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834394#comment-17834394 ] Anton Vinogradov commented on IGNITE-13114: --- And you got your answer each time you mentioned someone ;) > Off-by-one error in GridPortProcessor port number assertion > --- > > Key: IGNITE-13114 > URL: https://issues.apache.org/jira/browse/IGNITE-13114 > Project: Ignite > Issue Type: Bug >Reporter: Chris Dennis >Priority: Minor > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > GridPortProcessor asserts that the provided port number is `> 0` and `< > 65535`. This upper bounds check should be `<= 65535`. Since this is a Java > language assert it's likely to never be tripped in any production system, but > could be seen when using Ignite in a testing environment that turns on these > assertions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-13114) Off-by-one error in GridPortProcessor port number assertion
[ https://issues.apache.org/jira/browse/IGNITE-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834354#comment-17834354 ] Anton Vinogradov commented on IGNITE-13114: --- [~chrisdennis], sure, don't forget to mention someone nextime to be seen :) > Off-by-one error in GridPortProcessor port number assertion > --- > > Key: IGNITE-13114 > URL: https://issues.apache.org/jira/browse/IGNITE-13114 > Project: Ignite > Issue Type: Bug >Reporter: Chris Dennis >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > GridPortProcessor asserts that the provided port number is `> 0` and `< > 65535`. This upper bounds check should be `<= 65535`. Since this is a Java > language assert it's likely to never be tripped in any production system, but > could be seen when using Ignite in a testing environment that turns on these > assertions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21145) Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.*
[ https://issues.apache.org/jira/browse/IGNITE-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21145: -- Fix Version/s: 2.17 > Remove MVCC classes from package o.a.i.internal.processors.cache.tree.mvcc.* > > > Key: IGNITE-21145 > URL: https://issues.apache.org/jira/browse/IGNITE-21145 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 40m > Remaining Estimate: 0h > > Delete all classes from: > 1) org/apache/ignite/internal/processors/cache/tree/mvcc/data > * MvccCacheIdAwareDataInnerIO > * MvccCacheIdAwareDataLeafIO > * MvccDataInnerIO > * MvccDataLeafIO > * MvccDataRow > * MvccUpdateDataRow > * MvccUpdateResult > * ResultType > 2) org/apache/ignite/internal/processors/cache/tree/mvcc/search > * MvccDataPageClosure > * MvccFirstRowTreeClosure > * MvccLinkAwareSearchRow > * MvccMaxSearchRow > * MvccMinSearchRow > * MvccSearchRow > * MvccSnapshotSearchRow > * MvccTreeClosure -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21628) Transactional SQL commands removal
[
https://issues.apache.org/jira/browse/IGNITE-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-21628:
--
Fix Version/s: 2.17
> Transactional SQL commands removal
> --
>
> Key: IGNITE-21628
> URL: https://issues.apache.org/jira/browse/IGNITE-21628
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SQL commands should be removed:
> * {{BEGIN [TRANSACTION]}} -> {{SqlBeginTransactionCommand}}
> * {{COMMIT [TRANSACTION]}} -> {{SqlCommitTransactionCommand}}
> * {{ROLLBACK [TRANSACTION]}} -> {{SqlRollbackTransactionCommand}}
> * {{SELECT FOR UPDATE}}
> * etc.
> All corresponding parsing code should be removed too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21367) IgniteH2Indexing transactional code removal
[ https://issues.apache.org/jira/browse/IGNITE-21367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21367: -- Fix Version/s: 2.17 > IgniteH2Indexing transactional code removal > --- > > Key: IGNITE-21367 > URL: https://issues.apache.org/jira/browse/IGNITE-21367 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21346) Removal of MVCC code from GridCacheEntryEx and IgniteCacheOffheapManager
[ https://issues.apache.org/jira/browse/IGNITE-21346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21346: -- Fix Version/s: 2.17 > Removal of MVCC code from GridCacheEntryEx and IgniteCacheOffheapManager > > > Key: IGNITE-21346 > URL: https://issues.apache.org/jira/browse/IGNITE-21346 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Remove all MVCC code from GridCacheEntryEx and IgniteCacheOffheapManager and > their succesors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21436) Removal of MVCC *Enlist* classes
[ https://issues.apache.org/jira/browse/IGNITE-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21436: -- Fix Version/s: 2.17 > Removal of MVCC *Enlist* classes > > > Key: IGNITE-21436 > URL: https://issues.apache.org/jira/browse/IGNITE-21436 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Classes to remove: > *DHT:* > * GridDhtTxAbstractEnlistFuture > * GridDhtTxEnlistFuture > * GridDhtTxQueryAbstractEnlistFuture > * GridDhtTxQueryEnlistFuture > * GridDhtTxQueryEnlistRequest > * GridDhtTxQueryEnlistResponse > * GridDhtTxQueryFirstEnlistRequest > * GridDhtTxQueryResultsEnlistFuture > *Near:* > * GridNearTxAbstractEnlistFuture > * GridNearTxEnlistFuture > * GridNearTxEnlistRequest > * GridNearTxEnlistResponse > * GridNearTxFinishAndAckFuture > * GridNearTxQueryAbstractEnlistFuture > * GridNearTxQueryEnlistFuture > * GridNearTxQueryEnlistRequest > * GridNearTxQueryEnlistResponse > * GridNearTxQueryResultsEnlistFuture > * GridNearTxQueryResultsEnlistRequest > * GridNearTxQueryResultsEnlistResponse > All corresponding code have to be removed too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21368) MVCC code removal from transactional classes
[
https://issues.apache.org/jira/browse/IGNITE-21368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-21368:
--
Fix Version/s: 2.17
> MVCC code removal from transactional classes
>
>
> Key: IGNITE-21368
> URL: https://issues.apache.org/jira/browse/IGNITE-21368
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> MVCC code have to be removed from {{IgniteInternalTx}} and successors.
> Affected classes are {{GridNearTxLocal}}, {{IgniteTxAdapter}},
> {{IgniteTxLocalAdapter}}, etc. and corresponding code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-8801) Change default behaviour of atomic operations inside transactions
[
https://issues.apache.org/jira/browse/IGNITE-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811868#comment-17811868
]
Anton Vinogradov commented on IGNITE-8801:
--
[~scottmf]
> what is the implication of making a cache TRANSACTIONAL as opposed to ATOMIC?
> IOW, why can't all caches be TRANSACTIONAL?
Simple answer is "tx caches are much slower than atomic" and should be used
only when special (distributed tx) guaranties are required.
> Change default behaviour of atomic operations inside transactions
> -
>
> Key: IGNITE-8801
> URL: https://issues.apache.org/jira/browse/IGNITE-8801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ryabov Dmitrii
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise
> Fix For: 2.15
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Need to change default behaviour of atomic operations to fail inside
> transactions.
> 1) Remove IGNITE_ALLOW_ATOMIC_OPS_IN_TX system property.
> 2) Set default value to restrict atomic operations in
> {{CacheOperationContext}} constructor without arguments and arguments for
> calls of another constructor.
> 3) Fix javadocs.
> As per the latest round of discussion on Ignite Dev List as of 28/10/2022 we
> agreed on the following:
> 1) Revert deprecation IGNITE-17916 - reverted
> 2) Change default value in 2.15.
> 3) Notify users in release notes, an exception message - how to change the
> behavior back.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21130) TxLog removal
[
https://issues.apache.org/jira/browse/IGNITE-21130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-21130:
--
Fix Version/s: 2.17
> TxLog removal
> -
>
> Key: IGNITE-21130
> URL: https://issues.apache.org/jira/browse/IGNITE-21130
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Ilya Shishkov
>Assignee: Ilya Shishkov
>Priority: Minor
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Remove TxLog region [1, TxLog] and all corresponding data structures and
> code, such as classes from {{o.a.i.internal.processors.cache.mvcc.txlog.*}}
> package (except for {{TxState}}, see IGNITE-21345).
> #
> https://cwiki.apache.org/confluence/display/IGNITE/Distributed+MVCC+And+Transactional+SQL+Design
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21151) MVCC caching removal
[ https://issues.apache.org/jira/browse/IGNITE-21151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21151: -- Fix Version/s: 2.17 > MVCC caching removal > > > Key: IGNITE-21151 > URL: https://issues.apache.org/jira/browse/IGNITE-21151 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Remove MvccCachingManager and corresponding code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-21165) .NET platform test timeouts after ClientServerCompatibilityTest
[
https://issues.apache.org/jira/browse/IGNITE-21165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-21165:
-
Assignee: Vladimir Steshin
> .NET platform test timeouts after ClientServerCompatibilityTest
> ---
>
> Key: IGNITE-21165
> URL: https://issues.apache.org/jira/browse/IGNITE-21165
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Attachments:
> Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Core_Linux_39429.log.zip
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There are many timeouted test runs in the .NET suite. Example:
> https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetCoreLinux/7678070
> {code:java}
> The build Ignite Tests 2.x (JDK 8/11)::Platform .NET (Core Linux) #39429
> {buildId=7678070} has been running for more than 40 minutes. Terminating...
> {code}
> Looks like only port 47500 is requested while server node started on another.
> Probably a previous test didn't release the port yet.
> {code:java}
> Successfully bound communication NIO server to TCP port [port=47101,
> locHost=/127.0.0.1, selectorsCnt=4, selectorSpins=0, pairedConn=false]
> {code}
> {code:java}
> Failed to connect to any address from IP finder (make sure IP finder
> addresses are correct and firewalls are disabled on all host machines):
> [/127.0.0.1:47500]
> {code}
> It looks like this issue happens on JDK8 only. And only on Linux.
> _ClientServerCompatibilityTest_ starts a server node with _Runner.java_,
> _PlatformProcessUtils#startProcess()_ and stops with
> _PlatformProcessUtils#destriyProcess()_. On Windows, additional
> {code:java}
> serverProc.KillProcessTree();
> {code}
> is applied.
> We should wait until _java.lang.Process_ completely stops.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21165) .NET platform test timeouts after ClientServerCompatibilityTest
[
https://issues.apache.org/jira/browse/IGNITE-21165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-21165:
--
Fix Version/s: 2.17
> .NET platform test timeouts after ClientServerCompatibilityTest
> ---
>
> Key: IGNITE-21165
> URL: https://issues.apache.org/jira/browse/IGNITE-21165
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Attachments:
> Ignite_Tests_2.x_JDK_8_11_Platform_.NET_Core_Linux_39429.log.zip
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> There are many timeouted test runs in the .NET suite. Example:
> https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformNetCoreLinux/7678070
> {code:java}
> The build Ignite Tests 2.x (JDK 8/11)::Platform .NET (Core Linux) #39429
> {buildId=7678070} has been running for more than 40 minutes. Terminating...
> {code}
> Looks like only port 47500 is requested while server node started on another.
> Probably a previous test didn't release the port yet.
> {code:java}
> Successfully bound communication NIO server to TCP port [port=47101,
> locHost=/127.0.0.1, selectorsCnt=4, selectorSpins=0, pairedConn=false]
> {code}
> {code:java}
> Failed to connect to any address from IP finder (make sure IP finder
> addresses are correct and firewalls are disabled on all host machines):
> [/127.0.0.1:47500]
> {code}
> It looks like this issue happens on JDK8 only. And only on Linux.
> _ClientServerCompatibilityTest_ starts a server node with _Runner.java_,
> _PlatformProcessUtils#startProcess()_ and stops with
> _PlatformProcessUtils#destriyProcess()_. On Windows, additional
> {code:java}
> serverProc.KillProcessTree();
> {code}
> is applied.
> We should wait until _java.lang.Process_ completely stops.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-21093) MvccMessage removal
[ https://issues.apache.org/jira/browse/IGNITE-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21093: -- Fix Version/s: 2.17 > MvccMessage removal > --- > > Key: IGNITE-21093 > URL: https://issues.apache.org/jira/browse/IGNITE-21093 > Project: Ignite > Issue Type: Sub-task >Reporter: Julia Bakulina >Assignee: Julia Bakulina >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 50m > Remaining Estimate: 0h > > Remove MvccMessage > All classes in > modules/core/src/main/java/org/apache/ignite/internal/processors/cache/mvcc/msg > are deleted: > * MvccAckRequestQueryId > * MvccAckRequestQueryCntr > * MvccAckRequestTxAndQueryCntr > * MvccAckRequestTxAndQueryId > * MvccActiveQueriesMessage > * MvccFutureResponse > * MvccMessage > * MvccQuerySnapshotRequest > * MvccRecoveryFinishedMessage > * MvccAckRequestTx > * MvccSnapshotResponse > * MvccSnapshotRequest -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21141) MvccProcessor removal
[ https://issues.apache.org/jira/browse/IGNITE-21141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-21141: -- Fix Version/s: 2.17 > MvccProcessor removal > - > > Key: IGNITE-21141 > URL: https://issues.apache.org/jira/browse/IGNITE-21141 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Ilya Shishkov >Assignee: Ilya Shishkov >Priority: Minor > Labels: ise > Fix For: 2.17 > > Time Spent: 50m > Remaining Estimate: 0h > > Remove MvccProcessor class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
[ https://issues.apache.org/jira/browse/IGNITE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20913: -- Description: Just allowing CacheVersionConflictResolver to resolve -more- complex cases. Main goal is to allow any changes from other cluster when both clusters are synchronized (have the same value/version). was:Just allowing CacheVersionConflictResolver to resolve -more- complex cases. > Previous value, version, their combination or parts should be written as a > part of the DataEntry to allow CacheVersionConflictResolver use them on > resolve > -- > > Key: IGNITE-20913 > URL: https://issues.apache.org/jira/browse/IGNITE-20913 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.17 > > Time Spent: 10m > Remaining Estimate: 0h > > Just allowing CacheVersionConflictResolver to resolve -more- complex cases. > Main goal is to allow any changes from other cluster when both clusters are > synchronized (have the same value/version). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal
[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795678#comment-17795678 ] Anton Vinogradov commented on IGNITE-20506: --- [~liyuj], This Issue is already closed at 2.16. If we need to change something, let's create new linked issue. > CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal > - > > Key: IGNITE-20506 > URL: https://issues.apache.org/jira/browse/IGNITE-20506 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: YuJue Li >Priority: Major > Labels: important > Fix For: 2.16 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20945) Fix scala compilation by IDEA
[
https://issues.apache.org/jira/browse/IGNITE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-20945:
--
Ignite Flags: (was: Docs Required,Release Notes Required)
> Fix scala compilation by IDEA
> -
>
> Key: IGNITE-20945
> URL: https://issues.apache.org/jira/browse/IGNITE-20945
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
>
> Dependency update causes {{Cannot find project Scala library 2.12.16 for
> module}} and compilation fails on scala.
> The solution foud here at
> https://stackoverflow.com/questions/72687014/karate-gatlingcannot-find-project-scala-library-2-12-8-for-module
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-20945) Fix scala compilation by IDEA
[
https://issues.apache.org/jira/browse/IGNITE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov resolved IGNITE-20945.
---
Resolution: Fixed
> Fix scala compilation by IDEA
> -
>
> Key: IGNITE-20945
> URL: https://issues.apache.org/jira/browse/IGNITE-20945
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
>
> Dependency update causes {{Cannot find project Scala library 2.12.16 for
> module}} and compilation fails on scala.
> The solution foud here at
> https://stackoverflow.com/questions/72687014/karate-gatlingcannot-find-project-scala-library-2-12-8-for-module
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-20945) Fix scala compilation by IDEA
[
https://issues.apache.org/jira/browse/IGNITE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789110#comment-17789110
]
Anton Vinogradov commented on IGNITE-20945:
---
Checked TC compilation
https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_RunAllTests/7627102?buildTab=dependencies&type=snapshot&mode=timeline&range=1700740457000-1700742906000
Merged to the master.
> Fix scala compilation by IDEA
> -
>
> Key: IGNITE-20945
> URL: https://issues.apache.org/jira/browse/IGNITE-20945
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
>
> Dependency update causes {{Cannot find project Scala library 2.12.16 for
> module}} and compilation fails on scala.
> The solution foud here at
> https://stackoverflow.com/questions/72687014/karate-gatlingcannot-find-project-scala-library-2-12-8-for-module
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-20945) Fix scala compilation by IDEA
Anton Vinogradov created IGNITE-20945:
-
Summary: Fix scala compilation by IDEA
Key: IGNITE-20945
URL: https://issues.apache.org/jira/browse/IGNITE-20945
Project: Ignite
Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
Dependency update causes {{Cannot find project Scala library 2.12.16 for
module}} and compilation fails on scala.
The solution foud here at
https://stackoverflow.com/questions/72687014/karate-gatlingcannot-find-project-scala-library-2-12-8-for-module
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
[ https://issues.apache.org/jira/browse/IGNITE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20913: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Previous value, version, their combination or parts should be written as a > part of the DataEntry to allow CacheVersionConflictResolver use them on > resolve > -- > > Key: IGNITE-20913 > URL: https://issues.apache.org/jira/browse/IGNITE-20913 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.17 > > > Just allowing CacheVersionConflictResolver to resolve -more- complex cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
[ https://issues.apache.org/jira/browse/IGNITE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20913: -- Fix Version/s: 2.17 > Previous value, version, their combination or parts should be written as a > part of the DataEntry to allow CacheVersionConflictResolver use them on > resolve > -- > > Key: IGNITE-20913 > URL: https://issues.apache.org/jira/browse/IGNITE-20913 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.17 > > > Just allowing CacheVersionConflictResolver to resolve -more- complex cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
Anton Vinogradov created IGNITE-20913: - Summary: Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve Key: IGNITE-20913 URL: https://issues.apache.org/jira/browse/IGNITE-20913 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
[ https://issues.apache.org/jira/browse/IGNITE-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20913: -- Description: Just allowing CacheVersionConflictResolver to resolve -more- complex cases. > Previous value, version, their combination or parts should be written as a > part of the DataEntry to allow CacheVersionConflictResolver use them on > resolve > -- > > Key: IGNITE-20913 > URL: https://issues.apache.org/jira/browse/IGNITE-20913 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > Just allowing CacheVersionConflictResolver to resolve -more- complex cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[
https://issues.apache.org/jira/browse/IGNITE-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788363#comment-17788363
]
Anton Vinogradov commented on IGNITE-20816:
---
Cherry-picked to the 2.16 as well.
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
> Fix For: 2.16
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:424)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1903)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2536)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1996)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1688)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:791)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:645)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1080)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:752)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1078)
> [classes/:?]
>
[jira] [Updated] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[
https://issues.apache.org/jira/browse/IGNITE-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-20816:
--
Fix Version/s: 2.16
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
> Fix For: 2.16, 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:424)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1903)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2536)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1996)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1688)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:791)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:645)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1080)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:752)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.dist
[jira] [Updated] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[
https://issues.apache.org/jira/browse/IGNITE-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-20816:
--
Fix Version/s: 2.17
(was: 2.16)
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
> Fix For: 2.17
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:424)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1903)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2536)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1996)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1688)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:791)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:645)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1080)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:752)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.i
[jira] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[ https://issues.apache.org/jira/browse/IGNITE-20816 ]
Anton Vinogradov deleted comment on IGNITE-20816:
---
was (Author: ignitetcbot):
{panel:title=Branch: [pull/11037/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11037/head] Base: [master] : New Tests
(40)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 13{color} [[tests
40|https://ci2.ignite.apache.org/viewLog.html?buildId=7607851]]
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testClientCachePut[mode=TRANSACTIONAL,
persistence=true, gen=INT] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testCachePut[mode=TRANSACTIONAL,
persistence=true, gen=STR] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testClientCachePut[mode=TRANSACTIONAL,
persistence=true, gen=OBJ] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testCachePut[mode=TRANSACTIONAL,
persistence=true, gen=OBJ] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testClientCachePut[mode=TRANSACTIONAL,
persistence=true, gen=ARR_OBJ] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testCachePut[mode=TRANSACTIONAL,
persistence=true, gen=INT] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testClientCachePut[mode=TRANSACTIONAL,
persistence=true, gen=ARR] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testCachePut[mode=TRANSACTIONAL,
persistence=true, gen=ARR] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testClientCachePut[mode=TRANSACTIONAL,
persistence=true, gen=STR] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testCachePut[mode=TRANSACTIONAL,
persistence=false, gen=ARR] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite13:
CacheObjectTransformationCacheApiTest.testClientCachePut[mode=TRANSACTIONAL,
persistence=false, gen=STR] - PASSED{color}
... and 29 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7607949&buildTypeId=IgniteTests24Java8_RunAll]
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(Igni
[jira] [Updated] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[
https://issues.apache.org/jira/browse/IGNITE-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-20816:
--
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:424)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1903)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2536)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1996)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1688)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:791)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:645)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1080)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:752)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1078)
> [classes/:?]
>
[jira] [Updated] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[
https://issues.apache.org/jira/browse/IGNITE-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-20816:
--
Fix Version/s: 2.16
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:424)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1903)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2536)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1996)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1688)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:791)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:645)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1080)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:752)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distribute
[jira] [Commented] (IGNITE-20810) Fix duplicate documentation for Ignite extensions
[ https://issues.apache.org/jira/browse/IGNITE-20810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784723#comment-17784723 ] Anton Vinogradov commented on IGNITE-20810: --- [~igusev], Could you please fix the site to use the documentation from ignite repository while this issue is not implemented? > Fix duplicate documentation for Ignite extensions > - > > Key: IGNITE-20810 > URL: https://issues.apache.org/jira/browse/IGNITE-20810 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Priority: Major > > Some time ago we created a separate documentation for Ignite extensions in > the extensions repository: > [https://github.com/apache/ignite-extensions] > It is also published, but without links from main doc > [https://ignite.apache.org/docs/extensions/aws/aws] > This currently conflicts with extensions documentation still in the main repo: > [https://ignite.apache.org/docs/latest/extensions-and-integrations/spring/spring-boot] > [https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations] > We need to make sure there is only one documentation for extensions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-20816) in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache objects transformation applied
[
https://issues.apache.org/jira/browse/IGNITE-20816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-20816:
-
Assignee: Anton Vinogradov
> in-memory server node is crashed by TcpIgniteClient.putAllConflict() if cache
> objects transformation applied
>
>
> Key: IGNITE-20816
> URL: https://issues.apache.org/jira/browse/IGNITE-20816
> Project: Ignite
> Issue Type: Task
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
>
> The in-memory server node crashes with the below exception if
> TcpIgniteClient.putAllConflict() if cache objects transformation is applied.
> {noformat}
> [2023-11-09T09:34:30,401][ERROR][client-connector-#68%target%][] 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=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [groupId=-1407396309, pageIds=[844420635164695], msg=Runtime
> failure on search row: SearchRow [key=KeyCacheObjectImpl [part=10, val=52234,
> hasValBytes=true], hash=52234, cacheId=0
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [groupId=-1407396309, pageIds=[844420635164695],
> msg=Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl
> [part=10, val=52234, hasValBytes=true], hash=52234, cacheId=0]]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6534)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:2215)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1692)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1675)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:424)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1903)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2536)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1996)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1688)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:791)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:645)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1080)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$21.apply(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:752)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAll0(GridDhtAtomicCache.java:1078)
> [classes/:?]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAllConflictAsync(GridDhtAtomicCach
[jira] [Updated] (IGNITE-20804) Support custom conflict resolver at CDC based datacenter replication
[ https://issues.apache.org/jira/browse/IGNITE-20804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20804: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Support custom conflict resolver at CDC based datacenter replication > > > Key: IGNITE-20804 > URL: https://issues.apache.org/jira/browse/IGNITE-20804 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Choosing the right conflict resolution strategy depends on your specific use > case and requires a good understanding of your data and its usage. You should > consider the nature of your transactions, the rate of change of your data, > and the implications of potential data loss or overwrites when selecting a > conflict resolution strategy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20804) Support custom conflict resolver at CDC based datacenter replication
[ https://issues.apache.org/jira/browse/IGNITE-20804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20804: -- Fix Version/s: 2.17 > Support custom conflict resolver at CDC based datacenter replication > > > Key: IGNITE-20804 > URL: https://issues.apache.org/jira/browse/IGNITE-20804 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.17 > > Time Spent: 20m > Remaining Estimate: 0h > > Choosing the right conflict resolution strategy depends on your specific use > case and requires a good understanding of your data and its usage. You should > consider the nature of your transactions, the rate of change of your data, > and the implications of potential data loss or overwrites when selecting a > conflict resolution strategy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20804) Support custom conflict resolver at CDC based datacenter replication
Anton Vinogradov created IGNITE-20804: - Summary: Support custom conflict resolver at CDC based datacenter replication Key: IGNITE-20804 URL: https://issues.apache.org/jira/browse/IGNITE-20804 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Choosing the right conflict resolution strategy depends on your specific use case and requires a good understanding of your data and its usage. You should consider the nature of your transactions, the rate of change of your data, and the implications of potential data loss or overwrites when selecting a conflict resolution strategy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-20744) StandaloneContext should not load plugins from classpath
[ https://issues.apache.org/jira/browse/IGNITE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780923#comment-17780923 ] Anton Vinogradov commented on IGNITE-20744: --- Merged to the master [~NIzhikov], thanks for the review! > StandaloneContext should not load plugins from classpath > > > Key: IGNITE-20744 > URL: https://issues.apache.org/jira/browse/IGNITE-20744 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > Only explicitly specified plugins should be loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20744) StandaloneContext should not load plugins from classpath
[ https://issues.apache.org/jira/browse/IGNITE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20744: -- Description: Only explicitly specified plugins should be loaded. (was: Only explicitely specified plugins should be loaded.) > StandaloneContext should not load plugins from classpath > > > Key: IGNITE-20744 > URL: https://issues.apache.org/jira/browse/IGNITE-20744 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 10m > Remaining Estimate: 0h > > Only explicitly specified plugins should be loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20746) Cache objects transformation never happen on TcpIgniteClient.putAllConflict()
[ https://issues.apache.org/jira/browse/IGNITE-20746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20746: -- Fix Version/s: 2.16 > Cache objects transformation never happen on TcpIgniteClient.putAllConflict() > - > > Key: IGNITE-20746 > URL: https://issues.apache.org/jira/browse/IGNITE-20746 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-97 > Fix For: 2.16 > > > Happens on TcpIgniteClient.put() but not TcpIgniteClient.putAllConflict() -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20744) StandaloneContext should not load plugins from classpath
[ https://issues.apache.org/jira/browse/IGNITE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20744: -- Ignite Flags: (was: Docs Required,Release Notes Required) > StandaloneContext should not load plugins from classpath > > > Key: IGNITE-20744 > URL: https://issues.apache.org/jira/browse/IGNITE-20744 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Only explicitely specified plugins should be loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20744) StandaloneContext should not load plugins from classpath
[ https://issues.apache.org/jira/browse/IGNITE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20744: -- Fix Version/s: 2.16 > StandaloneContext should not load plugins from classpath > > > Key: IGNITE-20744 > URL: https://issues.apache.org/jira/browse/IGNITE-20744 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 10m > Remaining Estimate: 0h > > Only explicitely specified plugins should be loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20746) Cache objects transformation never happen on TcpIgniteClient.putAllConflict()
Anton Vinogradov created IGNITE-20746: - Summary: Cache objects transformation never happen on TcpIgniteClient.putAllConflict() Key: IGNITE-20746 URL: https://issues.apache.org/jira/browse/IGNITE-20746 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Happens on TcpIgniteClient.put() but not TcpIgniteClient.putAllConflict() -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20746) Cache objects transformation never happen on TcpIgniteClient.putAllConflict()
[ https://issues.apache.org/jira/browse/IGNITE-20746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20746: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Cache objects transformation never happen on TcpIgniteClient.putAllConflict() > - > > Key: IGNITE-20746 > URL: https://issues.apache.org/jira/browse/IGNITE-20746 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-97 > > Happens on TcpIgniteClient.put() but not TcpIgniteClient.putAllConflict() -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20746) Cache objects transformation never happen on TcpIgniteClient.putAllConflict()
[ https://issues.apache.org/jira/browse/IGNITE-20746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20746: -- Labels: iep-97 (was: ) > Cache objects transformation never happen on TcpIgniteClient.putAllConflict() > - > > Key: IGNITE-20746 > URL: https://issues.apache.org/jira/browse/IGNITE-20746 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: iep-97 > > Happens on TcpIgniteClient.put() but not TcpIgniteClient.putAllConflict() -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20744) StandaloneContext should not load plugins from classpath
Anton Vinogradov created IGNITE-20744: - Summary: StandaloneContext should not load plugins from classpath Key: IGNITE-20744 URL: https://issues.apache.org/jira/browse/IGNITE-20744 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Only explicitely specified plugins should be loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
[ https://issues.apache.org/jira/browse/IGNITE-20575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20575: -- Release Note: Mixed atomicity cache groups now restricted, but IGNITE_ALLOW_MIXED_CACHE_GROUPS system option may temporary allow them. (was: Mixed atomicity cache groups now restricted, but IGNITE_ALLOW_MIXED_CACHE_GROUPS system option may temporary allow it.) > Forbid mixed cache groups with both atomic and transactional caches (with > system property able to allow) > > > Key: IGNITE-20575 > URL: https://issues.apache.org/jira/browse/IGNITE-20575 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: ise > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
[ https://issues.apache.org/jira/browse/IGNITE-20575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20575: -- Release Note: Mixed atomicity cache groups now restricted, but IGNITE_ALLOW_MIXED_CACHE_GROUPS system option may temporary allow it. > Forbid mixed cache groups with both atomic and transactional caches (with > system property able to allow) > > > Key: IGNITE-20575 > URL: https://issues.apache.org/jira/browse/IGNITE-20575 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: ise > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-12622: -- Description: Apparently it's possible in Ignite to configure a cache group with both ATOMIC and TRANSACTIONAL caches. IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. As per discussed on dev list (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), the community has concluded that such configurations should be prohibited. Forbidden at IGNITE-20575 IGNITE-20623 should be fixed prior this fix. was: Apparently it's possible in Ignite to configure a cache group with both ATOMIC and TRANSACTIONAL caches. IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. As per discussed on dev list (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), the community has concluded that such configurations should be prohibited. Forbidden at IGNITE-20575 > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Ivan Rakov >Priority: Major > Labels: IEP-80, newbie > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. > Forbidden at IGNITE-20575 > IGNITE-20623 should be fixed prior this fix. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12622) Forbid mixed cache groups with both atomic and transactional caches
[ https://issues.apache.org/jira/browse/IGNITE-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-12622: -- Description: Apparently it's possible in Ignite to configure a cache group with both ATOMIC and TRANSACTIONAL caches. IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. As per discussed on dev list (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), the community has concluded that such configurations should be prohibited. Forbidden at IGNITE-20575 was: Apparently it's possible in Ignite to configure a cache group with both ATOMIC and TRANSACTIONAL caches. IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. As per discussed on dev list (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), the community has concluded that such configurations should be prohibited. > Forbid mixed cache groups with both atomic and transactional caches > --- > > Key: IGNITE-12622 > URL: https://issues.apache.org/jira/browse/IGNITE-12622 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Ivan Rakov >Priority: Major > Labels: IEP-80, newbie > > Apparently it's possible in Ignite to configure a cache group with both > ATOMIC and TRANSACTIONAL caches. > IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests. > As per discussed on dev list > (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), > the community has concluded that such configurations should be prohibited. > Forbidden at IGNITE-20575 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
[ https://issues.apache.org/jira/browse/IGNITE-20575 ]
Anton Vinogradov deleted comment on IGNITE-20575:
---
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10976/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10976/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=7372964&buildTypeId=IgniteTests24Java8_RunAll]
> Forbid mixed cache groups with both atomic and transactional caches (with
> system property able to allow)
>
>
> Key: IGNITE-20575
> URL: https://issues.apache.org/jira/browse/IGNITE-20575
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20623) Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc)
[ https://issues.apache.org/jira/browse/IGNITE-20623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20623: -- Description: Currently, creating ds with Atomic atomicity, we also creating Transactional meta cache inside the same cache group when it's specified. This causes mixed atomicity inside the cache group. As a result, we unable to use proper counters (finally restrict mixed groups). was: Currently, creating ds with Atomic atomicity, we also creating Transactional meta cache inside the same cache group when it's specified. This causes mixed atomicity inside the cache group. As a result, we unable to use proper counters. > Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc) > > > Key: IGNITE-20623 > URL: https://issues.apache.org/jira/browse/IGNITE-20623 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Priority: Major > > Currently, creating ds with Atomic atomicity, we also creating Transactional > meta cache inside the same cache group when it's specified. > This causes mixed atomicity inside the cache group. > As a result, we unable to use proper counters (finally restrict mixed groups). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20623) Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc)
[ https://issues.apache.org/jira/browse/IGNITE-20623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20623: -- Description: Currently, creating ds with Atomic atomicity, we also creating Transactional meta cache inside the same cache group when it's specified. This causes mixed atomicity inside the cache group. As a result, we unable to use proper counters. > Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc) > > > Key: IGNITE-20623 > URL: https://issues.apache.org/jira/browse/IGNITE-20623 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Priority: Major > > Currently, creating ds with Atomic atomicity, we also creating Transactional > meta cache inside the same cache group when it's specified. > This causes mixed atomicity inside the cache group. > As a result, we unable to use proper counters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20623) Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc)
Anton Vinogradov created IGNITE-20623: - Summary: Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc) Key: IGNITE-20623 URL: https://issues.apache.org/jira/browse/IGNITE-20623 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
[ https://issues.apache.org/jira/browse/IGNITE-20575 ]
Anton Vinogradov deleted comment on IGNITE-20575:
---
was (Author: ignitetcbot):
{panel:title=Branch: [pull/10976/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10976/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=7371590&buildTypeId=IgniteTests24Java8_RunAll]
> Forbid mixed cache groups with both atomic and transactional caches (with
> system property able to allow)
>
>
> Key: IGNITE-20575
> URL: https://issues.apache.org/jira/browse/IGNITE-20575
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20579) Finally restrict atomic operations inside the transaction (remove the system property)
[ https://issues.apache.org/jira/browse/IGNITE-20579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20579: -- Labels: ise (was: ) > Finally restrict atomic operations inside the transaction (remove the system > property) > -- > > Key: IGNITE-20579 > URL: https://issues.apache.org/jira/browse/IGNITE-20579 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: ise > Fix For: 2.16 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
[ https://issues.apache.org/jira/browse/IGNITE-20575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20575: -- Labels: ise (was: ) > Forbid mixed cache groups with both atomic and transactional caches (with > system property able to allow) > > > Key: IGNITE-20575 > URL: https://issues.apache.org/jira/browse/IGNITE-20575 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Labels: ise > Fix For: 2.16 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20579) Finally restrict atomic operations inside the transaction (remove the system property)
Anton Vinogradov created IGNITE-20579: - Summary: Finally restrict atomic operations inside the transaction (remove the system property) Key: IGNITE-20579 URL: https://issues.apache.org/jira/browse/IGNITE-20579 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20579) Finally restrict atomic operations inside the transaction (remove the system property)
[ https://issues.apache.org/jira/browse/IGNITE-20579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20579: -- Fix Version/s: 2.16 > Finally restrict atomic operations inside the transaction (remove the system > property) > -- > > Key: IGNITE-20579 > URL: https://issues.apache.org/jira/browse/IGNITE-20579 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20579) Finally restrict atomic operations inside the transaction (remove the system property)
[ https://issues.apache.org/jira/browse/IGNITE-20579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20579: -- Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Finally restrict atomic operations inside the transaction (remove the system > property) > -- > > Key: IGNITE-20579 > URL: https://issues.apache.org/jira/browse/IGNITE-20579 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
[ https://issues.apache.org/jira/browse/IGNITE-20575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20575: -- Fix Version/s: 2.16 > Forbid mixed cache groups with both atomic and transactional caches (with > system property able to allow) > > > Key: IGNITE-20575 > URL: https://issues.apache.org/jira/browse/IGNITE-20575 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20575) Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)
Anton Vinogradov created IGNITE-20575: - Summary: Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow) Key: IGNITE-20575 URL: https://issues.apache.org/jira/browse/IGNITE-20575 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal
[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-20506. --- Resolution: Fixed Merged to the master. [~NSAmelchev], thanks for the review! > CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal > - > > Key: IGNITE-20506 > URL: https://issues.apache.org/jira/browse/IGNITE-20506 > 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] [Created] (IGNITE-20566) CDC doesn't replicate complex objects when keepBinary is set to the false
Anton Vinogradov created IGNITE-20566:
-
Summary: CDC doesn't replicate complex objects when keepBinary is
set to the false
Key: IGNITE-20566
URL: https://issues.apache.org/jira/browse/IGNITE-20566
Project: Ignite
Issue Type: Bug
Reporter: Anton Vinogradov
Assignee: Nikolay Izhikov
To reproduce just change
{{org.apache.ignite.cdc.CdcConfiguration#DFLT_KEEP_BINARY}} to the {{false}}.
{{org.apache.ignite.cdc.AbstractReplicationTest#testActivePassiveReplication}}
still will be successfull since uses promitive key/val.
{{org.apache.ignite.cdc.AbstractReplicationTest#testActivePassiveReplicationComplexKeyWithKeyValue}}
will stuck, transaction on destination cluster will never be finished.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20508) DeadlockDetectionManager removal
[ https://issues.apache.org/jira/browse/IGNITE-20508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20508: -- Fix Version/s: 2.16 > DeadlockDetectionManager removal > > > Key: IGNITE-20508 > URL: https://issues.apache.org/jira/browse/IGNITE-20508 > 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] [Assigned] (IGNITE-20528) CDC doesn't work if the "Cache objects transformation" is applied
[
https://issues.apache.org/jira/browse/IGNITE-20528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-20528:
-
Assignee: Anton Vinogradov
> CDC doesn't work if the "Cache objects transformation" is applied
> -
>
> Key: IGNITE-20528
> URL: https://issues.apache.org/jira/browse/IGNITE-20528
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Korotkov
>Assignee: Anton Vinogradov
>Priority: Major
> Labels: iep-97, ise
>
> CDC doesn't work If some cache objects transformation is applied (see the
> [https://cwiki.apache.org/confluence/display/IGNITE/IEP-97+Cache+objects+transformation|https://cwiki.apache.org/confluence/display/IGNITE/IEP-97+Cache+objects+transformation]).
> ignite_cdc.sh utility produces the NPE (see below). The immediate reason of
> the NPE is that ignite_cdc.sh uses the reduced version of the context
> (StandaloneGridKernalContext), which doesn't contain the GridCacheProcessor.
>
> {noformat}
> [2023-10-02T10:43:32,017][ERROR][Thread-1][] Unable to convert value
> [CacheObjectImpl [val=null, hasValBytes=true]]
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.CacheObjectTransformerUtils.transformer(CacheObjectTransformerUtils.java:32)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectTransformerUtils.restoreIfNecessary(CacheObjectTransformerUtils.java:120)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectAdapter.valueFromValueBytes(CacheObjectAdapter.java:73)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:92)
> ~[classes/:?]
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.value(CacheObjectImpl.java:58)
> ~[classes/:?]
> at
> org.apache.ignite.internal.pagemem.wal.record.UnwrapDataEntry.unwrappedValue(UnwrapDataEntry.java:104)
> ~[classes/:?]
> at
> org.apache.ignite.internal.cdc.WalRecordsConsumer.lambda$static$c56580e2$1(WalRecordsConsumer.java:99)
> ~[classes/:?]
> at
> org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.nextX(TransformFilteringIterator.java:119)
> [classes/:?]
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:35)
> [classes/:?]
> at
> org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNextX(TransformFilteringIterator.java:85)
> [classes/:?]
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
> [classes/:?]
> at
> org.apache.ignite.cdc.AbstractCdcEventsApplier.apply(AbstractCdcEventsApplier.java:71)
> [ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.cdc.AbstractIgniteCdcStreamer.onEvents(AbstractIgniteCdcStreamer.java:118)
> [ignite-cdc-ext-1.0.0-SNAPSHOT.jar:?]
> at
> org.apache.ignite.internal.cdc.WalRecordsConsumer.onRecords(WalRecordsConsumer.java:142)
> [classes/:?]
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeSegmentActively(CdcMain.java:557)
> [classes/:?]
> at
> org.apache.ignite.internal.cdc.CdcMain.consumeWalSegmentsUntilStopped(CdcMain.java:496)
> [classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.runX(CdcMain.java:344)
> [classes/:?]
> at org.apache.ignite.internal.cdc.CdcMain.run(CdcMain.java:283) [classes/:?]
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal
[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20506: -- Ignite Flags: Release Notes Required > CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal > - > > Key: IGNITE-20506 > URL: https://issues.apache.org/jira/browse/IGNITE-20506 > 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] [Created] (IGNITE-20508) DeadlockDetectionManager removal
Anton Vinogradov created IGNITE-20508: - Summary: DeadlockDetectionManager removal Key: IGNITE-20508 URL: https://issues.apache.org/jira/browse/IGNITE-20508 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20508) DeadlockDetectionManager removal
[ https://issues.apache.org/jira/browse/IGNITE-20508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20508: -- Ignite Flags: (was: Docs Required,Release Notes Required) > DeadlockDetectionManager removal > > > Key: IGNITE-20508 > URL: https://issues.apache.org/jira/browse/IGNITE-20508 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal
[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20506: -- Ignite Flags: (was: Docs Required,Release Notes Required) > CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal > - > > Key: IGNITE-20506 > URL: https://issues.apache.org/jira/browse/IGNITE-20506 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal
[ https://issues.apache.org/jira/browse/IGNITE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20506: -- Fix Version/s: 2.16 > CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal > - > > Key: IGNITE-20506 > URL: https://issues.apache.org/jira/browse/IGNITE-20506 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20506) CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal
Anton Vinogradov created IGNITE-20506: - Summary: CacheAtomicityMode#TRANSACTIONAL_SNAPSHOT removal Key: IGNITE-20506 URL: https://issues.apache.org/jira/browse/IGNITE-20506 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20465) *.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20465: -- Ignite Flags: (was: Docs Required,Release Notes Required) > *.mvccEnabled() removal > --- > > Key: IGNITE-20465 > URL: https://issues.apache.org/jira/browse/IGNITE-20465 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20465) *.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20465: -- Fix Version/s: 2.16 > *.mvccEnabled() removal > --- > > Key: IGNITE-20465 > URL: https://issues.apache.org/jira/browse/IGNITE-20465 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20465) *.mvccEnabled() removal
Anton Vinogradov created IGNITE-20465: - Summary: *.mvccEnabled() removal Key: IGNITE-20465 URL: https://issues.apache.org/jira/browse/IGNITE-20465 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-20433) cctx.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-20433. --- Resolution: Fixed Merged to the master. [~vladsz83], thanks for the review! > cctx.mvccEnabled() removal > -- > > Key: IGNITE-20433 > URL: https://issues.apache.org/jira/browse/IGNITE-20433 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20433) cctx.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20433: -- Fix Version/s: 2.16 > cctx.mvccEnabled() removal > -- > > Key: IGNITE-20433 > URL: https://issues.apache.org/jira/browse/IGNITE-20433 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20433) cctx.mvccEnabled() removal
[ https://issues.apache.org/jira/browse/IGNITE-20433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20433: -- Ignite Flags: (was: Docs Required,Release Notes Required) > cctx.mvccEnabled() removal > -- > > Key: IGNITE-20433 > URL: https://issues.apache.org/jira/browse/IGNITE-20433 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > Time Spent: 3h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20433) cctx.mvccEnabled() removal
Anton Vinogradov created IGNITE-20433: - Summary: cctx.mvccEnabled() removal Key: IGNITE-20433 URL: https://issues.apache.org/jira/browse/IGNITE-20433 Project: Ignite Issue Type: Sub-task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20245) MVCC test/suites removal
[ https://issues.apache.org/jira/browse/IGNITE-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20245: -- Ignite Flags: (was: Docs Required,Release Notes Required) > 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 > Fix For: 2.16 > > Time Spent: 4h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20245) MVCC test/suites removal
[ https://issues.apache.org/jira/browse/IGNITE-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20245: -- Fix Version/s: 2.16 > 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 > Fix For: 2.16 > > Time Spent: 4h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13871) MVCC removal
[ https://issues.apache.org/jira/browse/IGNITE-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13871: -- Labels: ise (was: ) > MVCC removal > > > Key: IGNITE-13871 > URL: https://issues.apache.org/jira/browse/IGNITE-13871 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Anton Vinogradov >Priority: Blocker > Labels: ise > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The community has agreed that MVCC public API should be removed. > Vote thread > http://apache-ignite-developers.2346864.n4.nabble.com/Removing-MVCC-public-API-tp50550.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-20245) MVCC test/suites removal
Anton Vinogradov created IGNITE-20245: - Summary: 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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13871) MVCC removal
[ https://issues.apache.org/jira/browse/IGNITE-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13871: -- Fix Version/s: 2.16 > MVCC removal > > > Key: IGNITE-13871 > URL: https://issues.apache.org/jira/browse/IGNITE-13871 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Anton Vinogradov >Priority: Blocker > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > The community has agreed that MVCC public API should be removed. > Vote thread > http://apache-ignite-developers.2346864.n4.nabble.com/Removing-MVCC-public-API-tp50550.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13871) MVCC removal
[ https://issues.apache.org/jira/browse/IGNITE-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13871: -- Summary: MVCC removal (was: Removing MVCC public API) > MVCC removal > > > Key: IGNITE-13871 > URL: https://issues.apache.org/jira/browse/IGNITE-13871 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Anton Vinogradov >Priority: Blocker > Time Spent: 20m > Remaining Estimate: 0h > > The community has agreed that MVCC public API should be removed. > Vote thread > http://apache-ignite-developers.2346864.n4.nabble.com/Removing-MVCC-public-API-tp50550.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19844) TX code cleanup
[ https://issues.apache.org/jira/browse/IGNITE-19844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-19844: -- Description: It's an umbrella issue to keep all cleanup issues. Scope: #1 !scope.png|width=800! #2 !scope2.png|width=800! #3 !scope3.png|width=800! #4 !scope4.png|width=800! TODO #5 - Grid*Requests and Grid*Responses (like GridNearLockRequest) was: It's an umbrella issue to keep all cleanup issues. Scope: #1 !scope.png|width=800! #2 !scope2.png|width=800! #3 !scope3.png|width=800! #4 !scope4.png|width=800! TODO #5 - Grid*Requests (like GridNearLockRequest) > TX code cleanup > --- > > Key: IGNITE-19844 > URL: https://issues.apache.org/jira/browse/IGNITE-19844 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Attachments: scope.png, scope2.png, scope3.png, scope4.png > > > It's an umbrella issue to keep all cleanup issues. > Scope: > #1 > !scope.png|width=800! > #2 > !scope2.png|width=800! > #3 > !scope3.png|width=800! > #4 > !scope4.png|width=800! > TODO #5 - Grid*Requests and Grid*Responses (like GridNearLockRequest) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19844) TX code cleanup
[ https://issues.apache.org/jira/browse/IGNITE-19844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-19844: -- Description: It's an umbrella issue to keep all cleanup issues. Scope: #1 !scope.png|width=800! #2 !scope2.png|width=800! #3 !scope3.png|width=800! #4 !scope4.png|width=800! TODO #5 - Grid*Requests (like GridNearLockRequest) was: It's an umbrella issue to keep all cleanup issues. Scope: #1 !scope.png|width=800! #2 !scope2.png|width=800! #3 !scope3.png|width=800! #4 !scope4.png|width=800! > TX code cleanup > --- > > Key: IGNITE-19844 > URL: https://issues.apache.org/jira/browse/IGNITE-19844 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Attachments: scope.png, scope2.png, scope3.png, scope4.png > > > It's an umbrella issue to keep all cleanup issues. > Scope: > #1 > !scope.png|width=800! > #2 > !scope2.png|width=800! > #3 > !scope3.png|width=800! > #4 > !scope4.png|width=800! > TODO #5 - Grid*Requests (like GridNearLockRequest) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-13871) Removing MVCC public API
[ https://issues.apache.org/jira/browse/IGNITE-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-13871: - Assignee: Anton Vinogradov (was: Nikolay Izhikov) > Removing MVCC public API > > > Key: IGNITE-13871 > URL: https://issues.apache.org/jira/browse/IGNITE-13871 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Koptilin >Assignee: Anton Vinogradov >Priority: Blocker > Time Spent: 20m > Remaining Estimate: 0h > > The community has agreed that MVCC public API should be removed. > Vote thread > http://apache-ignite-developers.2346864.n4.nabble.com/Removing-MVCC-public-API-tp50550.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (IGNITE-20211) GridNearTxAbstractEnlistFuture and descendants code deduplication
[ https://issues.apache.org/jira/browse/IGNITE-20211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755464#comment-17755464 ] Anton Vinogradov edited comment on IGNITE-20211 at 8/17/23 10:12 AM: - Can not be fixed properly before MVCC removal (IGNITE-13871) was (Author: av): Can not be fix properly before MVCC removal (IGNITE-13871) > GridNearTxAbstractEnlistFuture and descendants code deduplication > - > > Key: IGNITE-20211 > URL: https://issues.apache.org/jira/browse/IGNITE-20211 > 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] [Resolved] (IGNITE-20211) GridNearTxAbstractEnlistFuture and descendants code deduplication
[ https://issues.apache.org/jira/browse/IGNITE-20211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-20211. --- Resolution: Won't Fix Can not be fix properly before MVCC removal (IGNITE-13871) > GridNearTxAbstractEnlistFuture and descendants code deduplication > - > > Key: IGNITE-20211 > URL: https://issues.apache.org/jira/browse/IGNITE-20211 > 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] [Deleted] (IGNITE-20218) CacheDistributedGetFutureAdapter and descendants initial deduplication
[ https://issues.apache.org/jira/browse/IGNITE-20218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov deleted IGNITE-20218: -- > CacheDistributedGetFutureAdapter and descendants initial deduplication > -- > > Key: IGNITE-20218 > URL: https://issues.apache.org/jira/browse/IGNITE-20218 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20218) CacheDistributedGetFutureAdapter and descendants initial deduplication
[ https://issues.apache.org/jira/browse/IGNITE-20218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-20218: -- Ignite Flags: (was: Docs Required,Release Notes Required) > CacheDistributedGetFutureAdapter and descendants initial deduplication > -- > > Key: IGNITE-20218 > URL: https://issues.apache.org/jira/browse/IGNITE-20218 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
