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 2E359200D19 for ; Fri, 6 Oct 2017 17:49:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2BA651609DF; Fri, 6 Oct 2017 15:49:53 +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 21B711609D0 for ; Fri, 6 Oct 2017 17:49:51 +0200 (CEST) Received: (qmail 95579 invoked by uid 500); 6 Oct 2017 15:49:51 -0000 Mailing-List: contact commits-help@fluo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.apache.org Delivered-To: mailing list commits@fluo.apache.org Received: (qmail 95570 invoked by uid 99); 6 Oct 2017 15:49:51 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Oct 2017 15:49:51 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 665A181A5F; Fri, 6 Oct 2017 15:49:48 +0000 (UTC) Date: Fri, 06 Oct 2017 15:49:48 +0000 To: "commits@fluo.apache.org" Subject: [fluo-website] branch asf-site updated: Jekyll build from gh-pages:94c1e64 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <150730498834.17923.1542790866219167322@gitbox.apache.org> From: mwalch@apache.org X-Git-Host: gitbox.apache.org X-Git-Repo: fluo-website X-Git-Refname: refs/heads/asf-site X-Git-Reftype: branch X-Git-Oldrev: bce04a0d67926fd0365c7cdce96e83eae835d74d X-Git-Newrev: bd931c4ad9a74150c6b72b500770fcf1a03b548c X-Git-Rev: bd931c4ad9a74150c6b72b500770fcf1a03b548c X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated archived-at: Fri, 06 Oct 2017 15:49:53 -0000 This is an automated email from the ASF dual-hosted git repository. mwalch pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/fluo-website.git The following commit(s) were added to refs/heads/asf-site by this push: new bd931c4 Jekyll build from gh-pages:94c1e64 bd931c4 is described below commit bd931c4ad9a74150c6b72b500770fcf1a03b548c Author: Mike Walch AuthorDate: Fri Oct 6 11:48:46 2017 -0400 Jekyll build from gh-pages:94c1e64 Remove slash from URL in docs * Added Next Steps to install docs --- docs/fluo/1.2/administration/initialize.html | 8 ++++---- docs/fluo/1.2/administration/manage-applications.html | 4 ++-- docs/fluo/1.2/administration/run-fluo-in-docker.html | 2 +- docs/fluo/1.2/administration/run-fluo-in-yarn.html | 6 +++--- docs/fluo/1.2/administration/run-fluo-processes.html | 4 ++-- docs/fluo/1.2/getting-started/create-application.html | 6 +++--- docs/fluo/1.2/getting-started/install-fluo.html | 4 ++++ docs/fluo/1.2/getting-started/quick-start.html | 12 ++++++------ feed.xml | 4 ++-- 9 files changed, 27 insertions(+), 23 deletions(-) diff --git a/docs/fluo/1.2/administration/initialize.html b/docs/fluo/1.2/administration/initialize.html index 5317b51..3a44a7f 100644 --- a/docs/fluo/1.2/administration/initialize.html +++ b/docs/fluo/1.2/administration/initialize.html @@ -286,12 +286,12 @@ name is used to start/stop the application and scan the Fluo table.

Run your Fluo application using one of the methods below:

-

Also, learn how to manage Fluo applications.

+

Also, learn how to manage Fluo applications.

diff --git a/docs/fluo/1.2/administration/manage-applications.html b/docs/fluo/1.2/administration/manage-applications.html index e208b53..261b007 100644 --- a/docs/fluo/1.2/administration/manage-applications.html +++ b/docs/fluo/1.2/administration/manage-applications.html @@ -247,8 +247,8 @@ configuration. See the javadoc on Debugging Applications -

While monitoring Fluo metrics can detect problems (like too many transaction collisions) -in a Fluo application, metrics may not provide enough information to debug the root cause +

While monitoring Fluo metrics can detect problems (like too many transaction collisions) +in a Fluo application, metrics may not provide enough information to debug the root cause of the problem. To help debug Fluo applications, low-level logging of transactions can be turned on by setting the following loggers to TRACE:

diff --git a/docs/fluo/1.2/administration/run-fluo-in-docker.html b/docs/fluo/1.2/administration/run-fluo-in-docker.html index a02a321..66cb20d 100644 --- a/docs/fluo/1.2/administration/run-fluo-in-docker.html +++ b/docs/fluo/1.2/administration/run-fluo-in-docker.html @@ -336,7 +336,7 @@ application is named myapp and was initia

Next Steps

-

Learn how to manage Fluo applications.

+

Learn how to manage Fluo applications.

