[tahoe-dev] Issue with Unplugging One Node from private grid

[Shawn Willden]

On Mon, Nov 29, 2010 at 12:41 PM, Bostonian <ygwen77 at gmail.com> wrote:

> The following is the architecture:
>
> 5 storage nodes + 1 introducer node + 1 client node (each of which is
> a desktop computer, running ubuntu 10.10)
>

So, seven total machines, all on a single network segment and subnet, right?


> In this case, I can connect to the client node, but cannot create any
> dir or download/upload any file. All the nodes still show connected
> from the gateway.
>

What error message(s) do you get when you try to perform these operations?


> Based on these tests, here are my guesses:
>
> i) when stopping tahoe, it pro-actively notifies introducer about its
> leave.
>
> ii) when unplugging the cable, introducer does not know that one node
> leaves. As a result, it still tries to connect it when requests.
>
> This seems to an bug with Tahoe. Given the nature of the system, it
> will see this situation quite often. Is there any monitoring mechanism
> at introducer?
>

The introducer isn't involved in uploading or downloading of files.  You can
even take the introducer off-line, and all of the nodes that already know
about one another will continue to work fine, so I don't think it's related
to that.

-- 
Shawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20101129/287203c7/attachment-0001.html>