You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/01/28 23:53:34 UTC
[jira] [Commented] (ACCUMULO-2266) TServer should ensure wal
settings are valid for underlying FS
[ https://issues.apache.org/jira/browse/ACCUMULO-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884817#comment-13884817 ]
ASF subversion and git services commented on ACCUMULO-2266:
-----------------------------------------------------------
Commit 07da9e3f3cf783074a52331e0d3a4fe0ab4e388b in branch refs/heads/1.5.1-SNAPSHOT from [~vines]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=07da9e3 ]
ACCUMULO-2266 Checking hdfs minimum block size and failing if it clashes with walog max size
> 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)