Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 226B418A41 for ; Fri, 21 Aug 2015 17:32:38 +0000 (UTC) Received: (qmail 79845 invoked by uid 500); 21 Aug 2015 17:32:38 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 79797 invoked by uid 500); 21 Aug 2015 17:32:38 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 79784 invoked by uid 99); 21 Aug 2015 17:32:37 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2015 17:32:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 521B4DFDA1 for ; Fri, 21 Aug 2015 17:32:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.898 X-Spam-Level: ** X-Spam-Status: No, score=2.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id q8yAEyzH-090 for ; Fri, 21 Aug 2015 17:32:36 +0000 (UTC) Received: from mail-io0-f169.google.com (mail-io0-f169.google.com [209.85.223.169]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id A506D21381 for ; Fri, 21 Aug 2015 17:32:35 +0000 (UTC) Received: by iodb91 with SMTP id b91so88943657iod.1 for ; Fri, 21 Aug 2015 10:32:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pjLpu1W/mUtw4urBmWMcexa0hjLWNHdPmLnTv+Wxb08=; b=Y5s9WUzA3+cLM9Lyzu5BLkPSV14cwrWufnFQCAuwPgxswaWSnb6CsifRwBePiI8kh2 oo8a7o3GE/SuMwwxDDDnywiZVmcEgfT6wzaY/gF7fBRnq+9ttIwlVVk/tP9HMSFOFiLu WijTcanRR0tPeJX2mFieDPazAIlwtFt0cnqDlZn3HbWZVLAiaq3tf13SiaBcz+EyEzJW sAOr99BqRDzJYJdgmcpGOmcpsj1gRJVIlcRaQZJCXVFt0bCh7PCcrfXKctz0pmW/bfQo SKBA97gLJnuGt+PGXMCgw05bMw/7IH+zZXvv6j+7vrVVnZnsHQG+8a3hyU1KkTxLs8UM mt2w== MIME-Version: 1.0 X-Received: by 10.107.19.81 with SMTP id b78mr9086780ioj.36.1440178354524; Fri, 21 Aug 2015 10:32:34 -0700 (PDT) Received: by 10.107.24.67 with HTTP; Fri, 21 Aug 2015 10:32:34 -0700 (PDT) In-Reply-To: <8d7d293d668a4938bf92916285cd5300@MSGOMA1DAG01Y.DMN1.FMR.com> References: <6a04304c4e944890877c47d891e2d57e@MSGOMA1DAG01Y.DMN1.FMR.com> <8d7d293d668a4938bf92916285cd5300@MSGOMA1DAG01Y.DMN1.FMR.com> Date: Fri, 21 Aug 2015 13:32:34 -0400 Message-ID: Subject: Re: Continuous crawl - add schedule to stop for maintenance window From: Karl Wright To: dev Content-Type: multipart/alternative; boundary=001a113f2d983c16a5051dd5a7ab --001a113f2d983c16a5051dd5a7ab Content-Type: text/plain; charset=UTF-8 Right. You can set this up with ONE record, if you do some calculations. The record should begin Monday at midnight, and go for some period of time until Saturday at 10AM. The number of minutes the job can run is: 5 * 24 * 60 + 10 * 60 minutes Karl On Fri, Aug 21, 2015 at 12:30 PM, Mcguinness, Cathal < Cathal.Mcguinness@fmr.com.invalid> wrote: > Thanks Karl, > I am still a little confused here. > I can add a schedule to run Monday to Friday, which is fine. > But how can I tell it to run on Saturday but only until 10 am? Is it a > matter of specifying the Maximum runtime parameter? > > Ultimately what I want is for the job to stop running at 10am on Saturday > and start running again first thing Monday. > > Regards > Cathal. > > -----Original Message----- > From: Karl Wright [mailto:daddywri@gmail.com] > Sent: 21 August 2015 5:07 > To: dev > Subject: Re: Continuous crawl - add schedule to stop for maintenance window > > Hi Cathal, > > You can have multiple schedule records, each defining a different time > window. It is the cumulative time window that MCF cares about, not what is > found in each individual record. > > Karl > > > On Fri, Aug 21, 2015 at 11:54 AM, Mcguinness, Cathal < > Cathal.Mcguinness@fmr.com.invalid> wrote: > > > Hi, > > What is the best way to configure a Continuous crawl job so as it will > not > > run within a defined maintenance window. > > This maintenance window is Saturday 10am until midnight Sunday. > > If I set a schedule but omit Sunday this will mean that the job will be > > running on Saturday during the maintenance window which is not desirable. > > What is the best approach here? Or is this type of configuration > > possible? I know we could go with pausing the job, but if possible would > > like the schedule to be in place. > > > > > > Regards > > Cathal. > > > > > --001a113f2d983c16a5051dd5a7ab--