[
https://issues.apache.org/jira/browse/HDFS-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Li updated HDFS-3186:
-----------------------------
Attachment: HDFS-3186.HDFS-3092.patch
The basic mechanism is like the following:
The journal service spawns a sync thread to download journal segments form
other journal services. The sync thread contacts other journal services one by
one until it can sync all the missed journal segments.
After the synchronization is done, the sync thread changes the journal service
state from SYNCING to IN_SYNC, and then blocks itself. The journal service
wakes up the sync thread to do another round of synchronization when its state
transits from WAITING_FOR_ROLL to SYNCING.
Here is the journal service state auto-machine
https://issues.apache.org/jira/secure/attachment/12524775/JNStates.png
> Sync lagging journal service from the active journal service
> ------------------------------------------------------------
>
> Key: HDFS-3186
> URL: https://issues.apache.org/jira/browse/HDFS-3186
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Reporter: Hari Mankude
> Assignee: Brandon Li
> Attachments: HDFS-3186.HDFS-3092.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
