|author||Jia Zhai <email@example.com>||Thu Aug 17 16:51:53 2017 -0700|
|committer||Sijie Guo <firstname.lastname@example.org>||Thu Aug 17 16:51:53 2017 -0700|
DL-2: DistributedLog should work with the official apache bookkeeper This change is to upgrade bookkeeper version to BK 4.5.0. - upgrade bookkeeper version to 4.5.0-SNAPSHOT (still waiting a few pull requests to merge apache/bookkeeper#297 apache/bookkeeper#287 - change registerSuccessEvent for StatsLogger to add TimeUnit - use netty4 eventloop - move twitter repository dependencies to proxy related module only. core library will not depend on scala dependency anymore. This change is a collaboration change with sijie We will provide a performance comparison between 0.4.0 (using Twitter BK) and 0.5.0 (using BK 4.5.) in a separate pull request or email. Author: Jia Zhai <email@example.com> Author: Jia Zhai <firstname.lastname@example.org> Author: Sijie Guo <email@example.com> Reviewers: Leigh Stewart <firstname.lastname@example.org> This closes #135 from zhaijack/bump_dl_version
Apache DistributedLog (DL) is a high-throughput, low-latency replicated log service, offering durability, replication and strong consistency as essentials for building reliable real-time applications.
Apache DistributedLog project graduated from Incubator at July 2017. It is now a sub-project of Apache BookKeeper.
DL is able to provide milliseconds latency on durable writes with a large number of concurrent logs, and handle high volume reads and writes per second from thousands of clients.
Messages are persisted on disk and replicated to store multiple copies to prevent data loss. They are guaranteed to be consistent among writers and readers in terms of strict ordering.
DL provides an efficient service layer that is optimized for running in a multi- tenant datacenter environment such as Mesos or Yarn. The service layer is able to support large scale writes (fan-in) and reads (fan-out).
DL supports various workloads from latency-sensitive online transaction processing (OLTP) applications (e.g. WAL for distributed database and in-memory replicated state machines), real-time stream ingestion and computing, to analytical processing.
To support a large number of logs for multi-tenants, DL is designed for I/O isolation in real-world workloads.
DL has a modern layered architecture design, which separates the stateless service tier from the stateful storage tier. To support large scale writes (fan- in) and reads (fan-out), DL allows scaling storage independent of scaling CPU and memory.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a jira.
Join us on Slack - This is the most immediate way to connect with DistributedLog committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Guide to get your local environment setup.
Take a look at our open issues.
Make your changes according to our code review workflow.
Checkout the list of project ideas to contribute more features or improvements.
See website/README.md on how to build the website.
See docs/README.md on how to build the documentation.
Apache DistributedLog is an open source project of The Apache Software Foundation (ASF). The Apache DistributedLog project originated from Twitter.