[tahoe-dev] erasure code

[Yu Xiang]

Dear Zooko,
then do you know how tahoe decided to upload how many of the file chunks to
a certain server? I didnt see any algorithm to allocate chunks in the
source code, and also the load balancing server selection algorithm is not
seen in client-storage.py where should be related to this.

Can you give me some insight of how tahoe is doing this?

Your help will be high appreciated.

Best,
Yu


On Sat, May 25, 2013 at 12:02 AM, Zooko O'Whielacronx <zookog at gmail.com>wrote:

> On Sat, May 25, 2013 at 3:16 AM, Yu Xiang <xy336699 at gwu.edu> wrote:
> > Hi all,
> > I see that the tahoe is using (10,3) erasure coding, since the file is
> > broken into 10 chunks,
>
> That's right, but that is configurable. See
> https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/configuration.rst
>
>
> > does the current version of tahoe allows users to
> > setup how many chunks it would like to upload to a certain server?
>
> Not yet. To support that is the topic of
> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/ServerSelection
>
> Regards,
>
> Zooko
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130525/d2beb128/attachment.html>