Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 38B9E1730E for ; Fri, 10 Oct 2014 20:43:30 +0000 (UTC) Received: (qmail 77910 invoked by uid 500); 10 Oct 2014 20:43:29 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 77863 invoked by uid 500); 10 Oct 2014 20:43:29 -0000 Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list dev@aurora.incubator.apache.org Received: (qmail 77852 invoked by uid 99); 10 Oct 2014 20:43:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 20:43:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jcohen@twopensource.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qc0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 20:43:04 +0000 Received: by mail-qc0-f176.google.com with SMTP id r5so2574112qcx.21 for ; Fri, 10 Oct 2014 13:43:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=GpWupe8FfWmIz2a9l8nl0gAjdpjT1+b811aIooiYn5g=; b=H8BR3N/osMPTtgedTqloy/XQSLZTMXUzE4aUu4+Gpkl1aNeVjt7/w3H0QXBpb67eNW kmzm3yFcWGjVnAHx8U8xd3WaIp3gwKnVC4K02JRVWjkFGEz1aSG2Y8NsCFprVbW+PH49 CODrJptU8vrp3gKK3rJ81I4Ibac+ORqISnTbMkhSXNVeD6SAauNTpkeQ/vn4Z8RU2y5E hrIyOtXVUD3agxGndC9jJqnKPk4TFuNHSkpsWk4NsW4W1MtMzV+StD7WNIQbaWzs0u2X 2iDzMJeijU3lWeg/Ct5LEAMK0QEA2A9lxCRpLyfCN1LHAolcGUfdAxfVlXzps6ZF2Oa+ aIbA== X-Gm-Message-State: ALoCoQl8I7B8EgGdXyfqZY8N49BZ0HXDpT4wRf+f7s3DNLcg+0qe77jzV61TFUhCXey3ZCIXpMbT MIME-Version: 1.0 X-Received: by 10.224.127.131 with SMTP id g3mr13002359qas.81.1412973782864; Fri, 10 Oct 2014 13:43:02 -0700 (PDT) Received: by 10.140.96.183 with HTTP; Fri, 10 Oct 2014 13:43:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Oct 2014 13:43:02 -0700 Message-ID: Subject: Re: Proposal: External Update Coordination From: Joshua Cohen To: "dev@aurora.incubator.apache.org" Content-Type: multipart/alternative; boundary=001a11c1e2d267c8ec0505179818 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1e2d267c8ec0505179818 Content-Type: text/plain; charset=UTF-8 In theory when the user resumes they'd also resume monitoring (and thus resume heartbeats)? Maybe the resumeJobUpdate RPC needs to support pauseIfNoHeartbeatsAfterMs as well? I'm not sure what a monitoring/heartbeating service would do with its record of a paused job while it's paused. How would it know when to resume monitoring and sending heartbeats without some notification that the update itself has resumed? By the same token, if monitoring were to continue while an updated was paused and an alert were to fire, what action would the monitoring service take with regard to the paused update? On Fri, Oct 10, 2014 at 1:28 PM, David McLaughlin wrote: > - A heartbeatJobUpdate RPC is called with the matching update ID. > Scheduler resets countdown and responds with STOP > > Paused is a tricky state because the user can resume at any time. I'd > propose we have a different response here. You really don't want to "stop" > monitoring the update while it is in a non-terminal state. You might want > to be aware that your heartbeat is a no-op, though. > > On Fri, Oct 10, 2014 at 12:47 PM, Maxim Khutornenko > wrote: > > > Hi all, > > > > We are proposing a new feature for the scheduler updater, which you > > may find helpful. > > > > I have posed a brief feature summary here: > > > > > https://github.com/maxim111333/incubator-aurora/blob/hb_doc/docs/update-heartbeat.md > > > > Please, reply with your feedback/concerns/comments. > > > > Thanks, > > Maxim > > > --001a11c1e2d267c8ec0505179818--