You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2008/08/06 03:50:44 UTC
[jira] Commented: (HADOOP-3905) Factor out a common interface for
edits log.
[ https://issues.apache.org/jira/browse/HADOOP-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620116#action_12620116 ]
Konstantin Shvachko commented on HADOOP-3905:
---------------------------------------------
HADOOP-3860 concluded particularly that edits log currently presents one of the main bottlenecks for the name-node performance.
Currently we can save edits records only into a file and are bound by hard drive performance.
We may try to stream edits e.g. into a database or another high performance system optimized for writes.
My primary focus though is to make it possible to stream records into a secondary name-node so that the latter could
always keep an up todate namespace state with a perspective of building an HA solution based on that.
> Factor out a common interface for edits log.
> --------------------------------------------
>
> Key: HADOOP-3905
> URL: https://issues.apache.org/jira/browse/HADOOP-3905
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.19.0
>
>
> Create a generic interface that would cover all edit log operations and be useful for implementing journaling functionality on different storage sources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.