Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CF9D6200D34 for ; Fri, 29 Sep 2017 00:55:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CDCB71609CD; Thu, 28 Sep 2017 22:55:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1F3531609EC for ; Fri, 29 Sep 2017 00:55:05 +0200 (CEST) Received: (qmail 83560 invoked by uid 500); 28 Sep 2017 22:55:05 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 83549 invoked by uid 99); 28 Sep 2017 22:55:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Sep 2017 22:55:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A0C331A3EF5 for ; Thu, 28 Sep 2017 22:55:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id f15RFccEzyr0 for ; Thu, 28 Sep 2017 22:55:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2D33D6104A for ; Thu, 28 Sep 2017 22:55:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 62525E0E2B for ; Thu, 28 Sep 2017 22:55:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 84A89242BE for ; Thu, 28 Sep 2017 22:55:00 +0000 (UTC) Date: Thu, 28 Sep 2017 22:55:00 +0000 (UTC) From: "Anu Engineer (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-12464) Ozone: More detailed documentation about the ozone components MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 28 Sep 2017 22:55:07 -0000 [ https://issues.apache.org/jira/browse/HDFS-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185060#comment-16185060 ] Anu Engineer commented on HDFS-12464: ------------------------------------- [~elek] All of the above are excellent questions and I complete agree we need to have documentation for each one of them. bq. One high level overview, with diagram, and explain the basic concepts. Typically for end-users: for the existing users of the HDFS to understand what's new, and why it's important I have just done that in HDFS-12551. bq. I created this more in-depth documentation for the developers/sys-admin who would like to use the system after they understood what is ozone and how it works. That is a very good point, Let us write this and attach it as a document to HDFS-7240. Rather than shipping it as part of the standard documentation. However, if you think end users are going to benefit from it, I am open to doing this. bq. It could help to understand the Ozone during the HDFS-7240 merge vote. . I agree that we need more documentation, but I wanted to make sure that we document the concepts, not the details. bq. It could help to understand the consequences of turning on ozone. For example it's a tipical question where will be any data written. I also missed the definition of the network commiunication for the existing HDFS/YARN. It could help a lot to debug the network issues. There is another JIRA the talks about documenting the file system layout and data storage layout. Let us write docs for those too. I am posting this as work in progress so that we can break this Patch into multiple as you have suggested. > Ozone: More detailed documentation about the ozone components > ------------------------------------------------------------- > > Key: HDFS-12464 > URL: https://issues.apache.org/jira/browse/HDFS-12464 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: HDFS-7240 > Affects Versions: HDFS-7240 > Reporter: Elek, Marton > Assignee: Elek, Marton > Labels: ozoneDoc > Attachments: HDFS-12464-HDFS-7240.001.patch, HDFS-7240-HDFS-12464.001.patch > > > I started to write a more detailed introduction about the Ozone components. The goal is to explain the basic responsibility of the components and the basic network topology (which components sends messages and to where?). > -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org