[
https://issues.apache.org/jira/browse/HDFS-11264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080492#comment-16080492
]
Rakesh R commented on HDFS-11264:
---------------------------------
Added extra Mover status check after updating the {{SPS#isRunning=true}}, which
will ensure that Mover will not start after SPS startup. With this, below is
the startup flow at both ends,
+Mover Tool:+
1) creates {{/system/mover.id}} path
2) check SPS running status
3) if SPS running then Mover exists by deleting path .
+SPS service:+
1) check Mover status by checking {{/system/mover.id}} path existence
2) update {{SPS#isRunning=true}}
3) check Mover status by checking {{/system/mover.id}} path existence
4) if Mover instance exists then stop SPS by setting {{SPS#isRunning=false}}
> [SPS]: Double checks to ensure that SPS/Mover are not running together
> ----------------------------------------------------------------------
>
> Key: HDFS-11264
> URL: https://issues.apache.org/jira/browse/HDFS-11264
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Reporter: Wei Zhou
> Assignee: Rakesh R
> Attachments: HDFS-11264-HDFS-10285-01.patch
>
>
> As discussed in HDFS-10885, double checks needed to insure SPS/Mover not
> running together, otherwise it may cause some issues.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
