Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5725819C2C for ; Thu, 24 Mar 2016 17:48:26 +0000 (UTC) Received: (qmail 76305 invoked by uid 500); 24 Mar 2016 17:48:26 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 76197 invoked by uid 500); 24 Mar 2016 17:48:26 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 75974 invoked by uid 99); 24 Mar 2016 17:48:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Mar 2016 17:48:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8706E2C1F61 for ; Thu, 24 Mar 2016 17:48:25 +0000 (UTC) Date: Thu, 24 Mar 2016 17:48:25 +0000 (UTC) From: "Jing Zhao (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-10195) Ozone: Add container persistence MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-10195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210632#comment-15210632 ] Jing Zhao commented on HDFS-10195: ---------------------------------- Thanks a lot for the detailed comments and explanation, [~anu]! bq. so ideally we should be having a DB per pipeline For a container's metadata db replication, I think it may be better to replicate the log/ops instead of replicating the db itself. Looks to me this can avoid the too many db issue, and also support metadata update ops better. We may need to have a separate metadata related log file for each container in this case (which may still have some advantage compared with writing individual leveldb logs/files I guess). For this jira I think we do not need to make any change to the current db design/impl. If you think it's worth further exploration and discussion, we can use a separate jira. > Ozone: Add container persistence > -------------------------------- > > Key: HDFS-10195 > URL: https://issues.apache.org/jira/browse/HDFS-10195 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Affects Versions: HDFS-7240 > Reporter: Anu Engineer > Assignee: Anu Engineer > Fix For: HDFS-7240 > > Attachments: HDFS-10195-HDFS-7240.001.patch > > > Adds file based persistence for containers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)