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 "Wei-Chiu Chuang (JIRA)" <ji...@apache.org> on 2019/05/16 08:57:00 UTC
[jira] [Commented] (HDFS-14497) Write lock hold by metasave impact
following RPC processing
[ https://issues.apache.org/jira/browse/HDFS-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841136#comment-16841136 ]
Wei-Chiu Chuang commented on HDFS-14497:
----------------------------------------
How long does it take to metasave? IIRC it's around several minutes range for large clusters.
I don't think switching to read lock would help much. I've seen read-only RPCs holding lock for too long and cause failover. (e.g. deleteSnapshot)
> Write lock hold by metasave impact following RPC processing
> -----------------------------------------------------------
>
> Key: HDFS-14497
> URL: https://issues.apache.org/jira/browse/HDFS-14497
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: He Xiaoqiao
> Assignee: He Xiaoqiao
> Priority: Major
>
> NameNode meta save hold global write lock currently, so following RPC r/w request or inner-thread of NameNode could be paused if they try to acquire global read/write lock and have to wait before metasave release it.
> I propose to change write lock to read lock and let some read request could be process normally. I think it could not change informations which meta save try to get if we try to open read request.
> Actually, we need ensure that there are only one thread to execute metaSave, otherwise, output streams could meet exception especially both streams hold the same file handle or some other same output stream.
--
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