[
https://issues.apache.org/jira/browse/IGNITE-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669954#comment-16669954
]
Ignite TC Bot commented on IGNITE-9903:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2203066]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
IgniteDiagnosticMessagesTest.testSeveralLongRunningTxs - 0,0% fails in last 100
master runs.
{color:#d04437}PDS 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2203158]]
*
ClientAffinityAssignmentWithBaselineTest.testDynamicCacheLongTransactionNodeStart
(last started)
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2203173&buildTypeId=IgniteTests24Java8_RunAll]
> Copy only actual amount of data during archiving of WAL segment
> ---------------------------------------------------------------
>
> Key: IGNITE-9903
> URL: https://issues.apache.org/jira/browse/IGNITE-9903
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Gura
> Assignee: Alexey Stelmak
> Priority: Major
> Fix For: 2.8
>
>
> Current WAL archiver implementation copies full WAL segment to the archive
> while actual size of the segment can be significantly less then
> {{maxWalSegmentSize}} (segment files are preallocated for max possible
> segment size).
> In order to reduce disk space consuming we need copy only actual data of
> segment using {{SWITCH_SEGMENT_RECORD}} as marker. It will require some kind
> of WAL iterator implementation that will just copy WAL records using
> information about record size without records deserialization.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
