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 2014/01/31 09:08:08 UTC
[jira] [Updated] (AURORA-74) Write snapshots and backups in a way
that requires less memory
[ https://issues.apache.org/jira/browse/AURORA-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Farner updated AURORA-74:
------------------------------
Description: Snapshots and backups currently involve passing around instances of the {{Snapshot}} struct. These are fully-hydrated copies of the entire storage. As a result, a scheduler process needs a constant multiplier of heap space headroom in order to perform these operations without encountering {{OutOfMemoryError}} s. Fixing this will require the ability to 'stream' fixed-size parts of storage from {{MemStorage}} to the backing store (currently an {{org.apache.mesos.Log}}), or a file in the case of backups. The reverse is also necessary — a snapshot must be read from a sequence of {{org.apache.mesos.Log.Entry}}s and fed into the in-memory storage. (was: Snapshots and backups currently involve passing around instances of the {{Snapshot}} struct. These are fully-hydrated copies of the entire storage. As a result, a scheduler process needs a constant multiplier of heap space headroom in order to perform these operations without encountering {{OutOfMemoryError}}s. Fixing this will require the ability to 'stream' fixed-size parts of storage from {{MemStorage}} to the backing store (currently an {{org.apache.mesos.Log}}), or a file in the case of backups. The reverse is also necessary — a snapshot must be read from a sequence of {{org.apache.mesos.Log.Entry}}s and fed into the in-memory storage.)
> Write snapshots and backups in a way that requires less memory
> --------------------------------------------------------------
>
> Key: AURORA-74
> URL: https://issues.apache.org/jira/browse/AURORA-74
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Bill Farner
> Priority: Minor
>
> Snapshots and backups currently involve passing around instances of the {{Snapshot}} struct. These are fully-hydrated copies of the entire storage. As a result, a scheduler process needs a constant multiplier of heap space headroom in order to perform these operations without encountering {{OutOfMemoryError}} s. Fixing this will require the ability to 'stream' fixed-size parts of storage from {{MemStorage}} to the backing store (currently an {{org.apache.mesos.Log}}), or a file in the case of backups. The reverse is also necessary — a snapshot must be read from a sequence of {{org.apache.mesos.Log.Entry}}s and fed into the in-memory storage.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)