This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Xen clustering

To: sadegh <mshoosh@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen clustering
From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Date: Thu, 01 Nov 2007 15:30:29 +0000
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 01 Nov 2007 08:29:55 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=EFuFOrkAH2YyRi/2h/JJPEFUuc8fLH4tyqX6GM60eag=; b=Q6QDYdzNgAH0otQXVRGGll1B4SSU7lGIlSPetTXTLR8IQJswRl+/gJgfcfldy1IghmXkszvIMRgO+USjYlgjCJ8D7h6F5ENRKkZJGjA8j+fHLMZAswL/NxCTkZjcNJ5YXCtE1MeEkSzkeeRZpVwqek0lF3WgU5luDqgMS48FVHg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Yzyt01d0M3mOIWyvGGFPoA0LzIghfaTXnXj2dOX44/C+uzOwDCu4XLCAzemHkwqQKfrRUaYpeuH7Vna692MTT/knqhuwvEELBYlRd2UlmPJllmDLvxMuifvipDyeCWuVfyzExpyFl3kIfbKUO/NZAbK7u7UCMh3vmwDsOG98iVA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <472A7C34.8040206@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <7fedbc910710310714t3e68a2earf816e470250300c9@xxxxxxxxxxxxxx> <47289EAE.9020407@xxxxxxxxx> <Pine.LNX.4.64.0710310951330.11273@localhost> <472A7C34.8040206@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20070809)
sadegh wrote:

Hi All,
well , if we say FailOver mechanism is stop one and restart another node it is true but if FailOver definition is Migration from one node to another.
What is your idea about it?
Slow down a moment. Failover means different things to different people. A full so-called "High Availability" solution, where each individual component can fail but the rest automatically switch the resources they're using, is useful sometimes but seriously expensive to implement, and the switchover mechanisms themselves create their own uncertainties.

increasing redundant hardwares is it?
It's part of an integrated solution. The redundant hardware has to be cross-wired in usable failover setups for individual setups. Xen can be a very useful component for this, because the potentially more reliable centralized storage system can be made extremely robust and the servers swap domains as necessary to other working hardware.
and if we have proactive fault detection mechanism we can do it.
Yes, but there are limits to this. Janitors blow fuses: cage monkeys accidentally crimp fiber, or disconnect idle connections. And hard drives fail without any warning whatsoever, even a few at a time. There's a white paper from Google on this I highly recommend, where roughly 30% of the drives fail without any SMART detection at all.

some related works exist.
My thesis is about this subject "Improving Survivability of HA Clusters" (that Mission-Critical apps. runs on...) if any body help me to Hacking Xen, heartbeat and implementing some other tools and compare results we can publishing some Papers about this and have friendly work group!
I am ready to contribute and very appreciate.
Best Regards
Ohhhh. Cool. It's not clear how much you need Xen for this, as much as integration of Xen with the available approaches.

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>