hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1291) Set OmKeyArgs#refreshPipeline flag properly to avoid reading from stale pipeline
Date Fri, 22 Mar 2019 19:38:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1291?focusedWorklogId=217410&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-217410
]

ASF GitHub Bot logged work on HDDS-1291:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Mar/19 19:37
            Start Date: 22/Mar/19 19:37
    Worklog Time Spent: 10m 
      Work Description: xiaoyuyao commented on pull request #639: HDDS-1291. Set OmKeyArgs#refreshPipeline
flag properly to avoid readi…
URL: https://github.com/apache/hadoop/pull/639
 
 
   …ng from stale pipeline. Contributed by Xiaoyu Yao.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 217410)
            Time Spent: 10m
    Remaining Estimate: 0h

> Set OmKeyArgs#refreshPipeline flag properly to avoid reading from stale pipeline
> --------------------------------------------------------------------------------
>
>                 Key: HDDS-1291
>                 URL: https://issues.apache.org/jira/browse/HDDS-1291
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Blocker
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After HDDS-1138, the OM client will not talk to SCM directly to fetch the pipeline info.
Instead the pipeline info is returned as part of the keyLocation cached by OM. 
>  
> In case SCM pipeline is changed such as closed, the client may get invalid pipeline exception.
In this case, the client need to getKeyLocation with OmKeyArgs#refreshPipeline = true to
force OM update its pipeline cache for this key. 
>  
> An optimization could be queue a background task to update all the keyLocations that
is affected when OM does a refreshPipeline. (This part can be done in 0.5)
> {code:java}
> oldpipeline->newpipeline{code}
>  



--
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


Mime
View raw message