Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9B418200CFA for ; Tue, 5 Sep 2017 10:41:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 940BF1657F1; Tue, 5 Sep 2017 08:41:20 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E3BA61657EE for ; Tue, 5 Sep 2017 10:41:19 +0200 (CEST) Received: (qmail 41397 invoked by uid 500); 5 Sep 2017 08:41:18 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 41381 invoked by uid 99); 5 Sep 2017 08:41:18 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Sep 2017 08:41:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2CC011A2BF2 for ; Tue, 5 Sep 2017 08:41:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KA6ruq9AygF2 for ; Tue, 5 Sep 2017 08:41:13 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7EED7612A3 for ; Tue, 5 Sep 2017 08:41:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A18EDE0F15 for ; Tue, 5 Sep 2017 08:41:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id CD5C724166 for ; Tue, 5 Sep 2017 08:41:02 +0000 (UTC) Date: Tue, 5 Sep 2017 08:41:02 +0000 (UTC) From: "Alexander Rukletsov (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MESOS-7931) LibeventSSLSocket send does not expose progress. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 05 Sep 2017 08:41:20 -0000 [ https://issues.apache.org/jira/browse/MESOS-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rukletsov updated MESOS-7931: --------------------------------------- Labels: (was: reliability) > LibeventSSLSocket send does not expose progress. > ------------------------------------------------ > > Key: MESOS-7931 > URL: https://issues.apache.org/jira/browse/MESOS-7931 > Project: Mesos > Issue Type: Bug > Components: libprocess > Reporter: Benjamin Mahler > > Currently, {{LibeventSSLSocket::send(const char* data, size_t size)}}, unlike {{PollSocket}} and the POSIX socket API, will only return once all of the data has been written. The caller is unable to see if some progress could be made on writing the data. > This is problematic. For example, if we want to implement a send timeout, we cannot cancel the timeout when progress is made, since we're only notified when the whole send finishes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)