[sheepdog-users] Several difficulties with sheepdog (from 0.4.0-0+tek2b-10 deb package)

[David Douard]

On 26/07/2012 16:39, icez network wrote:
> sheepdog v0.4.0 change the storage backend from 'simple' to 'farm' so
> that you required some manual task from 'good practices' (especially
> converting the storage backend from simple to farm).

Sure, I know that. The problems I describe occured on a functionnal
farm-backed cluster.


> 
> On Thu, Jul 26, 2012 at 9:27 PM, Bastian Scholz <nimrodxx at gmx.de
> <mailto:nimrodxx at gmx.de>> wrote:
> 
>     Sorry, if the mail arrives two times, used the wrong sender
>     Mailadress...
> 
>     Hi David,
> 
>     at the moment I shut down the complete cluster before
>     updating it (collie cluster shutdown)
> 
>     But I had some complete data losses too with the actual
>     debian package. At the moment I try to understand, why
>     this happens...

So I'm not alone...

Cheers,
David



>     Cheers
> 
>     Bastian
> 
>     Am 2012-07-26 15:54, schrieb David Douard:
> 
>         Hi,
> 
>         I'm trying the latest deb package made by Jens, and I encounter
>         problems: I cannot make the cluster accept IO.
> 
>         My main problem is that I find it very easy to loose my cluster;
>         almost
>         every time I try to shutdown the cluster, it ends with a
>         situation where
>         the cluster is corrupted (with  "Failed to read object
>         805a6c0500000000
>         No object found" kind of messages).
> 
>         I lost the data when I upgraded the deb packages for example, as
>         I use
>         in this context a cssh session, so all nodes are upgraded at the
>         same
>         time, and the upgrade provoque a restart of the sheepdog service.
> 
>         Is this behavior somewhat expected, since I do not follow some
>         kind of
>         "good practices"? What are theses good practices? Is sheepdog
>         "compatible" with sysadmin automating tools like puppet or salt
>         (that do
>         propagate changes to several nodes at a time)? How can I configure
>         something like automatic shutdown on power outage (I'm using
>         apcupsd)?
>         How do I restart my cluster after a shutdown? Can I just fire a
>         "service
>         sheepdog start" in a cssh session?
> 
>         I guess these questions are also somewhat related to the discussion
>         about the possibility to sheepdog to detect that a node is down
>         for a
>         short while, and not really failed, etc.
> 
>         So, how do you guys manage your sheepdog clusters so you don't loose
>         your data?
> 
> 
>     -- 
>     sheepdog-users mailing lists
>     sheepdog-users at lists.wpkg.org <mailto:sheepdog-users at lists.wpkg.org>
>     http://lists.wpkg.org/mailman/__listinfo/sheepdog-users
>     <http://lists.wpkg.org/mailman/listinfo/sheepdog-users>
> 
> 
> 
> 
> -- 
> Personal hosting by icez network
> http://www.thzhost.com
> 
> 


-- 
--
David DOUARD		LOGILAB
+33 1 45 32 03 12	david.douard at logilab.fr
+33 1 83 64 25 26	http://www.logilab.fr/id/david.douard

Formations - http://www.logilab.fr/formations
Développements - http://www.logilab.fr/services
Gestion de connaissances - http://www.cubicweb.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: david_douard.vcf
Type: text/x-vcard
Size: 302 bytes
Desc: not available
URL: <http://lists.wpkg.org/pipermail/sheepdog-users/attachments/20120726/ea5fdb9d/attachment-0004.vcf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.wpkg.org/pipermail/sheepdog-users/attachments/20120726/ea5fdb9d/attachment-0003.sig>