Opened at 2007-12-19T18:39:30Z
Closed at 2007-12-19T19:13:40Z
#240 closed defect (invalid)
shares not uploaded to a server?
| Reported by: | zooko | Owned by: | zooko |
|---|---|---|---|
| Priority: | major | Milestone: | eventually |
| Component: | code | Version: | 0.6.1 |
| Keywords: | peer-selection | Cc: | |
| Launchpad Bug: |
Description
!AnonymousUserNumber23 created an introducer and two nodes on cygwin, using tahoe 0.6.1.
He observed that each node was connected to each other node according to their webui welcome pages.
He uploaded a file from one of them, the one named tgc2.
Shares were added to tgc2's storage subdir, but not to tgc1's.
After some discussion, he tried another upload, and this time shares were added equally to the two storage directories, as expected. Subsequent uploads displayed the same correct behavior.
We currently don't have a hypothesis as to why tgc1 didn't receive shares in the first upload. I'm requesting logs from !AnonymouUserNumber23. (He's uploading them to the v0.6.1 public TestGrid. :-))
Change History (1)
comment:1 Changed at 2007-12-19T19:13:40Z by zooko
- Resolution set to invalid
- Status changed from new to closed
Okay, we made a mistake in observation -- the shares were all going to the *other* peer, not to the same peer, and they were doing that on every upload. This is because of the default setting of "push_to_myself=False" in v0.6.1. Closing.