From issues-return-90444-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Wed Feb 28 01:31:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 85CB5180651 for ; Wed, 28 Feb 2018 01:31:03 +0100 (CET) Received: (qmail 70929 invoked by uid 500); 28 Feb 2018 00:31:02 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 70920 invoked by uid 500); 28 Feb 2018 00:31:02 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 70917 invoked by uid 99); 28 Feb 2018 00:31:02 -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; Wed, 28 Feb 2018 00:31:02 +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 091EF1A06D0 for ; Wed, 28 Feb 2018 00:31:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 Vxq1XWbKffqn for ; Wed, 28 Feb 2018 00:31:01 +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 F23645F3B5 for ; Wed, 28 Feb 2018 00:31:00 +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 63AFAE00A7 for ; Wed, 28 Feb 2018 00:31:00 +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 1294E240AE for ; Wed, 28 Feb 2018 00:31:00 +0000 (UTC) Date: Wed, 28 Feb 2018 00:31:00 +0000 (UTC) From: "Sean Lair (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-10310) KVM hosts reboot if there is a short transient storage error MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sean Lair created CLOUDSTACK-10310: -------------------------------------- Summary: KVM hosts reboot if there is a short transient storag= e error Key: CLOUDSTACK-10310 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1031= 0 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the defa= ult.) Components: KVM Affects Versions: 4.10.0.0, 4.9.0 Reporter: Sean Lair If the KVM heartbeat file can't be written to, the host is rebooted, and th= us taking down all VMs running on it.=C2=A0 The code does try 5x times befo= re the reboot, but the there is not a delay between the retires, so they ar= e 5 simultaneous retries, which doesn't help.=C2=A0 Standard SAN storage HA= operations or quick network blip could cause this reboot to occur. Some discussions on the dev mailing list revealed that some people are just= commenting out the reboot line in their version of the CloudStack source. A better option (and a new PR is being issued) would be have it sleep betwe= en tries so it isn't 5x almost simultaneous tries.=C2=A0 Plus, instead of r= ebooting, the cloudstack-agent could just be stopped on the host instead.= =C2=A0 This will cause alerts to be issued and if the host is disconnected = long-enough, depending on the HA code in use, VM HA could handle the host f= ailure. The built-in reboot of the host seemed drastic -- This message was sent by Atlassian JIRA (v7.6.3#76005)