Return-Path: 
 <notifications-return-10601-apmail-accumulo-notifications-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org
Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2D7C010E5C
	for <apmail-accumulo-notifications-archive@minotaur.apache.org>;
 Wed, 16 Oct 2013 02:59:48 +0000 (UTC)
Received: (qmail 44538 invoked by uid 500); 16 Oct 2013 02:59:44 -0000
Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org
Received: (qmail 44518 invoked by uid 500); 16 Oct 2013 02:59:44 -0000
Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@accumulo.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@accumulo.apache.org>
List-Post: <mailto:notifications@accumulo.apache.org>
List-Id: <notifications.accumulo.apache.org>
Reply-To: jira@apache.org
Delivered-To: mailing list notifications@accumulo.apache.org
Received: (qmail 44502 invoked by uid 99); 16 Oct 2013 02:59:42 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 02:59:42 +0000
Date: Wed, 16 Oct 2013 02:59:42 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12661576.1375584789440.70311.1381892382066@arcas>
In-Reply-To: <JIRA.12661576.1375584789440@arcas>
References: <JIRA.12661576.1375584789440@arcas>
Subject: [jira] [Updated] (ACCUMULO-1637) Update HDFS append/sync
 precondition check for Hadoop 1.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/ACCUMULO-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-1637:
---------------------------------

    Description: 
Apache Hadoop 1.2.0 ships with the durable sync enabled by default and the support append option marked as obsolete. Because of this, the check inside of TabletServer, meant to ensure that the HDFS WAL can function properly, incorrectly fails as it doesn't know that dfs.durable.sync is on by default.

This can be worked around by specifying the old durable sync property in hdfs-site.xml:

{noformat}
<property>
  <name>dfs.durable.sync</name>
  <value>true</value>
</property>
{noformat}

I'm not sure how to best way to address the differences between the newer and older versions of Hadoop and their differing append support.

Thanks to Carlos Mundi for pointing this out on user@a.a.o

Using this table to track the presence of these variables and their default from hdfs/o/a/h/h/DFSConfigKeys
||Version||dfs.support.append||dfs.durable.sync||
|0.20.205.0|default:false|not present|
|0.23.x|default:true|not present|
|1.0.x|default:false|not present|
|1.1.X|not present|not present|
|2.0.x|default:true|not present|
|2.1.x|default:true|not present|
|2.2.0|default:true|not present|

  was:
Apache Hadoop 1.2.0 ships with the durable sync enabled by default and the support append option marked as obsolete. Because of this, the check inside of TabletServer, meant to ensure that the HDFS WAL can function properly, incorrectly fails as it doesn't know that dfs.durable.sync is on by default.

This can be worked around by specifying the old durable sync property in hdfs-site.xml:

{noformat}
<property>
  <name>dfs.durable.sync</name>
  <value>true</value>
</property>
{noformat}

I'm not sure how to best way to address the differences between the newer and older versions of Hadoop and their differing append support.

Thanks to Carlos Mundi for pointing this out on user@a.a.o

Using this table to track the presence of these variables and their default from hdfs/o/a/h/h/DFSConfigKeys
||Version||dfs.support.append||dfs.durable.sync||
|0.20.205.0|default:false|not present|
|0.23.x|default:true|not present|
|1.0.x|default:false|not present|
|1.1.x|not present|default:true|
|1.1.2|not present|not present|
|2.0.x|default:true|not present|
|2.1.x|default:true|not present|
|2.2.0|default:true|not present|


> Update HDFS append/sync precondition check for Hadoop 1.2
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-1637
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1637
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 1.5.1, 1.6.0
>
>
> Apache Hadoop 1.2.0 ships with the durable sync enabled by default and the support append option marked as obsolete. Because of this, the check inside of TabletServer, meant to ensure that the HDFS WAL can function properly, incorrectly fails as it doesn't know that dfs.durable.sync is on by default.
> This can be worked around by specifying the old durable sync property in hdfs-site.xml:
> {noformat}
> <property>
>   <name>dfs.durable.sync</name>
>   <value>true</value>
> </property>
> {noformat}
> I'm not sure how to best way to address the differences between the newer and older versions of Hadoop and their differing append support.
> Thanks to Carlos Mundi for pointing this out on user@a.a.o
> Using this table to track the presence of these variables and their default from hdfs/o/a/h/h/DFSConfigKeys
> ||Version||dfs.support.append||dfs.durable.sync||
> |0.20.205.0|default:false|not present|
> |0.23.x|default:true|not present|
> |1.0.x|default:false|not present|
> |1.1.X|not present|not present|
> |2.0.x|default:true|not present|
> |2.1.x|default:true|not present|
> |2.2.0|default:true|not present|



--
This message was sent by Atlassian JIRA
(v6.1#6144)