Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 28 Jan 2014 22:51:34 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12691658.1390925765973.778.1390949494769@arcas>
In-Reply-To: <JIRA.12691658.1390925765973@arcas>
References: <JIRA.12691658.1390925765973@arcas>
Subject: [jira] [Assigned] (ACCUMULO-2266) TServer should ensure wal
 settings are valid for underlying FS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Vines reassigned ACCUMULO-2266:
------------------------------------

    Assignee: John Vines

> TServer should ensure wal settings are valid for underlying FS
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-2266
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2266
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.5.0
>            Reporter: Sean Busbey
>            Assignee: John Vines
>            Priority: Critical
>             Fix For: 1.5.1, 1.6.0
>
>
> ACCUMULO-2264 revealed a problem in how the tserver handles conflicts between its settings and the restrictions of the underlying fs.
> In the case of ACCUMULO-2264, if the tserver is configured with a wal block size less than that allowed by HDFS the tserver sits in an infinite loop.
> The tserver should probably be checking for the minimum blocksize (the property is dfs.namenode.fs-limits.min-block-size) and then either issuing a WARN/ERROR to the client and using the minimum or failing loudly and refusing to start. I favor the latter.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)