aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <>
Subject [jira] [Assigned] (AURORA-942) Explore using a replicated log on top of ZooKeeper
Date Wed, 29 Nov 2017 20:41:00 GMT


Stephan Erb reassigned AURORA-942:

    Assignee: Bill Farner

> Explore using a replicated log on top of ZooKeeper
> --------------------------------------------------
>                 Key: AURORA-942
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Bill Farner
>            Assignee: Bill Farner
>            Priority: Minor
> The scheduler uses the replicated log implementation provided by mesos (native
 It would be interesting to compare this against a replacement that sllows us to:
> - shed code to implement backups and recovery
> - remove one use of a dynamically-linked native library
> - use a store that allows non-leaders to read, for faster recovery and serving from non-active
> - avoid the need for periodic failover (we currently have to do this to induce compaction
in LevelDB and minimize log replay time)
> At first glance, it seems like it would be relatively straightforward to come up with
a Log implementation \[1\] that persists transactions as nodes in ZooKeeper.  This would enable
all the above results.
> \[1\]

This message was sent by Atlassian JIRA

View raw message