[
https://issues.apache.org/jira/browse/IGNITE-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535718#comment-16535718
]
Maxim Muzafarov edited comment on IGNITE-8737 at 7/7/18 10:42 AM:
------------------------------------------------------------------
[~sergey-chugunov],
Yes, looks like we've missed some cases with this improvement and TeamCity
haven't showed us this problem due to execution timeouts for some suites.
I've filed new issue IGNITE-8957 for this case.
I'm not familiar with Ignite persistence. Would it be better and faster to ask
[~andmed] to fix this issue as an author of checkpoint logging improvement?
was (Author: mmuzaf):
[~sergey-chugunov],
Yes, looks like we've missed some cases with this improvement and TeamCity
haven't showed us this problem due to execution timeouts for some suites.
I've filed new issue
[IGNITE-8957|https://issues.apache.org/jira/browse/IGNITE-8957] for this case.
I'm not familiar with Ignite persistence. Would it be better and faster to ask
[~andmed] to fix this issue as an author of checkpoint logging improvement?
> Improve checkpoint logging information
> --------------------------------------
>
> Key: IGNITE-8737
> URL: https://issues.apache.org/jira/browse/IGNITE-8737
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: Andrew Medvedev
> Priority: Major
> Fix For: 2.7
>
>
> 1) Move to INFO log rollover and log archivation events
> 2) Make sure log rollover and archive errors are logged
> 3) When checkpoint finishes, we need to print out which segments were fully
> covered by this checkpoint in the "Checkpoint finished ..." message
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
