From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3A68813877A for ; Sun, 3 Aug 2014 20:06:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0B446E0818; Sun, 3 Aug 2014 20:05:53 +0000 (UTC) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C8B74E07B2 for ; Sun, 3 Aug 2014 20:05:51 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id u57so6676138wes.24 for ; Sun, 03 Aug 2014 13:05:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/Cpx1yF6EFN1UpXgnIUYfQr60BB6A7RCQJoNH4p3tAM=; b=tspswb9ZTyzdWgApkmh/pATLNOHkyDE3XGkQLo9nnbfOGTDw4tWzs/ZixCDd9ecwIK Quhjp62i18ekqeEqpvwchQg7zIZ7+YZIHPAko14wVfQzx2HXZkGegloc2aHiQCb40Ejf Hi1r8jnz5BQja0mjPjULAyDjlDoxx9rFdEZPiQJ8eg7lhdIePT0eKvxFcMQEWRvn5rN/ JaPyA7TPKs49TvcDHLPgmEJkw5LsT0825g7lrG8CoCYtyptyPKTpZwRhgX+REJn0AyDl ZRqnsvTIj3zkV4IVQrFd5D5AQRVd8nNujsp0z8qRXg7q4cA6WdxBve0w/WRfA1sx9ukX OZRQ== X-Received: by 10.194.188.46 with SMTP id fx14mr24954056wjc.112.1407096350430; Sun, 03 Aug 2014 13:05:50 -0700 (PDT) Received: from [172.20.0.41] (105-237-190-183.access.mtnbusiness.co.za. [105.237.190.183]) by mx.google.com with ESMTPSA id ez1sm33050968wib.15.2014.08.03.13.05.46 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Aug 2014 13:05:50 -0700 (PDT) Message-ID: <53DE95E2.9040303@gmail.com> Date: Sun, 03 Aug 2014 22:04:50 +0200 From: Alan McKinnon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Recommendations for scheduler References: <53DBCF34.6060601@gmail.com> <16363580.J1QuOUtA0j@andromeda> <7486488.GXbi5se7ee@andromeda> In-Reply-To: <7486488.GXbi5se7ee@andromeda> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: e1d6ff9d-71fc-4bfe-b4db-9c1c22f437c6 X-Archives-Hash: 158e885d88cc8bc86a5adfe48d8d5d25 On 03/08/2014 15:36, J. Roeleveld wrote: >> Maybe this "protocol" is not the most clever solution, but it is >> > one which could be implemented without lots of overhead: >> > Mainly, I was up to a "quick" solution which is working good enough >> > for me: If the server has no bugs, why should it die? >> > Moreover, if the server dies for some strange reasons, it is probably >> > safer to re-queue the jobs again, anyway. > With the kind of schedules I am working with (and I believe Alan will also end > up with), restarting the whole process from the start can lead to issues. > Finding out how far the process got before the service crashed can become > rather complex. Yes, very much so. My first concern is the database cleanups - without scheduler guarantees I'd need transactions in MySQL. -- Alan McKinnon alan.mckinnon@gmail.com