From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e1162e60709210741y5938ec86vf1c55cf4288fdf46@mail.gmail.com> Date: Fri, 21 Sep 2007 07:41:19 -0700 From: "David Leimbach" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] plan9.bell-labs.com In-Reply-To: <676c3c4f0709210718v59962c8cyac3796a35ac04a1d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18316_7368851.1190385679105" References: <148d84a2031783580c949aaa7334e9d6@plan9.bell-labs.com> <3e1162e60709201434l45d8b2e7jcb97f268a0e78085@mail.gmail.com> <676c3c4f0709201540s2bb3a80ua4df1740e919935f@mail.gmail.com> <3e1162e60709210655t14235d6cn9c4d379deb6c1b77@mail.gmail.com> <676c3c4f0709210718v59962c8cyac3796a35ac04a1d@mail.gmail.com> Topicbox-Message-UUID: c352e5ce-ead2-11e9-9d60-3106f5b1d025 ------=_Part_18316_7368851.1190385679105 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 9/21/07, Richard Bilson wrote: > > > Venti arenas stored on S3, with locally hosted indexes? > > You can't just throw a whole arena into an S3 file, since the S3 API > doesn't support seeking within files. > > On the other hand, an S3 bucket is essentially a big hash table, and > so is venti. So I opted for the simple approach of storing the blocks > themselves in S3. Given that, a local index doesn't help much. A local > bloom filter probably would help, but for now my server is stateless > (aside from cache). > > Right now the server supports the basic venti api, but it falls over > if anything goes wrong on the connection. Once I make it more robust, > I'll put it in contrib for interested parties. I hadn't looked into this idea much beyond a moment of curiosity... Sounds like you've thought it out quite a bit though :-) once I get my plan 9 box back up and healthy (and possibly add to the ranks in my home network) I'd be very interested in taking a look. Dave ------=_Part_18316_7368851.1190385679105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 9/21/07, Richard Bilson <rcbilson@gmail.com> wrote:
> Venti arenas stored on S3, with locally hosted indexes?

You can't just throw a whole arena into an S3 file, since the S3 API
doesn't support seeking within files.

On the other hand, an S3 bucket is essentially a big hash table, and
so is venti. So I opted for the simple approach of storing the blocks
themselves in S3. Given that, a local index doesn't help much. A local
bloom filter probably would help, but for now my server is stateless
(aside from cache).

Right now the server supports the basic venti api, but it falls over
if anything goes wrong on the connection. Once I make it more robust,
I'll put it in contrib for interested parties.

I hadn't looked into this idea much beyond a moment of curiosity...  Sounds like you've thought it out quite a bit though :-)

once I get my plan 9 box back up and healthy (and possibly add to the ranks in my home network) I'd be very interested in taking a look.

Dave

 

------=_Part_18316_7368851.1190385679105--