9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FileServer grid
Date: Sat,  7 Feb 2009 23:57:21 +0100	[thread overview]
Message-ID: <5d375e920902071457q34f69810rbdf6771613f9f824@mail.gmail.com> (raw)
In-Reply-To: <e1d437a40902070932g64ee093rcaff9f2b7ec23a2e@mail.gmail.com>

The link is *not* broken, plan9.bell-labs.com is, sadly and
unsurprisingly, broken.

uriel

On Sat, Feb 7, 2009 at 6:32 PM, Giacomo Tesio <giacomo@tesio.it> wrote:
> I'd like to move our softwares to Linux + Apache (where mounting a 9p
> fileserver would be easy), but actually it's a Windows + IIS.
>
> I would write a session state service for ASP.NET connecting it in 9p (using
> c# and the 9pc implementation linked by
> http://9p.cat-v.org/implementations... actually the link is broken...)
>
> If the filesystem grid work as I've understood, there would be only ONE
> filesystem.
>
> So, saving session state in the grid would make it available to all web
> servers connected to the filesystem, allowing load balance and high
> availability for the web servers (when one crash, the user sessions it was
> handling would be available to the others web server).
>
> But what if a node of the grid goes down? There would be a way to keep files
> in it replicated in other cpu node?
>
>
> Giacomo
>
> On Fri, Feb 6, 2009 at 11:41 PM, Roman V. Shaposhnik <rvs@sun.com> wrote:
>>
>> On Fri, 2009-02-06 at 23:26 +0100, Giacomo Tesio wrote:
>> > Hello every one...
>> > In a context of really heavy load and high availability needs, I'm
>> > evaluating plan 9 to implement a fileserver grid to be used by a web
>> > server for temporary storage (session's serializations, for example).
>>
>> What OS do you web servers run under?
>>
>> > I'd like to build a Plan 9 grid exposing a unique filesystem mounted
>> > by all the web servers.
>>
>> Are you going to talk to this filesystem using 9P or something else?
>>
>> > Each session could be accessible from any web server instantly, but
>> > what if a fileserver in the grid break?
>> > Is there a way to mantain such a session (actually the file storing
>> > the session data) available by keeping it sincronized beetween the
>> > Plan 9 fileservers?
>>
>> This is unclear. Please restate.
>>
>> Thanks,
>> Roman.
>>
>>
>
>



  reply	other threads:[~2009-02-07 22:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 22:26 Giacomo Tesio
2009-02-06 22:41 ` Roman V. Shaposhnik
2009-02-07 17:32   ` Giacomo Tesio
2009-02-07 22:57     ` Uriel [this message]
2009-02-07 23:00       ` erik quanstrom
2009-02-08  1:43         ` Uriel
2009-02-08 15:24       ` Giacomo Tesio
2009-02-08 17:12         ` ron minnich
2009-02-09  8:12           ` Giacomo Tesio
2009-02-10  3:52     ` Roman Shaposhnik
2009-02-10  8:06       ` Giacomo Tesio
2009-02-10 16:37         ` ron minnich
2009-02-10 21:41           ` Giacomo Tesio
2009-02-11  7:05             ` Skip Tavakkolian
2009-02-10 22:03         ` Roman V. Shaposhnik
2009-02-25  0:09     ` Enrico Weigelt
2009-02-06 22:53 ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d375e920902071457q34f69810rbdf6771613f9f824@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).