hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3211) JournalProtocol changes required for introducing epoch and fencing
Date Thu, 05 Apr 2012 23:08:23 GMT

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

Suresh Srinivas commented on HDFS-3211:

bq. You need to store the epoch persistently on disk to handle the case of journal daemon
restarts, I think. HDFS-3190 does a refactor to add a utility class you can use for this
I think that can be done in another jira. I was thinking of doing that in startLogSegment.
I think we are still discussing that. Once it is resolved, lets do a separate jira.

Also can you please look HDFS-3204. If you are busy, I will see if I can get it reviewed by
> JournalProtocol changes required for introducing epoch and fencing
> ------------------------------------------------------------------
>                 Key: HDFS-3211
>                 URL: https://issues.apache.org/jira/browse/HDFS-3211
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: Shared journals (HDFS-3092)
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-3211.txt, HDFS-3211.txt
> JournalProtocol changes to introduce epoch in every request. Adding new method fence
for fencing a JournalService. On BackupNode fence is a no-op. 

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


View raw message