[
https://issues.apache.org/jira/browse/AURORA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371994#comment-14371994
]
Maxim Khutornenko commented on AURORA-1211:
-------------------------------------------
Not necessarily. The caveat here is that native log still uses asynchronous
GLOG calls for stderr output. If stderr log file happens to be on the same
device used by scheduler backup process, logging to it may stall and delay
native log operations. Here is an example:
https://github.com/apache/mesos/blob/master/src/log/replica.cpp#L658
> 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)
