hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9820) RPCv9 wire protocol is insufficient to support multiplexing
Date Thu, 08 Aug 2013 15:41:48 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Daryn Sharp updated HADOOP-9820:

    Attachment: HADOOP-9820.patch

# Updated get*Stream comments per Sanjay
# Renamed classes for wrapped stream's per Luke
# Removed default buf size per me
#* I was using the RFC max for digest-md5 which is different than gssapi
#* It was the wrong value.  RAW_SEND_BUF is the correct value which is guaranteed to be set.
 Just to be sure, verified in the SASL md5 and krb5 clients.
# Once the SASL auth completes, _only_ SASL wrapped packets are allowed per Sanjay/Luke.
> RPCv9 wire protocol is insufficient to support multiplexing
> -----------------------------------------------------------
>                 Key: HADOOP-9820
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9820
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc, security
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HADOOP-9820.patch, HADOOP-9820.patch
> RPCv9 is intended to allow future support of multiplexing.  This requires all wire messages
to be tagged with a RPC header so a demux can decode and route the messages accordingly.
> RPC ping packets and SASL QOP wrapped data is known to not be tagged with a header.

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

View raw message