[jira] [Created] (IGNITE-13875) Configure notifications for ignite-3 git repository
Ivan Pavlukhin created IGNITE-13875: --- Summary: Configure notifications for ignite-3 git repository Key: IGNITE-13875 URL: https://issues.apache.org/jira/browse/IGNITE-13875 Project: Ignite Issue Type: Task Components: general Reporter: Ivan Pavlukhin Currently notifications for PRs in https://github.com/apache/ignite-3 repository are sent to dev-list. Notifications can be configured similarly to https://github.com/apache/ignite repository. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12998) Fix a typo in CONTRIBUTING.md
Ivan Pavlukhin created IGNITE-12998: --- Summary: Fix a typo in CONTRIBUTING.md Key: IGNITE-12998 URL: https://issues.apache.org/jira/browse/IGNITE-12998 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin CoPDoC abbreviation should be spelled properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12987) Remove TC badge from README.md
Ivan Pavlukhin created IGNITE-12987: --- Summary: Remove TC badge from README.md Key: IGNITE-12987 URL: https://issues.apache.org/jira/browse/IGNITE-12987 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin Currently TC badge in main [README|https://github.com/apache/ignite/blob/master/README.md] seems to be not very useful because a build status is not seen directly (is says "no permissions to get data"). Moreover TC results are not very representative because integration tests are not stable by nature and we rely on TC bot checks instead of plain TC status. Let's remove this badge. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12980) Use Apache Ignite logo with registered trade mark symbol in README.md
Ivan Pavlukhin created IGNITE-12980: --- Summary: Use Apache Ignite logo with registered trade mark symbol in README.md Key: IGNITE-12980 URL: https://issues.apache.org/jira/browse/IGNITE-12980 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin Logo in the top of https://github.com/apache/ignite/blob/master/README.md should have registered trademark symbol ® instead of unregistered one ™. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12965) Redirect ignite-website GitHub notifications
Ivan Pavlukhin created IGNITE-12965: --- Summary: Redirect ignite-website GitHub notifications Key: IGNITE-12965 URL: https://issues.apache.org/jira/browse/IGNITE-12965 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin GitHub notifications for all Ignite repositories are sent to notificati...@ignite.apache.org after INFRA-17351. But notifications for a new ignite-website repository (https://github.com/apache/ignite-website) are sent to dev@ignite.apache.org. These notifications should be sent to notificati...@ignite.apache.org as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12787) Remove obsolete Selector.open workaround code from GridNioServer
Ivan Pavlukhin created IGNITE-12787:
---
Summary: Remove obsolete Selector.open workaround code from
GridNioServer
Key: IGNITE-12787
URL: https://issues.apache.org/jira/browse/IGNITE-12787
Project: Ignite
Issue Type: Task
Components: general
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Fix For: 2.9
There is a code in {{GridNioServer}} aimed to workaround an old bug in JDK 1.5
which was fixed in 1.7.
{code}
static {
// This is a workaround for JDK bug (NPE in Selector.open()).
// http://bugs.sun.com/view_bug.do?bug_id=6427854
try {
Selector.open().close();
}
catch (IOException ignored) {
// No-op.
}
}
{code}
Currently Java 8 is a minimal supported version. So, the workaround code can be
removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12686) Deprecate obsolete configuration properties
Ivan Pavlukhin created IGNITE-12686: --- Summary: Deprecate obsolete configuration properties Key: IGNITE-12686 URL: https://issues.apache.org/jira/browse/IGNITE-12686 Project: Ignite Issue Type: Bug Components: cache Reporter: Ivan Pavlukhin Fix For: 2.9 Following properties were discovered as obsolete (no usages in codebase): * TransactionConfiguration.PessimisticTxLogSize * TransactionConfiguration.PessimisticTxLogLinger * CacheConfiguration.DefaultLockTimeout Let's deprecate them. Note that we are not going to remove them at this stage to avoid possible compatibility issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12679) Simplify javadocs in SQL classes
Ivan Pavlukhin created IGNITE-12679: --- Summary: Simplify javadocs in SQL classes Key: IGNITE-12679 URL: https://issues.apache.org/jira/browse/IGNITE-12679 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Fix For: 2.9 Update javadocs according to comments in PR https://github.com/apache/ignite/pull/7412 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12664) Failed to dump debug information. Failed to create string representation of binary object.
Ivan Pavlukhin created IGNITE-12664:
---
Summary: Failed to dump debug information. Failed to create string
representation of binary object.
Key: IGNITE-12664
URL: https://issues.apache.org/jira/browse/IGNITE-12664
Project: Ignite
Issue Type: Bug
Components: binary
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Fix For: 2.9
Logging long transactions warning fails:
{noformat}
Dec 12, 2019 12:18:09 PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to dump debug information: class o.a.i.IgniteException: Failed
to create string representation of binary object.
class org.apache.ignite.IgniteException: Failed to create string representation
of binary object.
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1021)
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:761)
Caused by: java.lang.ClassNotFoundException:
org.springframework.security.core.authority.SimpleGrantedAuthority
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
{noformat}
We are using replicated cache: Cache sessionsCache
where MapSession is:
{code}
public final class MapSession implements ExpiringSession, Serializable {
public static final int DEFAULT_MAX_INACTIVE_INTERVAL_SECONDS = 1800;
private String id;
private Map sessionAttrs;
private long creationTime;
private long lastAccessedTime;
private int maxInactiveInterval;
private static final long serialVersionUID = 7160779239673823561L;
{code}
and sessionAttrs contains SimpleGrantedAuthority.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12644) Get rid of Hadoop javadocs web link
Ivan Pavlukhin created IGNITE-12644:
---
Summary: Get rid of Hadoop javadocs web link
Key: IGNITE-12644
URL: https://issues.apache.org/jira/browse/IGNITE-12644
Project: Ignite
Issue Type: Task
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Fix For: 2.9
Curently we have an external link to Hadoop javadocs in parent pom.xml.
{code}
https://hadoop.apache.org/docs/current/api/
{code}
Quite frequently javadoc build job fails because of inability to connect to
that address. As Hadoop integrations are a subject for removal in next versions
and we do not use external javadoc links for all dependencies it seems safe to
remove the aforementioned link.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12630) Remove developers sections from parent pom.xml
Ivan Pavlukhin created IGNITE-12630: --- Summary: Remove developers sections from parent pom.xml Key: IGNITE-12630 URL: https://issues.apache.org/jira/browse/IGNITE-12630 Project: Ignite Issue Type: Bug Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Fix For: 2.9 We have a section in parent/pom.xml. Listed info in fact is outdated and it is not practical and useful to enumerate everyone in this section. Moreover the proper position here is that the project is developed by Apache Ignite Community. Let's remove this section. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12619) Extend test coverage of [IGNITE-11056] SQL: Create a view with list of existing indexes
Ivan Pavlukhin created IGNITE-12619: --- Summary: Extend test coverage of [IGNITE-11056] SQL: Create a view with list of existing indexes Key: IGNITE-12619 URL: https://issues.apache.org/jira/browse/IGNITE-12619 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Fix For: 2.9 Extend SQL INDEXES system view test coverage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12610) Disable H2 object cache reliably
Ivan Pavlukhin created IGNITE-12610:
---
Summary: Disable H2 object cache reliably
Key: IGNITE-12610
URL: https://issues.apache.org/jira/browse/IGNITE-12610
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.8
Reporter: Ivan Pavlukhin
Fix For: 2.9
Internally H2 maintains a cache of {{org.h2.value.Value}} objects. It can be
disabled by using "h2.objectCache" system property. There is a clear intent to
disable this cache because the system property is set to "false" in
{{org.apache.ignite.internal.processors.query.h2.ConnectionManager}}. But
apparently it is too late, because the property is read by H2 internals before
it. Consequently the object cache is enabled by default.
We need to set this property earlier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12591) Scan query scans invalid partitions on unstable topology
Ivan Pavlukhin created IGNITE-12591:
---
Summary: Scan query scans invalid partitions on unstable topology
Key: IGNITE-12591
URL: https://issues.apache.org/jira/browse/IGNITE-12591
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.8
Reporter: Ivan Pavlukhin
Apparently scan query {{ScanQuery}} (without specifying explicit partition)
does not reserve partitions. Consequently when there is a partition movement
(unstable topology, e.g. new node joins the cluster) query can read from an
invalid (e.g. already destroyed) partition.
It is easy to catch "java.lang.IllegalStateException: Tree is being
concurrently destroyed". As it is a consequence of a race condition other
exceptions might be possible. See attached reproducer.
One possible solution here is to reserve partitions properly. Other approach is
to consider some optimistic strategy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12574) Fix failing IoStatisticsBasicIndexSelfTest
Ivan Pavlukhin created IGNITE-12574: --- Summary: Fix failing IoStatisticsBasicIndexSelfTest Key: IGNITE-12574 URL: https://issues.apache.org/jira/browse/IGNITE-12574 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Fix For: 2.9 Need to move org.apache.ignite.internal.processors.cache.index.IoStatisticsBasicIndexSelfTest into a test suite with enabled persistence. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12565) Extend test coverage [IGNITE-9279] Support custom default SQL schema name
Ivan Pavlukhin created IGNITE-12565: --- Summary: Extend test coverage [IGNITE-9279] Support custom default SQL schema name Key: IGNITE-12565 URL: https://issues.apache.org/jira/browse/IGNITE-12565 Project: Ignite Issue Type: Task Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Fix For: 2.9 Add more tests to cover schemas support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12498) Calcite integration. Create a test suite on TC.
Ivan Pavlukhin created IGNITE-12498: --- Summary: Calcite integration. Create a test suite on TC. Key: IGNITE-12498 URL: https://issues.apache.org/jira/browse/IGNITE-12498 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin A separate TC build job should be created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12482) SQL: sql returns incorrect results for replicated caches if started on node where rebalance is in progress
Ivan Pavlukhin created IGNITE-12482: --- Summary: SQL: sql returns incorrect results for replicated caches if started on node where rebalance is in progress Key: IGNITE-12482 URL: https://issues.apache.org/jira/browse/IGNITE-12482 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Fix For: 2.8 To reproduce you should do next: 1)Start 3 data nodes with persistence 2)Load 100_000 entries to SQL cache 3)Stop one node 4)Load another100_000 entries to SQL cache 5)Stop second node 6)Load another100_000 entries to SQL cache 7)Start node one and node2 -> rebalance will be started 8)In parallel start select count query from every data node Results will be like next. SqlSize is 30, Ignite is sqltests.IncorrectSizeDuringRebalanceOfReplicatedCachesTest2 SqlSize is 122684, Ignite is sqltests.IncorrectSizeDuringRebalanceOfReplicatedCachesTest1 SqlSize is 26898, Ignite is sqltests.IncorrectSizeDuringRebalanceOfReplicatedCachesTest0 Cache sizes will be correct in this case: CacheSize is 30, Ignite is sqltests.IncorrectSizeDuringRebalanceOfReplicatedCachesTest2 CacheSize is 30, Ignite is sqltests.IncorrectSizeDuringRebalanceOfReplicatedCachesTest1 CacheSize is 30, Ignite is sqltests.IncorrectSizeDuringRebalanceOfReplicatedCachesTest0 It means that during rebalance customers will be able to get incorrect results for SQL queries during the rebalance process if it will be started from "bad" node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12477) Slow test in Queries 1 test suite
Ivan Pavlukhin created IGNITE-12477: --- Summary: Slow test in Queries 1 test suite Key: IGNITE-12477 URL: https://issues.apache.org/jira/browse/IGNITE-12477 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin "Queries 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12476) Slow test in Continuous Query 1 test suite
Ivan Pavlukhin created IGNITE-12476: --- Summary: Slow test in Continuous Query 1 test suite Key: IGNITE-12476 URL: https://issues.apache.org/jira/browse/IGNITE-12476 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin "Continuous Query 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12457) Cache 6 test suite fails with exit code 137
Ivan Pavlukhin created IGNITE-12457: --- Summary: Cache 6 test suite fails with exit code 137 Key: IGNITE-12457 URL: https://issues.apache.org/jira/browse/IGNITE-12457 Project: Ignite Issue Type: Bug Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Recently Cache 6 test suite started failing with uplesantly with exit code 137. Whole suite fails with no details about passed and failed tests. IgniteCache150ClientsTest seems to be a root cause. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
Ivan Pavlukhin created IGNITE-12424: --- Summary: Fix default query timeout behavior for thin JDBC Key: IGNITE-12424 URL: https://issues.apache.org/jira/browse/IGNITE-12424 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Fix For: 2.8 After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. Thin JDBC handles explicit query timeout on a client side. Default query timeout is tracked on a server side. As a server is not aware of explicit client timeout it is not possible to override a default timeout with longer explicit timeout (effectively a query will be cancelled after a default timeout expiration). The expected behavior is that an explicit query timeout always overrides a default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12050) MVCC test suites resurrection
Ivan Pavlukhin created IGNITE-12050: --- Summary: MVCC test suites resurrection Key: IGNITE-12050 URL: https://issues.apache.org/jira/browse/IGNITE-12050 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Need to resurrect MVCC test suites for RunAll. Mute all tests with fail rate more 50% And start use scale factor for MVCC tests to reduce execution time. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12041) CacheMvccTransactionsTest.testNodesRestartNoHang fails frequently
Ivan Pavlukhin created IGNITE-12041:
---
Summary: CacheMvccTransactionsTest.testNodesRestartNoHang fails
frequently
Key: IGNITE-12041
URL: https://issues.apache.org/jira/browse/IGNITE-12041
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
CacheMvccTransactionsTest.testNodesRestartNoHang fails frequently on TC.
{noformat}
84)
[2019-08-02
15:48:13,510][ERROR][sys-stripe-21-#34781%mvcc.CacheMvccTransactionsTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=StopNodeFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=CRITICAL_ERROR, err=class
o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=81227264,
val2=844420635164673]], msg=Runtime failure on search row: TxKey
[major=1564750080783, minor=1116
class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=81227264,
val2=844420635164673]], msg=Runtime failure on search row: TxKey
[major=1564750080783, minor=1116]]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:5921)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1865)
at
org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.put(TxLog.java:294)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.updateState(MvccProcessorImpl.java:695)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.setMvccState(IgniteTxManager.java:2551)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1227)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.state(IgniteTxAdapter.java:1069)
at
org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.prepareRemoteTx(GridDistributedTxRemoteAdapter.java:422)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.startRemoteTx(IgniteTxHandler.java:1855)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxPrepareRequest(IgniteTxHandler.java:1201)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$400(IgniteTxHandler.java:121)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:227)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:225)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1141)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1602)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1227)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4300(GridIoManager.java:131)
at
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1124)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:550)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.lang.IllegalStateException: Unexpected new transaction state.
[currState=2, newState=1, cntr=1116]
at
org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.invalid(TxLog.java:630)
at
org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.checkAborted(TxLog.java:606)
at
org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:500)
at
org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:441)
[jira] [Created] (IGNITE-12040) IgniteNodeStoppedDuringDisableWALTest.test[AFTER_DISABLE_WAL] fails in MVCC mode
Ivan Pavlukhin created IGNITE-12040:
---
Summary:
IgniteNodeStoppedDuringDisableWALTest.test[AFTER_DISABLE_WAL] fails in MVCC mode
Key: IGNITE-12040
URL: https://issues.apache.org/jira/browse/IGNITE-12040
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
IgniteNodeStoppedDuringDisableWALTest.test[AFTER_DISABLE_WAL] fails in MVCC
mode.
{noformat}
[2019-08-02
12:59:35,836][ERROR][test-runner-#7379%wal.IgniteNodeStoppedDuringDisableWALTest%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [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.StorageException: Failed to read record by
pointer [ptr=FileWALPointer [idx=0, fileOff=0, len=0], rec=IgniteBiTuple
[val1=FileWALPointer [idx=0, fileOff=29, len=29], val2=MemoryRecoveryRecord
[time=1564739950672, super=WALRecord [size=29, chainSize=0, pos=FileWALPointer
[idx=0, fileOff=29, len=29], type=MEMORY_RECOVERY]]
class org.apache.ignite.internal.processors.cache.persistence.StorageException:
Failed to read record by pointer [ptr=FileWALPointer [idx=0, fileOff=0, len=0],
rec=IgniteBiTuple [val1=FileWALPointer [idx=0, fileOff=29, len=29],
val2=MemoryRecoveryRecord [time=1564739950672, super=WALRecord [size=29,
chainSize=0, pos=FileWALPointer [idx=0, fileOff=29, len=29],
type=MEMORY_RECOVERY
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.read(FileWriteAheadLogManager.java:913)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2233)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:795)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:5461)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1167)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1987)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1687)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1110)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:608)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:970)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:911)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:899)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:865)
at
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteNodeStoppedDuringDisableWALTest.testStopNodeWithDisableWAL(IgniteNodeStoppedDuringDisableWALTest.java:203)
at
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteNodeStoppedDuringDisableWALTest.test(IgniteNodeStoppedDuringDisableWALTest.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2069)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12039) CacheGroupMetricsMBeanTest.testCacheGroupMetrics fails in MVCC mode
Ivan Pavlukhin created IGNITE-12039:
---
Summary: CacheGroupMetricsMBeanTest.testCacheGroupMetrics fails in
MVCC mode
Key: IGNITE-12039
URL: https://issues.apache.org/jira/browse/IGNITE-12039
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
CacheGroupMetricsMBeanTest.testCacheGroupMetrics fails in MVCC mode.
{noformat}
java.lang.AssertionError: Renting partitions count when node returns not equals
to moved partitions when node left
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
org.apache.ignite.testframework.junits.JUnitAssertAware.assertTrue(JUnitAssertAware.java:28)
at
org.apache.ignite.internal.processors.cache.CacheGroupMetricsMBeanTest.testCacheGroupMetrics(CacheGroupMetricsMBeanTest.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2069)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12037) Ignore tests in MVCC PDS 3 suite canonically
Ivan Pavlukhin created IGNITE-12037:
---
Summary: Ignore tests in MVCC PDS 3 suite canonically
Key: IGNITE-12037
URL: https://issues.apache.org/jira/browse/IGNITE-12037
Project: Ignite
Issue Type: Task
Components: mvcc
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Currently tests in IgnitePdsMvccTestSuite3 are ignored using following
construction:
{code}
// TODO https://issues.apache.org/jira/browse/IGNITE-11937
ignoredTests.add(IgnitePdsContinuousRestartTest.class);
ignoredTests.add(IgnitePdsContinuousRestartTestWithExpiryPolicy.class);
{code}
But IgnitePdsContinuousRestartTestWithExpiryPolicy is already ignored (as
ExpiryPolicy is not supported for MVCC caches). And it worth to ignore tests in
IgnitePdsContinuousRestartTest explicitly so they will be listed as ignored
tests after execution.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12009) Clarify java.time.LocalTime mapping in SQL queries
Ivan Pavlukhin created IGNITE-12009:
---
Summary: Clarify java.time.LocalTime mapping in SQL queries
Key: IGNITE-12009
URL: https://issues.apache.org/jira/browse/IGNITE-12009
Project: Ignite
Issue Type: Task
Components: sql
Affects Versions: 2.7.5
Reporter: Ivan Pavlukhin
Currently mappings between, java.time. java.sql and h2 temporal types provokes
some surprising behavior. Need to figure out if there are bugs or it is an
expected behavior.
One example is using java.time.LocalTime as QueryEntity field. If a value of
such column is modified by SQL {{UPDATE}} then precision more than milliseconds
is lost.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12004) CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky
Ivan Pavlukhin created IGNITE-12004: --- Summary: CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky Key: IGNITE-12004 URL: https://issues.apache.org/jira/browse/IGNITE-12004 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.7.5 Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields fails often https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4227647830422954979=testDetails -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12001) SchemaExchangeSelfTest.testServerRestartWithNewTypes is flaky
Ivan Pavlukhin created IGNITE-12001: --- Summary: SchemaExchangeSelfTest.testServerRestartWithNewTypes is flaky Key: IGNITE-12001 URL: https://issues.apache.org/jira/browse/IGNITE-12001 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin SchemaExchangeSelfTest.testServerRestartWithNewTypes is flaky. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12000) IgniteSqlQueryMinMaxTest is flaky
Ivan Pavlukhin created IGNITE-12000: --- Summary: IgniteSqlQueryMinMaxTest is flaky Key: IGNITE-12000 URL: https://issues.apache.org/jira/browse/IGNITE-12000 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.7.5 Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin IgniteSqlQueryMinMaxTest is flaky. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11996) Assertion error in IgniteCacheOffheapManagerImpl#destroyCacheDataStore
Ivan Pavlukhin created IGNITE-11996:
---
Summary: Assertion error in
IgniteCacheOffheapManagerImpl#destroyCacheDataStore
Key: IGNITE-11996
URL: https://issues.apache.org/jira/browse/IGNITE-11996
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.7.5
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Assertion error occurs in a following code:
{code}
boolean removed = partDataStores.remove(p, store);
assert removed;
{code}
It asserts that a partition store must be removed from a map here. But in
practice a removal can occur at least in 2 places: node stop and partition
eviction. Employed synchronization is not sufficient to guarantee that a
removal happens exactly once.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-11951) Set ThreadLocal node name only once in JdkMarshaller
Ivan Pavlukhin created IGNITE-11951:
---
Summary: Set ThreadLocal node name only once in JdkMarshaller
Key: IGNITE-11951
URL: https://issues.apache.org/jira/browse/IGNITE-11951
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.7.5
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Currently {{JdkMarshaller}} saves a node name twice in couple of
marshall/unmarshall methods. Code can be improved to do it only once.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11948) Row count statistics tests fail frequently
Ivan Pavlukhin created IGNITE-11948: --- Summary: Row count statistics tests fail frequently Key: IGNITE-11948 URL: https://issues.apache.org/jira/browse/IGNITE-11948 Project: Ignite Issue Type: Bug Components: sql Reporter: Ivan Pavlukhin RowCountTableStatisticsSurvivesNodeRestartTest and RowCountTableStatisticsUsageTest fail frequently on TC https://ci.ignite.apache.org/viewLog.html?buildId=4238573=IgniteTests24Java8_BinaryObjectsSimpleMapperQueries -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11946) Do not add java.transaction module in Ignite launch scripts
Ivan Pavlukhin created IGNITE-11946:
---
Summary: Do not add java.transaction module in Ignite launch
scripts
Key: IGNITE-11946
URL: https://issues.apache.org/jira/browse/IGNITE-11946
Project: Ignite
Issue Type: Task
Affects Versions: 2.7.5
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Currenlty {{--add-modules=java.transaction}} is used in ignite scripts for Java
9 and 10. Most likely we can remove it safely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11940) MVCC SysPropWalDeltaConsistencyTest.testPutRemoveMultinode fails frequently
Ivan Pavlukhin created IGNITE-11940: --- Summary: MVCC SysPropWalDeltaConsistencyTest.testPutRemoveMultinode fails frequently Key: IGNITE-11940 URL: https://issues.apache.org/jira/browse/IGNITE-11940 Project: Ignite Issue Type: Bug Components: mvcc Affects Versions: 2.7.5 Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11933) Build scalar scaladoc only if javadoc profile is active
Ivan Pavlukhin created IGNITE-11933: --- Summary: Build scalar scaladoc only if javadoc profile is active Key: IGNITE-11933 URL: https://issues.apache.org/jira/browse/IGNITE-11933 Project: Ignite Issue Type: Improvement Components: build Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Currently scaladoc for module _scalar_ is built even if it is not needed. We already have a profile _javadoc_ to enable documentation generation. We can put scaladoc generation under that profile as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11908) OOM in MVCC PDS4
Ivan Pavlukhin created IGNITE-11908: --- Summary: OOM in MVCC PDS4 Key: IGNITE-11908 URL: https://issues.apache.org/jira/browse/IGNITE-11908 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Almost every time [MVCC PDS 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds4_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv] fails with OOM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11901) CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple is flaky
Ivan Pavlukhin created IGNITE-11901: --- Summary: CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple is flaky Key: IGNITE-11901 URL: https://issues.apache.org/jira/browse/IGNITE-11901 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11888) CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup fails on GG TC
Ivan Pavlukhin created IGNITE-11888: --- Summary: CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup fails on GG TC Key: IGNITE-11888 URL: https://issues.apache.org/jira/browse/IGNITE-11888 Project: Ignite Issue Type: Bug Components: cache Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin A test CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11808) Scale test execution time constant along in IgniteCacheCrossCacheTxFailoverTest
Ivan Pavlukhin created IGNITE-11808:
---
Summary: Scale test execution time constant along in
IgniteCacheCrossCacheTxFailoverTest
Key: IGNITE-11808
URL: https://issues.apache.org/jira/browse/IGNITE-11808
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Execution time of {{IgniteCacheCrossCacheTxFailoverTest}} is scaled by using
{{ScaleFactorUtil}}. Currently an explicit constant is used to define test
execution timeout and a magic constant is used after scaling to define a
duration of the test. It is better to use the explicit constant throughout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11534) Partition loss policy is not handled properly for implicit single key transactions
Ivan Pavlukhin created IGNITE-11534:
---
Summary: Partition loss policy is not handled properly for
implicit single key transactions
Key: IGNITE-11534
URL: https://issues.apache.org/jira/browse/IGNITE-11534
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
Assignee: Ivan Pavlukhin
Fix For: 2.8
There is a bug in handling partition loss policies for single put operations
over {{TRANSACTIONAL}} cache (implicit transaction). Key values are passed
improperly for validation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11503) MVCC: Handle partition loss policies
Ivan Pavlukhin created IGNITE-11503: --- Summary: MVCC: Handle partition loss policies Key: IGNITE-11503 URL: https://issues.apache.org/jira/browse/IGNITE-11503 Project: Ignite Issue Type: Task Components: mvcc Reporter: Ivan Pavlukhin We need to be sure that partition loss policy is properly handled during interaction with MVCC caches. It should be covered by tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11398) Remove leftover @RunWith(JUnit4.class)
Ivan Pavlukhin created IGNITE-11398: --- Summary: Remove leftover @RunWith(JUnit4.class) Key: IGNITE-11398 URL: https://issues.apache.org/jira/browse/IGNITE-11398 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin During migration to junit4 transitional construction `@RunWith(JUnit4.class)` was used. And it was forgotten in couple of places. Let's clean up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11357) MVCC: SQL tx operations and DDL inside tx block
Ivan Pavlukhin created IGNITE-11357:
---
Summary: MVCC: SQL tx operations and DDL inside tx block
Key: IGNITE-11357
URL: https://issues.apache.org/jira/browse/IGNITE-11357
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
DLL and special tx (BEGIN, COMMIT) and DDL operations does not behave well
inside explicit tx started using Java API. We should define how such operations
behave inside tx or forbid them inside tx. See test
{{SqlTransactionsCommandsWithMvccEnabledSelfTest#testSqlOperationsWithinNonSqlTransaction}}.
Here is an example of problematic construction:
{code}
try (Transaction tx = node.transactions().txStart(PESSIMISTIC, SERIALIZABLE)) {
cache.put(1, 1);
cache.query(new SqlFieldsQuery("commit"));
cache.put(2, 2);
tx.commit();
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling
Ivan Pavlukhin created IGNITE-11356:
---
Summary: Test framework: Remove custom assumption exceptions
handling
Key: IGNITE-11356
URL: https://issues.apache.org/jira/browse/IGNITE-11356
Project: Ignite
Issue Type: Task
Reporter: Ivan Pavlukhin
It turns out that custom handling of {{AssumptionViolatedException}} can be
removed. Currently with custom handling tests with unmet assumptions are marked
as passed. With default handling failed assumptions on instance level mark
tests as ignored.
Note: on class level reporting in case of unmet assumptions does not look
perfect. But with custom handling a particular test is not included into TC
report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11301) MVCC: Remove extra MVCC initialization messages from logs
Ivan Pavlukhin created IGNITE-11301:
---
Summary: MVCC: Remove extra MVCC initialization messages from logs
Key: IGNITE-11301
URL: https://issues.apache.org/jira/browse/IGNITE-11301
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
Currently upon each MVCC cache start we check that MVCC facilities are started
on a node. As a result we can see many unneeded messages like:
{{[INFO ]... Mvcc processor started.}}
{{[WARN ]... Attempting to start active vacuum.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11300) MVCC: forbid using DataStreamer with allowOverwrite=true
Ivan Pavlukhin created IGNITE-11300:
---
Summary: MVCC: forbid using DataStreamer with allowOverwrite=true
Key: IGNITE-11300
URL: https://issues.apache.org/jira/browse/IGNITE-11300
Project: Ignite
Issue Type: Task
Components: mvcc
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
Fix For: 2.8
Calling {{IgniteDataStreamer.allowOverwrite(true)}} configures a streamer to
use single-key cache put/remove operations for data modification. But
put/remove operations on MVCC caches can be aborted due to write conflicts. So,
some development effort is needed to support that mode properly. Let's throw
exception in such case for MVCC caches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11289) BPlusTree.AbstractForwardCursor can use obsolete page
Ivan Pavlukhin created IGNITE-11289:
---
Summary: BPlusTree.AbstractForwardCursor can use obsolete page
Key: IGNITE-11289
URL: https://issues.apache.org/jira/browse/IGNITE-11289
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Ivan Pavlukhin
There is a possibility that {{AbstractForwardCursor.nextPageId}} refers to a
page which was already excluded from the tree. The problem reproduces with a
scan query execution with put/remove load in background.
Linked PR contains reproducer and some tricks allowing to reproduce the problem
more often. Problem becomes evident when problematic page is taken from
REUSE_BUCKET. But there could be other hidden problems which do no cause any
runtime errors but lead to data inconsistency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11246) Do not use pending entries tree in MVCC execution flow
Ivan Pavlukhin created IGNITE-11246:
---
Summary: Do not use pending entries tree in MVCC execution flow
Key: IGNITE-11246
URL: https://issues.apache.org/jira/browse/IGNITE-11246
Project: Ignite
Issue Type: Improvement
Components: mvcc
Reporter: Ivan Pavlukhin
Fix For: 2.8
Currently {{IgniteCacheOffheapManagerImpl#pendingEntries}} methods are called
during mvcc execution flow. Looks irrelevant and should be cleaned up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11168) .NET: changing TxTimeoutOnPartitionMapExchange has no effect
Ivan Pavlukhin created IGNITE-11168:
---
Summary: .NET: changing TxTimeoutOnPartitionMapExchange has no
effect
Key: IGNITE-11168
URL: https://issues.apache.org/jira/browse/IGNITE-11168
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
It looks like that only default value of {{TxTimeoutOnPartitionMapExchange}}
property is passed from .NET {{TransactionConfiguration}} to Java. The default
value is 0 which means that it is not possible to enable rollback on PME from
.NET {{TransactionConfiguration}}.
It looks like a using wrong variable in code
https://github.com/apache/ignite/blob/751ab2a488eeb5af32280125673907adb3ac9262/modules/platforms/dotnet/Apache.Ignite.Core/IgniteConfiguration.cs#L517
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11029) Public API for edge-chasing deadlock detection configuration
Ivan Pavlukhin created IGNITE-11029:
---
Summary: Public API for edge-chasing deadlock detection
configuration
Key: IGNITE-11029
URL: https://issues.apache.org/jira/browse/IGNITE-11029
Project: Ignite
Issue Type: Task
Components: mvcc
Reporter: Ivan Pavlukhin
Fix For: 2.8
As deadlock detection introduce overhead during transaction processing some
configuration means should be introduced. Following aspects should be addressed:
1. Turning detection on/off.
2. Adjusting a timeout before starting actual detection.
It is proposed to introduce single property in {{TransactionConfiguration}} to
address both items.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11020) Document edge-chasing deadlock detection
Ivan Pavlukhin created IGNITE-11020: --- Summary: Document edge-chasing deadlock detection Key: IGNITE-11020 URL: https://issues.apache.org/jira/browse/IGNITE-11020 Project: Ignite Issue Type: Bug Components: documentation, mvcc Reporter: Ivan Pavlukhin Assignee: Artem Budnikov Fix For: 2.8 Documentation for deadlock detection implemented in related ticket is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10999) NOT NULL sql constraint is not checked for data streamer operations
Ivan Pavlukhin created IGNITE-10999:
---
Summary: NOT NULL sql constraint is not checked for data streamer
operations
Key: IGNITE-10999
URL: https://issues.apache.org/jira/browse/IGNITE-10999
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
It is possible to violate NOT NULL constraint when using
{{IgniteDataStreamer}}. See attached reproducer.
Attention should be paid to various SQL commands using data streamer
internally. Among them:
1. {{COPY}} command.
2. Operations executed with {{SET STREAMING ON}} mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10917) IgniteCacheQueryNodeRestartSelfTest2.testRestarts stable failure
Ivan Pavlukhin created IGNITE-10917:
---
Summary: IgniteCacheQueryNodeRestartSelfTest2.testRestarts stable
failure
Key: IGNITE-10917
URL: https://issues.apache.org/jira/browse/IGNITE-10917
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.7
Reporter: Ivan Pavlukhin
{{IgniteCacheQueryNodeRestartSelfTest2.testRestarts}} fails on master. It was
broken by extending exception details when query fails by linked ticked.
Messages were changed but test expects old ones.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10841) Edge-chasing deadlock detection monitoring
Ivan Pavlukhin created IGNITE-10841: --- Summary: Edge-chasing deadlock detection monitoring Key: IGNITE-10841 URL: https://issues.apache.org/jira/browse/IGNITE-10841 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin A deadlock detection process introduces several effects in the system which should be visible for an administrator. Here are couple of such effects: 1. Rolling back deadlocked transactions. 2. Introducing messaging overhead even in case when there are not deadlocks. Several metrics can be exposed via JMX and/or SQL view. Here are some candidates: 1. Number of detected deadlocks and involved transactions. 2. Sent/received deadlock detection messages count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10807) Support long-running tx rollback on PME
Ivan Pavlukhin created IGNITE-10807:
---
Summary: Support long-running tx rollback on PME
Key: IGNITE-10807
URL: https://issues.apache.org/jira/browse/IGNITE-10807
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
Currently long-running tx rollback on PME does not work for MVCC transactions.
{{org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnTopologyChangeTest#testRollbackOnTopologyChange}}
can be used as starting point.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10757) Refactoring: split MvccProcessor into multiple components
Ivan Pavlukhin created IGNITE-10757: --- Summary: Refactoring: split MvccProcessor into multiple components Key: IGNITE-10757 URL: https://issues.apache.org/jira/browse/IGNITE-10757 Project: Ignite Issue Type: Improvement Components: mvcc Reporter: Ivan Pavlukhin Fix For: 2.8 In current implementation MvccProcessor has multiple responsibilities which can be extracted into separate components. Also it looks like that we do not need an independent processor here because all logic is bound to CacheProcessor. At least 3 components could be created: 1. ShapshotManager responsible for granting MVCC snapshots and handling related messages. 2. LockManager implementing (exclusive) locking for write operations and associated wait queues. Deadlock detection facilities could be also placed here. 3. VacuumManager responsible for scavenging not needed anymore row versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10722) Abbr-plugin: refactoring inside write action error
Ivan Pavlukhin created IGNITE-10722:
---
Summary: Abbr-plugin: refactoring inside write action error
Key: IGNITE-10722
URL: https://issues.apache.org/jira/browse/IGNITE-10722
Project: Ignite
Issue Type: Bug
Reporter: Ivan Pavlukhin
Abbreviation plugin reports error to IDEA log when applying abbreviate
intention. It claims that deadlock is possible.
{code}
2018-12-17 13:35:10,849 [ 21351] ERROR -
oring.BaseRefactoringProcessor - Refactorings should not be started
inside write action
because they start progress inside and any read action from the
progress task would cause the deadlock
java.lang.Exception
at
com.intellij.refactoring.BaseRefactoringProcessor.run(BaseRefactoringProcessor.java:560)
at com.intellij.refactoring.RefactoringImpl.run(RefactoringImpl.java:73)
at
org.apache.ignite.idea.inspection.abbrev.IgniteAbbreviationInspection$RenameToFix.rename(IgniteAbbreviationInspection.java:163)
at
org.apache.ignite.idea.inspection.abbrev.IgniteAbbreviationInspection$RenameToFix.applyFix(IgniteAbbreviationInspection.java:148)
at
org.apache.ignite.idea.inspection.abbrev.IgniteAbbreviationInspection$RenameToFix.applyFix(IgniteAbbreviationInspection.java:121)
at
com.intellij.codeInspection.ex.QuickFixWrapper.invoke(QuickFixWrapper.java:75)
at
com.intellij.codeInsight.intention.impl.IntentionActionWithTextCaching$MyIntentionAction.invoke(IntentionActionWithTextCaching.java:173)
at
com.intellij.codeInsight.intention.impl.ShowIntentionActionsHandler.lambda$invokeIntention$3(ShowIntentionActionsHandler.java:202)
at com.intellij.openapi.application.WriteAction.run(WriteAction.java:105)
at
com.intellij.codeInsight.intention.impl.ShowIntentionActionsHandler.invokeIntention(ShowIntentionActionsHandler.java:204)
at
com.intellij.codeInsight.intention.impl.ShowIntentionActionsHandler.lambda$null$1(ShowIntentionActionsHandler.java:179)
at
com.intellij.openapi.application.TransactionGuardImpl.runSyncTransaction(TransactionGuardImpl.java:88)
at
com.intellij.openapi.application.TransactionGuardImpl.submitTransactionAndWait(TransactionGuardImpl.java:153)
at
com.intellij.codeInsight.intention.impl.ShowIntentionActionsHandler.lambda$chooseActionAndInvoke$2(ShowIntentionActionsHandler.java:178)
at
com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:139)
at
com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:97)
at
com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:87)
at
com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:73)
at
com.intellij.codeInsight.intention.impl.ShowIntentionActionsHandler.chooseActionAndInvoke(ShowIntentionActionsHandler.java:177)
at
com.intellij.codeInsight.intention.impl.IntentionListStep.lambda$applyAction$0(IntentionListStep.java:118)
at
com.intellij.openapi.application.TransactionGuardImpl.performUserActivity(TransactionGuardImpl.java:195)
at
com.intellij.ui.popup.AbstractPopup.lambda$dispose$8(AbstractPopup.java:1417)
at com.intellij.util.ui.UIUtil.invokeLaterIfNeeded(UIUtil.java:3097)
at
com.intellij.ide.IdeEventQueue.ifFocusEventsInTheQueue(IdeEventQueue.java:183)
at
com.intellij.ide.IdeEventQueue.executeWhenAllFocusEventsLeftTheQueue(IdeEventQueue.java:132)
at
com.intellij.openapi.wm.impl.FocusManagerImpl.doWhenFocusSettlesDown(FocusManagerImpl.java:190)
at
com.intellij.openapi.wm.impl.IdeFocusManagerImpl.doWhenFocusSettlesDown(IdeFocusManagerImpl.java:58)
at com.intellij.ui.popup.AbstractPopup.dispose(AbstractPopup.java:1411)
at com.intellij.ui.popup.WizardPopup.dispose(WizardPopup.java:160)
at com.intellij.ui.popup.list.ListPopupImpl.dispose(ListPopupImpl.java:307)
at com.intellij.openapi.util.Disposer$1.execute(Disposer.java:48)
at com.intellij.openapi.util.Disposer$1.execute(Disposer.java:44)
at
com.intellij.openapi.util.objectTree.ObjectNode$1.execute(ObjectNode.java:138)
at
com.intellij.openapi.util.objectTree.ObjectNode$1.execute(ObjectNode.java:107)
at
com.intellij.openapi.util.objectTree.ObjectTree.executeActionWithRecursiveGuard(ObjectTree.java:182)
at
com.intellij.openapi.util.objectTree.ObjectNode.execute(ObjectNode.java:107)
at
com.intellij.openapi.util.objectTree.ObjectTree.executeAll(ObjectTree.java:151)
at com.intellij.openapi.util.Disposer.dispose(Disposer.java:129)
at com.intellij.openapi.util.Disposer.dispose(Disposer.java:125)
at com.intellij.ui.popup.WizardPopup.disposeAllParents(WizardPopup.java:263)
at
com.intellij.ui.popup.list.ListPopupImpl.handleNextStep(ListPopupImpl.java:442)
at
com.intellij.ui.popup.list.ListPopupImpl._handleSelect(ListPopupImpl.java:396)
at
[jira] [Created] (IGNITE-10704) Abbr-plugin: update list of abbreviations
Ivan Pavlukhin created IGNITE-10704: --- Summary: Abbr-plugin: update list of abbreviations Key: IGNITE-10704 URL: https://issues.apache.org/jira/browse/IGNITE-10704 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Recently the list of abbreviation to use was revisited. Updated list is located at https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules The following should be done: * Update the list used by abbreviation plugin. * Rebuild and publish new version of the plugin. NOTE: New version must attached to the page containing rules. Also it could be published on GitHub. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10685) Support JTA transactions for MVCC
Ivan Pavlukhin created IGNITE-10685:
---
Summary: Support JTA transactions for MVCC
Key: IGNITE-10685
URL: https://issues.apache.org/jira/browse/IGNITE-10685
Project: Ignite
Issue Type: Task
Components: mvcc
Reporter: Ivan Pavlukhin
Fix For: 2.8
Currently JTA transactions do not work with MVCC caches. Reported error message
seems wrong:
{code}
SQL queries and cache operations may not be used in the same transaction.
{code}
It also worth to check error messages for other unsupported scenarios (mixed
cache modes in a same transaction).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10167) MVCC-compatible IgniteCache.localEntries
Ivan Pavlukhin created IGNITE-10167:
---
Summary: MVCC-compatible IgniteCache.localEntries
Key: IGNITE-10167
URL: https://issues.apache.org/jira/browse/IGNITE-10167
Project: Ignite
Issue Type: Bug
Reporter: Ivan Pavlukhin
IgniteCache API method {{localEntries}} should be supported. The idea is to
provide an entries iterator seeing latest committed versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10103) Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation
Ivan Pavlukhin created IGNITE-10103: --- Summary: Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation Key: IGNITE-10103 URL: https://issues.apache.org/jira/browse/IGNITE-10103 Project: Ignite Issue Type: Bug Components: cache Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10063) MVCC SQL: Tx SQL commands are not supported in multistatements
Ivan Pavlukhin created IGNITE-10063:
---
Summary: MVCC SQL: Tx SQL commands are not supported in
multistatements
Key: IGNITE-10063
URL: https://issues.apache.org/jira/browse/IGNITE-10063
Project: Ignite
Issue Type: Bug
Reporter: Ivan Pavlukhin
Is is possible to execute multiple statements in single JDBC call like:
{code:sql}UPDATE t1 SET b = '2'; COMMIT{code}
Currently tx commands fail to execute if passed in such multistatement. Tx
commands are e.g. {{BEGIN}}, {{COMMIT}}, {{ROLLBACK}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9783) MVCC: Track all nodes participating in transaction
Ivan Pavlukhin created IGNITE-9783: -- Summary: MVCC: Track all nodes participating in transaction Key: IGNITE-9783 URL: https://issues.apache.org/jira/browse/IGNITE-9783 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin Fix For: 2.7 All nodes should be tracked by near tx in order to make recovery possible. Backup nodes should be tracked as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9774) CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan hangs
Ivan Pavlukhin created IGNITE-9774:
--
Summary:
CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
hangs
Key: IGNITE-9774
URL: https://issues.apache.org/jira/browse/IGNITE-9774
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
Test
{{CacheMvccTransactionsTest#testPutAllGetAll_ClientServer_Backups1_Restart_Scan
hangs}} and can freeze a whole suite. Investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9750) Prohibit near cache configuration for MVCC caches
Ivan Pavlukhin created IGNITE-9750: -- Summary: Prohibit near cache configuration for MVCC caches Key: IGNITE-9750 URL: https://issues.apache.org/jira/browse/IGNITE-9750 Project: Ignite Issue Type: Task Components: mvcc Reporter: Ivan Pavlukhin We should throw an exception when near cache is configured for MVCC cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9735) Determine partitions during parsing for MVCC DML statements
Ivan Pavlukhin created IGNITE-9735:
--
Summary: Determine partitions during parsing for MVCC DML
statements
Key: IGNITE-9735
URL: https://issues.apache.org/jira/browse/IGNITE-9735
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
Now with for MVCC caches query like below is broadcasted instead off sending to
single node only.
{code:java}
update table set _val = _val + 1 where _key = ?{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9647) EVT_CACHE_OBJECT_REMOVED is fired when entry is absent before remove
Ivan Pavlukhin created IGNITE-9647:
--
Summary: EVT_CACHE_OBJECT_REMOVED is fired when entry is absent
before remove
Key: IGNITE-9647
URL: https://issues.apache.org/jira/browse/IGNITE-9647
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Ivan Pavlukhin
Attachments: RemoveEventBugReproducer.java
Currently {{cache.remove(key)}} triggers {{EVT_CACHE_OBJECT_REMOVED}} event
regardless whether entry was in cache before remove or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9624) Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT javadoc
Ivan Pavlukhin created IGNITE-9624:
--
Summary: Refine CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT javadoc
Key: IGNITE-9624
URL: https://issues.apache.org/jira/browse/IGNITE-9624
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
Currently {{CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT}} javadoc contains some
typos. It might be good idea to proof read it and correct grammar.
See PR as starting point.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9622) MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
Ivan Pavlukhin created IGNITE-9622: -- Summary: MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions Key: IGNITE-9622 URL: https://issues.apache.org/jira/browse/IGNITE-9622 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin For cache with enabled mvcc we should allow running only PESSIMISTIC REPEATABLE_READ transactions. For other modes exception should be thrown (like is done for SQL API). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9605) Implicit mvcc transaction could use completed one instead of starting new
Ivan Pavlukhin created IGNITE-9605: -- Summary: Implicit mvcc transaction could use completed one instead of starting new Key: IGNITE-9605 URL: https://issues.apache.org/jira/browse/IGNITE-9605 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin It is possible that statement executed outside of explicit transaction uses completed one explicit transaction from ThreadLocal and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9604) Implicit mvcc transaction could use completed one instead of starting new
Ivan Pavlukhin created IGNITE-9604: -- Summary: Implicit mvcc transaction could use completed one instead of starting new Key: IGNITE-9604 URL: https://issues.apache.org/jira/browse/IGNITE-9604 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin It is possible that statement executed outside of explicit transaction uses completed one explicit transaction from ThreadLocal and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9602) Transaction timeout setter could break GridTimeoutProcessor behavior
Ivan Pavlukhin created IGNITE-9602: -- Summary: Transaction timeout setter could break GridTimeoutProcessor behavior Key: IGNITE-9602 URL: https://issues.apache.org/jira/browse/IGNITE-9602 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7 Reporter: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9516) Vaccum cannot complete after rebalance
Ivan Pavlukhin created IGNITE-9516:
--
Summary: Vaccum cannot complete after rebalance
Key: IGNITE-9516
URL: https://issues.apache.org/jira/browse/IGNITE-9516
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
In mvcc tests we wait for full Vacuum cleanup in {{afterTest}} method in a sake
of tests isolation.
{{org.apache.ignite.internal.processors.cache.mvcc.CacheMvccTransactionsTest#testRebalanceSimple}}
hangs waiting Vacuum to complete. Most likely it was broken after implementing
{{Cache.size}} for SQL operations over mvcc caches. Size for Cache API was not
implemented properly (see related ticket).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9506) Timeout object with mutable end time breaks GridTimeoutProcessor behavior
Ivan Pavlukhin created IGNITE-9506:
--
Summary: Timeout object with mutable end time breaks
GridTimeoutProcessor behavior
Key: IGNITE-9506
URL: https://issues.apache.org/jira/browse/IGNITE-9506
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Ivan Pavlukhin
Current transaction API provides setter method for transaction timeout. It is
possible to run transaction as follows:
{code:java}
try (Transaction tx = ign.transactions().txStart()) {
tx.timeout(TimeUnit.SECONDS.toMillis(10));
...
}{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9459) MVCC Cache.size corner cases
Ivan Pavlukhin created IGNITE-9459:
--
Summary: MVCC Cache.size corner cases
Key: IGNITE-9459
URL: https://issues.apache.org/jira/browse/IGNITE-9459
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Ivan Pavlukhin
During implementation of Cache.size for MVCC some corner cases were found.
Attention must be put on:
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccInitialValue}}
{{mvccRemoveAll}} could erroneously decrement size when deleting version which
was deleted (having {{newVersion}} committed).
{{mvccInitialValue}} could increment value over already existing value from
history during rebalance.
It worth carefully reproduce both cases before making any fixes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9451) Cache API update Cache.size according to SNAPSHOT isolation
Ivan Pavlukhin created IGNITE-9451: -- Summary: Cache API update Cache.size according to SNAPSHOT isolation Key: IGNITE-9451 URL: https://issues.apache.org/jira/browse/IGNITE-9451 Project: Ignite Issue Type: Task Components: mvcc Reporter: Ivan Pavlukhin In scope of supporting Cache API for MVCC caches we should ensure that Cache.size is updated consistently and only on transaction commit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9404) Ignite start hangs infinitely when sync preloading is cancelled
Ivan Pavlukhin created IGNITE-9404:
--
Summary: Ignite start hangs infinitely when sync preloading is
cancelled
Key: IGNITE-9404
URL: https://issues.apache.org/jira/browse/IGNITE-9404
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.6
Reporter: Ivan Pavlukhin
This case fires very rarely in {{TcpDiscoveryRestartTest.testRestart}}. Caches
with {{SYNC}} rebalance mode are affected. When **starting** instance is trying
to preload partitions for such cache from another instance which **stops**
around the same time, first instance could hang infinitely. When {{SYNC}}
rebalance mode is enabled starting instance awaits on **preload future** in
start routine. In another thread it starts fetching partitions and receives an
error from **stopping** instance and cancels **rebalance future** but **preload
future** is not cancelled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9373) MVCC tests fail
Ivan Pavlukhin created IGNITE-9373: -- Summary: MVCC tests fail Key: IGNITE-9373 URL: https://issues.apache.org/jira/browse/IGNITE-9373 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Number of tests in MVCC test suites fail. Most of the fails is a regression introduces by new changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9300) Removal count metric is calculated improperly for transactional cache
Ivan Pavlukhin created IGNITE-9300: -- Summary: Removal count metric is calculated improperly for transactional cache Key: IGNITE-9300 URL: https://issues.apache.org/jira/browse/IGNITE-9300 Project: Ignite Issue Type: Bug Components: cache Reporter: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9292) MVCC SQL: Race during updating TX log on near backup
Ivan Pavlukhin created IGNITE-9292: -- Summary: MVCC SQL: Race during updating TX log on near backup Key: IGNITE-9292 URL: https://issues.apache.org/jira/browse/IGNITE-9292 Project: Ignite Issue Type: Bug Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9233) MVCC SQL: False write conflicts on fast updates
Ivan Pavlukhin created IGNITE-9233: -- Summary: MVCC SQL: False write conflicts on fast updates Key: IGNITE-9233 URL: https://issues.apache.org/jira/browse/IGNITE-9233 Project: Ignite Issue Type: Bug Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Currently is possible to encounter query failure e.g. in case when DELETE with directly specified key encounters write conflict for row which is created by concurrent INSERT. From SNAPSHOT isolation point of view DELETE either should not see a row and do nothing or should remove a row gracefully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9224) MVCC SQL: Cache metrics
Ivan Pavlukhin created IGNITE-9224: -- Summary: MVCC SQL: Cache metrics Key: IGNITE-9224 URL: https://issues.apache.org/jira/browse/IGNITE-9224 Project: Ignite Issue Type: Improvement Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9125) MVCC SQL: Streaming SQL data load operations support
Ivan Pavlukhin created IGNITE-9125: -- Summary: MVCC SQL: Streaming SQL data load operations support Key: IGNITE-9125 URL: https://issues.apache.org/jira/browse/IGNITE-9125 Project: Ignite Issue Type: Improvement Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Since DataStreamer is already enabled for MVCC COPY command and *streaming* INSERT operations should be enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9062) MVCC SQL: H2 connection and statement cache reafactoring
Ivan Pavlukhin created IGNITE-9062: -- Summary: MVCC SQL: H2 connection and statement cache reafactoring Key: IGNITE-9062 URL: https://issues.apache.org/jira/browse/IGNITE-9062 Project: Ignite Issue Type: Improvement Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin H2 connection and statement caching logic is currently spread between several variables. It seems feasible to extract and encapsulate such logic into some H2ConnectionManager class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8982) SQL TX: reuse H2 connections
Ivan Pavlukhin created IGNITE-8982: -- Summary: SQL TX: reuse H2 connections Key: IGNITE-8982 URL: https://issues.apache.org/jira/browse/IGNITE-8982 Project: Ignite Issue Type: Improvement Reporter: Ivan Pavlukhin H2 Connection creation is not very fast. Reusing already created connections could speed up execution in several cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
