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

Rakesh R commented on HDFS-10885:
---------------------------------

Thanks [~zhouwei], [~umamaheswararao] for the dscussions.

bq. How about we use mover id file for communicating this.
Since both the process are distributed {{/system/mover.id} based logic would 
work well. Presently {{Mover tool}} is writing the host name details into this 
file, this could be used for logging inside SPS to know the already running 
instance.

{code}
NameNodeConnector#checkAndMarkRunning()

        fsout.writeBytes(InetAddress.getLocalHost().getHostName());
{code}

bq. Anyway HSM is already depending on Xattr for storing policy ids. 
Exactly, SPS has dependency with Xattr, so we could do a check during SPS 
startup as well.

Adding another point to consider, dynamically enable/disable SPS without making 
NN restart. Are you planning to address this use case as part of this jira. 

> [SPS]: Mover tool should not be allowed to run when Storage Policy Satisfier 
> is on
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-10885
>                 URL: https://issues.apache.org/jira/browse/HDFS-10885
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>    Affects Versions: HDFS-10285
>            Reporter: Wei Zhou
>            Assignee: Wei Zhou
>             Fix For: HDFS-10285
>
>         Attachments: HDFS-10800-HDFS-10885-00.patch, 
> HDFS-10800-HDFS-10885-01.patch, HDFS-10800-HDFS-10885-02.patch, 
> HDFS-10885-HDFS-10285.03.patch, HDFS-10885-HDFS-10285.04.patch
>
>
> These two can not work at the same time to avoid conflicts and fight with 
> each other.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to