[
https://issues.apache.org/jira/browse/HDFS-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439719#comment-15439719
]
Uma Maheswara Rao G commented on HDFS-10794:
--------------------------------------------
HI [~rakeshr], Thank you for working on this. I think our Jenkins will pick it
up automatically based on patch name. Could you please follow our patch naming
convention?
Please check the section [naming your
patch|http://wiki.apache.org/hadoop/HowToContribute#Naming_your_patch]
{quote}
Patches for a non-trunk branch should be named
<jiraName>-<branchName>.<versionNum>.patch, e.g. HDFS-1234-branch-2.003.patch.
The branch name suffix should be the exact name of a git branch, such as
"branch-2". Jenkins will check the name of the patch and detect the appropriate
branch for testing.
{quote}
> [SPS]: Provide storage policy satisfy worker at DN for co-ordinating the
> block storage movement work
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-10794
> URL: https://issues.apache.org/jira/browse/HDFS-10794
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: HDFS-10794-00.patch
>
>
> The idea of this jira is to implement a mechanism to move the blocks to the
> given target in order to satisfy the block storage policy. Datanode receives
> {{blocktomove}} details via heart beat response from NN. More specifically,
> its a datanode side extension to handle the block storage movement commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
