[
https://issues.apache.org/jira/browse/HDFS-15313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158491#comment-17158491
]
Hadoop QA commented on HDFS-15313:
----------------------------------
| (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} 18m
4s{color} | {color:red} Docker failed to build yetus/hadoop:b98299bc57c.
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-15313 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13007712/HDFS-15313.branch-2.8.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/29512/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |
This message was automatically generated.
> Ensure inodes in active filesytem are not deleted during snapshot delete
> ------------------------------------------------------------------------
>
> Key: HDFS-15313
> URL: https://issues.apache.org/jira/browse/HDFS-15313
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 3.2.2, 3.3.1, 3.4.0
>
> Attachments: HDFS-15313.000.patch, HDFS-15313.001.patch,
> HDFS-15313.branch-2.8.patch, HDFS-15313.branch-3.1.patch
>
>
> After HDFS-13101, it was observed in one of our customer deployments that
> delete snapshot ends up cleaning up inodes from active fs which can be
> referred from only one snapshot as the isLastReference() check for the parent
> dir introduced in HDFS-13101 may return true in certain cases. The aim of
> this Jira to add a check to ensure if the Inodes are being referred in the
> active fs , should not get deleted while deletion of snapshot happens.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]