You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2014/01/28 17:17:41 UTC
[jira] [Updated] (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:all-tabpanel ]
Sean Busbey updated ACCUMULO-2266:
----------------------------------
Description:
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.
was:
ACCUMULO-2264 revealed a problem in how the tserver handles conflicts between it's 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.
> 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
> 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)