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 9D9F3200C16 for ; Thu, 9 Feb 2017 17:11:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9C448160B50; Thu, 9 Feb 2017 16:11:32 +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 E7E49160B4C for ; Thu, 9 Feb 2017 17:11:31 +0100 (CET) Received: (qmail 69860 invoked by uid 500); 9 Feb 2017 16:11:31 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 69495 invoked by uid 99); 9 Feb 2017 16:11:30 -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; Thu, 09 Feb 2017 16:11:30 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 8FBA9DFBE6; Thu, 9 Feb 2017 16:11:30 +0000 (UTC) From: mjwall To: dev@accumulo.apache.org Reply-To: dev@accumulo.apache.org References: In-Reply-To: Subject: [GitHub] accumulo pull request #211: ACCUMULO-4480 - update user manual for 1.8 Content-Type: text/plain Message-Id: <20170209161130.8FBA9DFBE6@git1-us-west.apache.org> Date: Thu, 9 Feb 2017 16:11:30 +0000 (UTC) archived-at: Thu, 09 Feb 2017 16:11:32 -0000 Github user mjwall commented on a diff in the pull request: https://github.com/apache/accumulo/pull/211#discussion_r100342451 --- 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. +Release notes typically contain information about versions used in +release testing. + +The following table shows the Hadoop, Zookeeper and +Thrift versions defined in the dependency section of the POM for building the +artifacts. + +|================================================ +|Accumulo |Hadoop |Zookeeper |Thrift +|1.7 |2.2.0 |3.4.6 |0.9.1 +|1.8 |2.6.4 |3.4.6 |0.9.3 +|================================================ + --- End diff -- So here is where I am after reading through this. Replace the table with a paragraph that combines the wording from > Accumulo has been built and tested with specific dependency versions. Please check the release notes at https://accumulo.apache.org for the version of Accumulo you're using, for any known compatibility issues. and > The versions set in the pom for Hadoop and ZooKeeper are treated as stable releases which provide a large-breadth of compatibility across other versions of those components. They do not guarantee compatibility with any other versions because Hadoop and ZooKeeper do not provide any such guarantee. and include a warning about getting the thrift version correct. --- 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. ---