[jira] [Commented] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
[
https://issues.apache.org/jira/browse/IGNITE-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754909#comment-16754909
]
Ignite TC Bot commented on IGNITE-10764:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2893911]]
* IgnitePdsTestSuite:
BPlusTreeReuseListPageMemoryImplTest.testSizeForRandomPutRmvMultithreadedAsync_16
- 0,0% fails in last 430 master runs.
{color:#d04437}Cache 3{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2893895]]
* IgniteBinaryObjectsCacheTestSuite3:
IgniteCacheGroupsTest.testEntriesTtlAtomicPartitioned - 0,0% fails in last 277
master runs.
{color:#d04437}Cache 9{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2893901]]
* IgniteCacheTestSuite9: IoStatisticsManagerSelfTest.testPersistentIOGlobalStat
- 0,0% fails in last 76 master runs.
{color:#d04437}Cache 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2893896]]
* IgniteCacheTestSuite4:
CacheStoreUsageMultinodeDynamicStartTxTest.testDynamicStartWriteBehindStore -
0,0% fails in last 423 master runs.
{color:#d04437}Platform C++ (Win x64 | Release){color} [[tests 0
BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2893870]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2893944buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Transactions failed to acquire lock within timeout
>
>
> Key: IGNITE-10764
> URL: https://issues.apache.org/jira/browse/IGNITE-10764
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some tests failed sporadically due to a transaction timeout though they
> update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
[
https://issues.apache.org/jira/browse/IGNITE-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754782#comment-16754782
]
Roman Kondakov commented on IGNITE-10764:
-
[~Pavlukhin], in this case patch looks good for me and can be merged.
> MVCC: Transactions failed to acquire lock within timeout
>
>
> Key: IGNITE-10764
> URL: https://issues.apache.org/jira/browse/IGNITE-10764
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some tests failed sporadically due to a transaction timeout though they
> update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
[
https://issues.apache.org/jira/browse/IGNITE-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754777#comment-16754777
]
Ivan Pavlukhin commented on IGNITE-10764:
-
[~rkondakov] Yes you described the thing pretty well.
> MVCC: Transactions failed to acquire lock within timeout
>
>
> Key: IGNITE-10764
> URL: https://issues.apache.org/jira/browse/IGNITE-10764
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some tests failed sporadically due to a transaction timeout though they
> update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
[
https://issues.apache.org/jira/browse/IGNITE-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754093#comment-16754093
]
Roman Kondakov commented on IGNITE-10764:
-
[~Pavlukhin], could you please clarify the reason of the test failures? Is it
caused by the big size of the transaction and small timeout? And on some weak
agents transactions were were not able to acquire all needed locks within
timeout? And there is no any other reason why are locks are not acquired in
time, right?
> MVCC: Transactions failed to acquire lock within timeout
>
>
> Key: IGNITE-10764
> URL: https://issues.apache.org/jira/browse/IGNITE-10764
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some tests failed sporadically due to a transaction timeout though they
> update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
[
https://issues.apache.org/jira/browse/IGNITE-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752116#comment-16752116
]
Ivan Pavlukhin commented on IGNITE-10764:
-
TC run of the suite containing problematic the test.
> MVCC: Transactions failed to acquire lock within timeout
>
>
> Key: IGNITE-10764
> URL: https://issues.apache.org/jira/browse/IGNITE-10764
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some tests failed sporadically due to a transaction timeout though they
> update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
[
https://issues.apache.org/jira/browse/IGNITE-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750048#comment-16750048
]
Ivan Pavlukhin commented on IGNITE-10764:
-
Increasing timeout for a single transaction might fix mentioned test.
Decreasing tx timeout allows to reproduce the issue easily. Exception message
{code}Failed to acquire lock within provided timeout for transaction{code}
looks misleading.
> MVCC: Transactions failed to acquire lock within timeout
>
>
> Key: IGNITE-10764
> URL: https://issues.apache.org/jira/browse/IGNITE-10764
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> Some tests failed sporadically due to a transaction timeout though they
> update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
