Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: ctubbsii <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-211-accumulo@git.apache.org>
In-Reply-To: <git-pr-211-accumulo@git.apache.org>
Subject: [GitHub] accumulo pull request #211: ACCUMULO-4480 - update user manual for 1.8
Content-Type: text/plain
Message-Id: <20170203042611.3307CDFF6D@git1-us-west.apache.org>
Date: Fri,  3 Feb 2017 04:26:11 +0000 (UTC)
archived-at: Fri, 03 Feb 2017 04:26:13 -0000

Github user ctubbsii commented on a diff in the pull request:

    https://github.com/apache/accumulo/pull/211#discussion_r99274946
  
    --- Diff: docs/src/main/asciidoc/chapters/administration.txt ---
    @@ -1182,17 +1182,19 @@ conditions that vary from the environments individually tested in the various
     components. For example, Accumulo's use of HDFS includes many short block
     reads, which differs from the more common full file read used in most
     map/reduce applications. We have found that certain versions of Accumulo and
    -Hadoop will include stability bugs that greatly affect overall stability. In
    -our testing, Accumulo 1.6.2, Hadoop 2.6.0, and Zookeeper 3.4.6 resulted in a
    -stable VM clusters that did not fail a month of testing, while Accumulo 1.6.1,
    -Hadoop 2.5.1, and Zookeeper 3.4.5 had a mean time between failure of less than
    -a week under heavy ingest and query load. We expect that results will vary with
    -other configurations, and you should choose your software versions with that in
    -mind.
    -
    -
    -
    -
    -
    -
    -
    +Hadoop will include stability bugs that greatly affect overall stability.
    --- End diff --
    
    It might be worded better as "...may include bugs that..."


---
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.
---