You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@distributedlog.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2016/12/06 17:23:58 UTC
[jira] [Created] (DL-117) Stream metadata store
Sijie Guo created DL-117:
----------------------------
Summary: Stream metadata store
Key: DL-117
URL: https://issues.apache.org/jira/browse/DL-117
Project: DistributedLog
Issue Type: Improvement
Components: distributedlog-core
Affects Versions: 0.4.0
Reporter: Sijie Guo
Assignee: Sijie Guo
This change is to abstract the zookeeper operations into a stream metadata store, so we can replace zookeeper with other me
tadata store easily.
So the metadata operations in distributedlog now are managed by 3 classes:
- LogMetadataStore : it is the namespace metadata store : it manages the location (uri) mapping for streams and handle name
space operations.
- LogStreamMetadataStore: it is the stream metadata store : it manages the metadata for a single stream, such as managing r
ead/write lock, retriving/creating stream metadata, deleting metadata and such.
- LogSegmentMetadataStore: it is the segment metadata store : it manages the log segment metadata for individual log segmen
t.
LogMetadataStore and LogSegmentMetadataStore are already there. This change focus on LogStreamMetadataStore
Changed:
* abstract all the zookeeper metadata operation in log handlers to LogStreamMetadataStore
* remove disabling max tx id santify check, as maxTxId update is part of the metadata update transaction
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)