You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2012/05/07 19:42:48 UTC
[jira] [Commented] (ACCUMULO-578) consider using hdfs for the walog
[ https://issues.apache.org/jira/browse/ACCUMULO-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269809#comment-13269809 ]
Todd Lipcon commented on ACCUMULO-578:
--------------------------------------
bq. we don't have fine-grained insight when a single node makes dfs slow
See HDFS-3170 for some ideas here.
> consider using hdfs for the walog
> ---------------------------------
>
> Key: ACCUMULO-578
> URL: https://issues.apache.org/jira/browse/ACCUMULO-578
> Project: Accumulo
> Issue Type: Improvement
> Components: logger, tserver
> Affects Versions: 1.5.0-SNAPSHOT
> Reporter: Eric Newton
> Assignee: Eric Newton
>
> Using HDFS for walogs would fix:
> * ACCUMULO-84: any node can read the replicated files
> * ACCUMULO-558: wouldn't need to monitor loggers
> * ACCUMULO-544: log references wouldn't include hostnames
> * ACCUMULO-423: wouldn't need to monitor loggers
> * ACCUMULO-258: hdfs has load balancing already
> To implement it, we would need the ability to distribute log sorts.
> Continuing to use loggers helps us avoid:
> * hdfs pipeline strategy
> * we don't have fine-grained insight when a single node makes dfs slow
> * additional namenode pressure
> * flexibility: for example, we can add fadvise() calls to the logger before HDFS supports it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira