[tahoe-dev] erasure code

[Yu Xiang]

Dear all,
Thanks for your kindly help on this issue, I did see in the source code
storage-client.py, the roadmap in the beginning says "4: enable static
config: tahoe.cfg can add descriptors. Make the introducer optional. This
closes #467", and ticket 467 is about how to set which server you would
like to upload to in tahoe.cfg in the very beginning, that ticket doesnt
seem to have a solution in the ticket page, has this issue already been
solved in the current version of tahoe in storage-client.py? Since i didnt
see the prefered peer setup part in tahoe.cfg file when node created.

Any help would be highly appreciated!

Best,
Yu


On Sat, May 25, 2013 at 1:30 AM, Oleksandr Drach <luckyredhot at gmail.com>wrote:

> Dear Yu,
>
> Here is the reply on server selection:
> " The current system will try to distribute the shares as widely as
> possible, using a different pseudo-random permutation for each file, but it
> is completely unaware of server properties like "location". If you have
> more free servers than shares, it will only put one share on any given
> server, but you might wind up with more shares in one location than the
> others."
>
> It can be found in FAQ:
> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/FAQ#Q12_server_location_distribution
> .
>
> Should you have further questions feel free to ask them!
> On May 25, 2013 7:22 AM, "Yu Xiang" <xy336699 at gwu.edu> wrote:
>
>> 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
>>>
>>
>>
>> _______________________________________________
>> tahoe-dev mailing list
>> tahoe-dev at tahoe-lafs.org
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>
>>
> _______________________________________________
> 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/4824fcdf/attachment.html>