[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2859: introducer client uses cache even if it doesn't have to

Tahoe-LAFS trac at tahoe-lafs.org
Thu Dec 29 19:44:42 UTC 2016


#2859: introducer client uses cache even if it doesn't have to
---------------------+---------------------------
 Reporter:  dawuud   |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  undecided
Component:  unknown  |        Version:  1.12.0
 Keywords:           |  Launchpad Bug:
---------------------+---------------------------
 Hello, I'm at 33c3 with str4d discussing the introducer client. He's
 report a connectivity ordering problem in #2858 however this also brought
 our attention to the currenct introducer client implementation: the
 introducer client connects to the cached storage servers even if the
 introducer is available. Is this a bug?

 Shouldn't the introducer client try and fail to connect to the introducer
 before using the introducer cache and connecting to the cache storage node
 addresses?

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2859>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list