You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/07/31 23:52:20 UTC
[jira] [Updated] (MESOS-5946) Consider supporting compression for
the event stream.
[ https://issues.apache.org/jira/browse/MESOS-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anand Mazumdar updated MESOS-5946:
----------------------------------
Description:
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.
was: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.
> 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
> 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.4#6332)