[
https://issues.apache.org/jira/browse/HDFS-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508993#comment-13508993
]
Colin Patrick McCabe commented on HDFS-4045:
--------------------------------------------
I think that Todd's idea of simply having a {{readOpRaw}} and writing the
resulting bytes to the HTTP[S] response stream directly makes a lot of sense.
That way, you don't have to create a new kind of {{EditLogOutputStream}} at all.
I see that the current change adds a rawBytes field to every {{FSEditLogOp}},
which can be accessed by clients of the {{EditLogInputStream}}. This seems
like a viable alternative approach to {{readOpRaw}}, though it's unfortunate
that it adds some overhead to the regular loading path. I would not make this
field protected, though-- perhaps make it private and add an accessor. This is
just a possible idea-- I think you could equally well create {{readOpRaw}}.
> SecondaryNameNode cannot read from QuorumJournal URI
> ----------------------------------------------------
>
> Key: HDFS-4045
> URL: https://issues.apache.org/jira/browse/HDFS-4045
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Vinithra Varadharajan
> Assignee: Andy Isaacson
> Attachments: hdfs-4045-2.txt, hdfs4045-3.txt, hdfs4045-4.txt,
> hdfs-4045.txt
>
>
> If HDFS is set up in basic mode (non-HA) with QuorumJournal, and the
> dfs.namenode.edits.dir is set to only the QuorumJournal URI and no local dir,
> the SecondaryNameNode is unable to do a checkpoint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
