Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 91E1DCDCA for ; Thu, 25 Jul 2013 16:52:12 +0000 (UTC) Received: (qmail 74354 invoked by uid 500); 25 Jul 2013 16:52:10 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 72836 invoked by uid 500); 25 Jul 2013 16:52:08 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 72821 invoked by uid 99); 25 Jul 2013 16:52:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 16:52:05 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kirkkosinski@gmail.com designates 209.85.220.49 as permitted sender) Received: from [209.85.220.49] (HELO mail-pa0-f49.google.com) (209.85.220.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 16:51:59 +0000 Received: by mail-pa0-f49.google.com with SMTP id bi5so2205690pad.8 for ; Thu, 25 Jul 2013 09:51:38 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=1Ggp+HbG3yJ7WmCifD5a/X/z8FDO3tFce/GEo3BMIuc=; b=oFGUTofInhCdbBKwPoJMILldj533l+I6bSLva2ais21zZYsUeAoA7Frao4YK/7+oEU cTUCh25sROQFK475W7+1/GiOajPzKB6+US2S4Cx1+xFguhs0WVUeOOhO5Mrh46KOvIwh LWqVSuB4vkyP5eZGwX37WiHRYUIL8unDtiUPJpBRWLXJ4SvuOJi81HilNyh2wrPC/qOK Y+J2S/aulBEx8T8c2H7CHJPKo+Ck+jr6KwOc2ammXUN97/7BHcLsq/itMXOV2S3I1LtR ERlT6XZN4Be6eMUy3ig+UQBod5lbqUsOIbsh9nExjQ/AD9y8aoSyfzkCV+hnk8uEJsmx WovA== X-Received: by 10.66.232.73 with SMTP id tm9mr27328539pac.159.1374771098046; Thu, 25 Jul 2013 09:51:38 -0700 (PDT) Received: from [172.20.0.56] (dsl081-233-032.lax1.dsl.speakeasy.net. [64.81.233.32]) by mx.google.com with ESMTPSA id vu5sm58698310pab.10.2013.07.25.09.51.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 25 Jul 2013 09:51:37 -0700 (PDT) Message-ID: <51F15797.6070606@gmail.com> Date: Thu, 25 Jul 2013 09:51:35 -0700 From: Kirk Kosinski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130705 Thunderbird/17.0.7 MIME-Version: 1.0 To: users@cloudstack.apache.org CC: Ahmad Emneina Subject: Re: Hosts in CloudStack's avoid set References: <8E70BEF1-AD97-46D3-B739-9A00CDC7C313@me.com> <20130724163953.GA3469@cloud-2.local> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Right. The "avoid set" error should be interpreted as "scroll up to find the real error". It is only a temporary state and indicates there was a failure earlier in the attempted action. So look at the log more carefully, or upload it on Pastebin and ask on the list. Best regards, Kirk On 07/24/2013 11:34 AM, Ahmad Emneina wrote: > I'll add onto Prasanna's email by saying avoid set is cleared on each > deploy vm. So if youre seeing that a lot, there's issues elsewhere. Reading > the log line by line when deploying is pretty helpful, you can see what > hosts are available for initial deploy, as well as storage pools. Usually > there is a reason given when assessing a host... avail cpu & mem, and host > tags matching. look for those specifically. > > > On Wed, Jul 24, 2013 at 9:39 AM, Prasanna Santhanam wrote: > >> On Wed, Jul 24, 2013 at 10:34:58AM -0600, Caleb Call wrote: >>> When I've seen this (and I've seen it a lot) I usually see that it >>> thinks it's missed a ping and so it puts the host in an avoid set. >>> I think the "health check" feature in CS needs a lot of work to be >>> much more reliable. Sometimes if I let the host sit long enough, it >>> will magically (there's no rhyme or reason to it) start working >>> again. My only sure fix has been pulling the host completely out of >>> Cloudstack and then re-adding it. >>> >>> >>> On Jul 23, 2013, at 11:18 PM, Indra Pramana wrote: >>> >>>> Dear all, >>>> >>>> Good day to you. >>>> >>>> From time to time, CloudStack will put a hypervisor host on avoid set >> and >>>> not willing to deploy VM on that host. >>>> >>>> === >>>> 2013-07-24 13:12:34,639 DEBUG [allocator.impl.FirstFitAllocator] >>>> (Job-Executor-2:job-672 FirstFitRoutingAllocator) Host name: hv-kvm-02, >>>> hostId: 28 is in avoid set, skipping this and trying other available >> hosts >>>> 2013-07-24 13:12:34,639 DEBUG [allocator.impl.FirstFitAllocator] >>>> (Job-Executor-2:job-672 FirstFitRoutingAllocator) Host name: hv-kvm-01, >>>> hostId: 32 is in avoid set, skipping this and trying other available >> hosts >>>> === >>>> >>>> 1. What are the possible reasons on why CloudStack would put a >> hypervisor >>>> host on avoid set? >> >> When CS decides to deploy a VM and sets its eyes on a host ie to say >> it has finalized a deployment destination for the VM it assumes >> everything will go through fine. If it doesn't and for some reason the >> VM deployment fails CS tries to avoid that host for further >> deployments. This is the notion of avoid set as I understand it. >> >>>> 2. How to manually force CloudStack to remove the hypervisor host from >> its >>>> avoid set? >>>> >>>> Looking forward to your reply, thank you. >>>> >>>> Cheers. >> >> -- >> Prasanna., >> >> ------------------------ >> Powered by BigRock.com >> >> >