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-3125) Add a service that enables JournalDaemon
Date Mon, 26 Mar 2012 17:50:30 GMT

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

Suresh Srinivas commented on HDFS-3125:

bq. The new patch needs to check state in journal(..) and startLogSegment(..), and verify(registration)
in startLogSegment(..). Otherwise, it looks good.
Currently theses states are for listener side only. The method calls above are received over
RPC call. Given that RPC server could be controlled from outside, the expectation is that
either Service stop has stopped RPC server or external application has stopped the server.

The missing functionality currently is - Service should unregister during stop. Currently
an errorReport of fatal is used as unregister. I was planning to add unregister method to
the protocol. If that is not needed, I can call errorReport in service#stop() method.
> Add a service that enables JournalDaemon
> ----------------------------------------
>                 Key: HDFS-3125
>                 URL: https://issues.apache.org/jira/browse/HDFS-3125
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-3125.patch, HDFS-3125.patch, HDFS-3125.patch
> In this subtask, I plan to add JournalService. It will provide the following functionality:
> # Starts RPC server with JournalProtocolService or uses the RPC server provided and add
JournalProtocol service. 
> # Registers with the namenode.
> # Receives JournalProtocol related requests and hands it to over to a listener.

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