You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/03/20 01:35:38 UTC

[jira] [Commented] (AURORA-1211) Spread snapshot creation and backup file write

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

Bill Farner commented on AURORA-1211:
-------------------------------------

I'm not following the hypothesis here.  What is the fallout of high CPU due to garbage collection along with a backup write?

> Spread snapshot creation and backup file write
> ----------------------------------------------
>
>                 Key: AURORA-1211
>                 URL: https://issues.apache.org/jira/browse/AURORA-1211
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>
> Currently, backup files are written asynchronously and overlay with the peak of GC cleaning up after persisting snapshot in native log. We should generally avoid overlaying resource-heavy activities when possible to avoid troubleshooting complicated performance related issues.
> Consider delaying backup file write (e.g. for 1 minute) to clearly separate its impact from the snapshot GC.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)