[
https://issues.apache.org/jira/browse/AURORA-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lambert updated AURORA-1087:
----------------------------------
Component/s: Technical Debt
Removing this from the AURORA-999 epic, as it is not urgent.
> Investigate truncating the replicated log asynchronously
> --------------------------------------------------------
>
> Key: AURORA-1087
> URL: https://issues.apache.org/jira/browse/AURORA-1087
> Project: Aurora
> Issue Type: Story
> Components: Scheduler, Stress Testing, Technical Debt
> Reporter: Kevin Sweeney
> Priority: Minor
>
> Right now we perform a log truncation operation after writing a snapshot
> while holding the global write lock. However this isn't necessary - after
> we've written a Snapshot we can asynchronously truncate to the new log head
> position.
> Investigate if there's a performance benefit here to justify this refactor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
