You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Yiqun Lin (JIRA)" <ji...@apache.org> on 2018/05/23 02:48:00 UTC
[jira] [Commented] (HDFS-12978) Fine-grained locking while
consuming journal stream.
[ https://issues.apache.org/jira/browse/HDFS-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486627#comment-16486627 ]
Yiqun Lin commented on HDFS-12978:
----------------------------------
Hi [~shv], I don't think {{Long.MAX_VALUE}} is a appropriate value for {{DFS_HA_TAILEDITS_MAX_TXNS_PER_LOCK_DEFAULT}}, that means we should display this so long number in hdfs-default.xml file. Maybe we can just use -1 instead, that means we don't do any limitation for consuming transactions.
> Fine-grained locking while consuming journal stream.
> ----------------------------------------------------
>
> Key: HDFS-12978
> URL: https://issues.apache.org/jira/browse/HDFS-12978
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Priority: Major
> Attachments: HDFS-12978.001.patch
>
>
> In current implementation SBN consumes the entire segment of transactions under a single namesystem lock, which does not allow reads over a long period of time until the segment is processed. We should break the lock into fine grained chunks. In extreme case each transaction should release the lock once it is applied.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org