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

Hadoop QA commented on HDFS-11572:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red}  0m  
6s{color} | {color:red} Docker failed to build yetus/hadoop:a9ad5d6. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-11572 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12863510/HDFS-11572-HDFS-10285-00.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/19093/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> [SPS]: SPS should clean Xattrs when no blocks required to satisfy for a file
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-11572
>                 URL: https://issues.apache.org/jira/browse/HDFS-11572
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS-10285
>            Reporter: Uma Maheswara Rao G
>            Assignee: Uma Maheswara Rao G
>         Attachments: HDFS-11572-HDFS-10285-00.patch
>
>
> When user calls on a file to satisfy storage policy, but that file already 
> well satisfied. This time, SPS will just scan and make sure no blocks needs 
> to satisfy and will leave that element. In this case, we are not cleaning 
> Xattrs. This is the JIRA to make sure we will clean Xattrs in this situation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to