You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Zhitao Li (JIRA)" <ji...@apache.org> on 2017/04/27 20:04:04 UTC

[jira] [Commented] (MESOS-5946) Consider supporting compression for the event stream.

    [ https://issues.apache.org/jira/browse/MESOS-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987506#comment-15987506 ] 

Zhitao Li commented on MESOS-5946:
----------------------------------

Proposal:

Similar to how [grpc handles compression | https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md#requests ], the {{api/v1}} endpoint will add support to a new optional header {{Message-Accept-Encoding}}.

If this header is present with a supported value (initially only {{identity}} and {{gzip}}), each line in recordio response will be processed accordingly (no-op for {{identity}} which is the default case, and gzip-compressed for {{gzip}}).

> Consider supporting compression for the event stream.
> -----------------------------------------------------
>
>                 Key: MESOS-5946
>                 URL: https://issues.apache.org/jira/browse/MESOS-5946
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Anand Mazumdar
>            Assignee: Zhitao Li
>              Labels: mesosphere
>
> Currently, we support GZIP compression for HTTP based responses in Libprocess. However, for events streamed on the persistent connection (RecordIO encoded) for schedulers/executors/subscribers, we don't yet have support for compression. 
> We would need an implementation of GZIP/other compression technique that would work efficiently for streaming data and is not fixed length based.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)