[
https://issues.apache.org/jira/browse/IGNITE-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968184#comment-16968184
]
Ignite TC Bot commented on IGNITE-12351:
----------------------------------------
{panel:title=Branch: [pull/7036/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4749388&buildTypeId=IgniteTests24Java8_RunAll]
> Append additional cp tracking activity - pages sort.
> ----------------------------------------------------
>
> Key: IGNITE-12351
> URL: https://issues.apache.org/jira/browse/IGNITE-12351
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladimir Malinovskiy
> Assignee: Vladimir Malinovskiy
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CheckpointMetricsTracker has no info about _splitAndSortCpPagesIfNeeded_
> stage, thus in case of huge number of dirty pages someone can observe in log:
> 10:08:00 checkpoint started
> 10:10:00 checkpoint finished
> <--- ??
> 10:10:20 checkpoint started
> if checkpointFrequency = 30000 and all tracker durations: beforeLockDuration,
> lockWaitDuration gives no clue what kind of work (20 sec) Checkpointer thread
> is waiting for.
> Additionally (hope this is not big deal) need t obe fixed redundant
> effectivePageId computation cause FullPageId already has effectivePageId info.
>
> {{return Long.compare(PageIdUtils.effectivePageId(o1.pageId()),
> PageIdUtils.effectivePageId(o2.pageId()));}}
> writeCheckpointEntr() duration should also be logged.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