diff --git a/docs/fluo/1.2/administration/run-fluo-in-yarn.html b/docs/fluo/1.2/administration/run-fluo-in-yarn.html index 334f01f..93ed7e5 100644 --- a/docs/fluo/1.2/administration/run-fluo-in-yarn.html +++ b/docs/fluo/1.2/administration/run-fluo-in-yarn.html @@ -236,7 +236,7 @@

Set up your Fluo application

-

Before you can launch a Fluo application in YARN, you should install Fluo and initialize your +

Before you can launch a Fluo application in YARN, you should install Fluo and initialize your application. After your application has been initialized, follow the instructions below to install the Fluo YARN launcher and run your application in YARN. Avoid using the fluo command to start local oracle and worker processes if you are running in YARN.

@@ -315,7 +315,7 @@ each application.

Start Fluo application in YARN

-

Follow the instructions below to start your application in YARN. If you have not done so already, you should initialize +

Follow the instructions below to start your application in YARN. If you have not done so already, you should initialize your Fluo application before following these instructions.

    @@ -337,7 +337,7 @@ application in the YARN resource manager and view its logs.

    Manage Fluo application in YARN

    -

    Except for stopping your application in YARN, the fluo script can be used to manage your application using the +

    Except for stopping your application in YARN, the fluo script can be used to manage your application using the scan and wait commands.

    When you want you stop your Fluo application, use the the YARN resource manager or the diff --git a/docs/fluo/1.2/administration/run-fluo-processes.html b/docs/fluo/1.2/administration/run-fluo-processes.html index dca963c..dfee6f2 100644 --- a/docs/fluo/1.2/administration/run-fluo-processes.html +++ b/docs/fluo/1.2/administration/run-fluo-processes.html @@ -209,7 +209,7 @@ can be manually started by users on a single node or distributed across a cluste

    Requirements

    -

    Each node where Fluo is run must have Fluo installed.

    +

    Each node where Fluo is run must have Fluo installed.

    Start Fluo processes

    @@ -245,7 +245,7 @@ tool like Salt, Ansible, or Chef to install and run Fluo on a cluster.

    Next Steps

    -

    Learn how to manage Fluo applications.

    +

    Learn how to manage Fluo applications.

    diff --git a/docs/fluo/1.2/getting-started/create-application.html b/docs/fluo/1.2/getting-started/create-application.html index 5d19ad3..bc2421f 100644 --- a/docs/fluo/1.2/getting-started/create-application.html +++ b/docs/fluo/1.2/getting-started/create-application.html @@ -204,8 +204,8 @@ -

    Once you have Fluo installed, you can create and run Fluo applications consisting -of clients and observers. This documentation shows how to create a Fluo client and observer.

    +

    Once you have Fluo installed, you can create and run Fluo applications consisting +of clients and observers. This documentation shows how to create a Fluo client and observer.

    Fluo Maven Dependencies

    @@ -326,7 +326,7 @@ These columns persisted in Zookeeper are used by transactions to know when to tr

    Next Steps

    -

    Initialize your Fluo application before running it.

    +

    Initialize your Fluo application before running it.

    diff --git a/docs/fluo/1.2/getting-started/install-fluo.html b/docs/fluo/1.2/getting-started/install-fluo.html index 4e853f4..da79bc9 100644 --- a/docs/fluo/1.2/getting-started/install-fluo.html +++ b/docs/fluo/1.2/getting-started/install-fluo.html @@ -373,6 +373,10 @@ probably increase the tserver.server.threads.min

    Using at least Accumulo 1.6.1 is recommended because multiple performance bugs were fixed.

    +

    Next Steps

    + +

    Create a Fluo application to run or use an example application.

    +
    diff --git a/docs/fluo/1.2/getting-started/quick-start.html b/docs/fluo/1.2/getting-started/quick-start.html index 84a79fb..d8611ee 100644 --- a/docs/fluo/1.2/getting-started/quick-start.html +++ b/docs/fluo/1.2/getting-started/quick-start.html @@ -208,21 +208,21 @@
    1. -

      Install Fluo

      +

      Install Fluo

    2. -

      Create a Fluo application or use an example application.

      +

      Create a Fluo application or use an example application.

    3. -

      Initialize your Fluo application

      +

      Initialize your Fluo application

    4. Pick a method below to run your Fluo application

    diff --git a/feed.xml b/feed.xml index 87756ce..1a4fdac 100644 --- a/feed.xml +++ b/feed.xml @@ -5,8 +5,8 @@ https://fluo.apache.org// - Fri, 06 Oct 2017 15:38:27 +0000 - Fri, 06 Oct 2017 15:38:27 +0000 + Fri, 06 Oct 2017 15:48:41 +0000 + Fri, 06 Oct 2017 15:48:41 +0000 Jekyll v3.3.1 -- To stop receiving notification emails like this one, please contact ['"commits@fluo.apache.org" '].