hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Surendra Singh Lilhore (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12225) [SPS]: Optimize extended attributes for tracking SPS movements
Date Mon, 14 Aug 2017 19:50:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126301#comment-16126301

Surendra Singh Lilhore commented on HDFS-12225:

v1 :

1. This patch will set the xAttr on  the directory, for which SPS is called.
2. Introduced in new list {{pendingSPSxAttrInode}} in {{StoragePolicySatisfier.java}}. {{pendingSPSxAttrInode}}
keep the list of Inode which has SPS xAttr while loading the edits logs..
3. Once namenode will become active {{PendingSPSTaskScanner}} thread scan the  {{pendingSPSxAttrInode}}
queue and load files in {{storageMovementNeeded}} queue to satisfy the policy.
4. Added one more map {{pendingWorkForDirectory}} in {{StorageMovementNeeded}}. It will keep
the count of pending work for directory. Once all the work is done for directory it will remove
the SPS xAttr.

Please review..

> [SPS]: Optimize extended attributes for tracking SPS movements
> --------------------------------------------------------------
>                 Key: HDFS-12225
>                 URL: https://issues.apache.org/jira/browse/HDFS-12225
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Uma Maheswara Rao G
>            Assignee: Surendra Singh Lilhore
>         Attachments: HDFS-12225-HDFS-10285-01.patch
> We have discussed to optimize number extended attributes and asked to report separate
JIRA while implementing [HDFS-11150 | https://issues.apache.org/jira/browse/HDFS-11150?focusedCommentId=15766127&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15766127]
> This is the JIRA to track that work 
> For the context, comment copied from HDFS-11150
> {quote}
> [~yuanbo] wrote : I've tried that before. There is an issue here if we only mark the
directory. When recovering from FsImage, the InodeMap isn't built up, so we don't know the
sub-inode of a given inode, in the end, We cannot add these inodes to movement queue in FSDirectory#addToInodeMap,
any thoughts?{quote}
> {quote}
> [~umamaheswararao] wrote: I got what you are saying. Ok for simplicity we can add for
all Inodes now. For this to handle 100%, we may need intermittent processing, like first we
should add them to some intermittentList while loading fsImage, once fully loaded and when
starting active services, we should process that list and do required stuff. But it would
add some additional complexity may be. Let's do with all file inodes now and we can revisit
later if it is really creating issues. How about you raise a JIRA for it and think to optimize
> {quote}
> {quote}
> [~andrew.wang] wrote in HDFS-10285 merge time review comment : HDFS-10899 also the cursor
of the iterator in the EZ root xattr to track progress and handle restarts. I wonder if we
can do something similar here to avoid having an xattr-per-file being moved.
> {quote}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message