If the machine run the introducer down,what can i do

[str4d]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

This is exactly why the I2P version of Tahoe-LAFS uses a
multi-introducer patch which allows multiple introducers to be used
for the same grid; introducers can go down indefinitely (a common
problem in I2P) without destroying the grid. But if all known
introducers go down, you still have the same problem of informing all
nodes of the new grid. (We also have a separate monitoring script that
pulls a list of known introducers from a volunteer and adds them
automatically; this just abstracts the failure point back a step).

There are relevant tickets on the Tahoe-LAFS bug tracker about both
the multi-introducer system, and a no-introducers system. One (or
both) of these should eventually get merged into Tahoe-LAFS.

str4d

On 03/11/2014 02:28 PM, Zancas Dearana wrote:
> On Sun, Mar 9, 2014 at 7:59 PM, xiao_s_yuan <xiao_s_yuan at 163.com>
> wrote:
> 
>> If the machine run the introducer down and can not run again,is
>> that means I should create a new introducer on the other machine
>> and change the furl in all the storage and client nodes? And If I
>> can still find the file or directory in the grid?
>> 
>> 
>> 
>> _______________________________________________ tahoe-dev mailing
>> list tahoe-dev at tahoe-lafs.org 
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>> 
>> 
> I think you are correct, you need a new introducer, and the nodes
> in the grid need to know its furl.
> 
> 
> 
> _______________________________________________ tahoe-dev mailing
> list tahoe-dev at tahoe-lafs.org 
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQEcBAEBCgAGBQJTHm+OAAoJENXeOJaUpGWyEmwH/24aPj/XmnZn9zH/PUPdMRO4
w1W3FoUF4lZHKhocqhMJnCrlVS+3SI2l4H5X0oc8RNeXsjzLyltlv1iExNuqd2Vd
0zgAZbllXKw36gNZtqWswrwqWYIbBK3qOiozJzB6iN9I8+HXUulMLp4dEbQ9uUOh
ZHGYugoSqSy5czSMr3hVgxbnye2OHSRdSbT6LkJXzsSReLKZssPZinWBzxeVlFMM
enPx3A13BG3/cKmfodZ/RByCOaLVoTk1eplKtiZkVuToQ5NFuEhZLRVzaDbVQOQ+
EAH+KNW+m6lk3+3kXMCGRfcWz5DZwpnih6SUv7jHjjejwyNIWHaol1V7jP/z6JQ=
=CUeg
-----END PGP SIGNATURE-----