[
https://issues.apache.org/jira/browse/HADOOP-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702012#comment-14702012
]
Hadoop QA commented on HADOOP-10300:
------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12706046/HADOOP-10300.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 71aedfa |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/7502/console |
This message was automatically generated.
> Allowed deferred sending of call responses
> ------------------------------------------
>
> Key: HADOOP-10300
> URL: https://issues.apache.org/jira/browse/HADOOP-10300
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ipc
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Labels: BB2015-05-TBR
> Attachments: HADOOP-10300.patch, HADOOP-10300.patch
>
>
> RPC handlers currently do not return until the RPC call completes and
> response is sent, or a partially sent response has been queued for the
> responder. It would be useful for a proxy method to notify the handler to
> not yet the send the call's response.
> An potential use case is a namespace handler in the NN might want to return
> before the edit log is synced so it can service more requests and allow
> increased batching of edits per sync. Background syncing could later trigger
> the sending of the call response to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
