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 8E81F200BA5 for ; Wed, 19 Oct 2016 19:19:49 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8D387160AEA; Wed, 19 Oct 2016 17:19:49 +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 D38B9160ADC for ; Wed, 19 Oct 2016 19:19:48 +0200 (CEST) Received: (qmail 39984 invoked by uid 500); 19 Oct 2016 17:19:48 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 39969 invoked by uid 99); 19 Oct 2016 17:19:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2016 17:19:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1C733C1009 for ; Wed, 19 Oct 2016 17:19:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -7.019 X-Spam-Level: X-Spam-Status: No, score=-7.019 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HhbJHST-YsJd for ; Wed, 19 Oct 2016 17:19:44 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id EAF775F1C2 for ; Wed, 19 Oct 2016 17:19:28 +0000 (UTC) Received: (qmail 39381 invoked by uid 99); 19 Oct 2016 17:19:22 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2016 17:19:22 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id DC6E1E04AF; Wed, 19 Oct 2016 17:19:21 +0000 (UTC) From: dyozie To: dev@hawq.incubator.apache.org Reply-To: dev@hawq.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-hawq-docs pull request #22: Feature/start init Content-Type: text/plain Message-Id: <20161019171921.DC6E1E04AF@git1-us-west.apache.org> Date: Wed, 19 Oct 2016 17:19:21 +0000 (UTC) archived-at: Wed, 19 Oct 2016 17:19:49 -0000 Github user dyozie commented on a diff in the pull request: https://github.com/apache/incubator-hawq-docs/pull/22#discussion_r84121208 --- Diff: reference/cli/admin_utilities/hawqinit.html.md.erb --- @@ -40,11 +40,17 @@ where: The `hawq init ` utility will create a HAWQ instance using configuration parameters defined in `$GPHOME/etc/hawq-site.xml`. Before running this utility, make sure that you have installed the HAWQ software on all the hosts in the array. -In a HAWQ DBMS, each database instance (the master and all segments) must be initialized across all of the hosts in the system in such a way that they can all work together as a unified DBMS. The `hawq init cluster` utility takes care of initializing the HAWQ master and each segment instance, and configuring the system as a whole. When hawq init cluster is run, the cluster comes online automatically without needing to explicitly start it. A single node cluster can be started without any user-defined changes to the default `hawq-site.xml` file. The template-hawq-site.xml file is used to specify the configuration for larger clusters. +In a HAWQ DBMS, each database instance (the master and all segments) must be initialized across all of the hosts in the system in such a way that they can all work together as a unified DBMS. The `hawq init cluster` utility takes care of initializing the HAWQ master and each segment instance, and configuring the system as a whole. When hawq init cluster is run, the cluster comes online automatically without needing to explicitly start it. A single node cluster can be started without any user-defined changes to the default `hawq-site.xml` file. Use the template-hawq-site.xml file to specify the configuration for larger clusters. --- End diff -- Also do a quick edit for passive voice here. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---