[
https://issues.apache.org/jira/browse/HDFS-15099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010655#comment-17010655
]
Ayush Saxena edited comment on HDFS-15099 at 1/8/20 1:20 PM:
-------------------------------------------------------------
Shouldn't we throw {{ObserverRetryOnActiveException}} for all write operations
on Observer, we can add it in {{CheckOperation(op)}}?
Well technically that won't happen, but we can put it at a common place rather
than just tweaking at one place
was (Author: ayushtkn):
Shouldn't we throw {{ObserverRetryOnActiveException}} for all write operations
on Observer, we can add it in {{CheckOperation(op)}}?
> [SBN Read] getBlockLocations() should throw ObserverRetryOnActiveException on
> an attempt to change aTime on ObserverNode
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-15099
> URL: https://issues.apache.org/jira/browse/HDFS-15099
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.10.0
> Reporter: Konstantin Shvachko
> Priority: Major
>
> The precision of updating an INode's aTime while executing
> {{getBlockLocations()}} is 1 hour by default. Updates cannot be handled by
> ObserverNode, so the call should be redirected to Active NameNode. In order
> to redirect to active the ObserverNode should through
> {{ObserverRetryOnActiveException}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
