ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10045) Add fail-fast mode to bounded iteration of StandaloneWalRecordsIterator
Date Wed, 31 Oct 2018 11:09:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669953#comment-16669953
] 

Ignite TC Bot commented on IGNITE-10045:
----------------------------------------

{panel:title=Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Cache{color} [[tests 3|https://ci.ignite.apache.org/viewLog.html?buildId=2194668]]
* IgniteCacheMvccTestSuite: CacheMvccPartitionedCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_RestartCoordinator_GetPut_Persistence
- 0,0% fails in last 100 master runs.
* IgniteCacheMvccTestSuite: CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence
- 0,0% fails in last 100 master runs.

{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=2194617]]
* IgniteBinarySimpleNameMapperBasicTestSuite: MarshallerContextLockingSelfTest.testMultithreadedUpdate
- 0,0% fails in last 100 master runs.

{color:#d04437}PDS 2{color} [[tests 3|https://ci.ignite.apache.org/viewLog.html?buildId=2194709]]
* IgnitePdsTestSuite2: IgnitePdsPartitionFilesDestroyTest.testPartitionFileDestroyAfterCheckpoint
- 0,0% fails in last 100 master runs.

{color:#d04437}Cache 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=2194687]]
* IgniteBinaryCacheTestSuite: IgniteCacheEntryListenerTxTest.testNoOldValue - 0,0% fails in
last 100 master runs.

{color:#d04437}Cache (Full API Config Variations / Basic){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=2194680]]
* IgniteCacheBasicConfigVariationsFullApiTestSuite: IgniteCacheConfigVariationsFullApiTest.testTtlTx
- 0,0% fails in last 100 master runs.

{color:#d04437}Client Nodes{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2194621]]
* IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect (last started)

{color:#d04437}PDS (Direct IO) 2{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2194704]]
* WalDeletionArchiveFsyncTest.testGridDoesNotStart_BecauseBothWalHistorySizeAndMaxWalArchiveSizeUsed
(last started)

{panel}
[TeamCity Run All Results|http://ci.ignite.apache.org/viewLog.html?buildId=2194724&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Add fail-fast mode to bounded iteration of StandaloneWalRecordsIterator
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-10045
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10045
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Rakov
>            Assignee: Alexey Stelmak
>            Priority: Major
>             Fix For: 2.8
>
>
> Since IGNITE-9294 StandaloneWalRecordsIterator supports bounded iteration. That means
we can specify "from" and "to" WAL pointers and iterator will return records only between
given bounds. 
> The problem is that in current implementation StandaloneWalRecordsIterator just skips
segments if they are missing. For example: if we'll specify fromIdx=0, toIdx = 10 and segments
with indexes=[9, 10] will be missing, we'll just silently finish iteration on idx=8.
> To prevent that, we should be able to switch on fail-fast mode, in which StandaloneWalRecordsIterator
will throw error unless iteration is really started from left bound and ended on right bound.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message