docs/frontends/webapi.txt: note that 'count-good-share-hosts' is computed incorrectly...
authordavid-sarah <david-sarah@jacaranda.org>
Sat, 11 Sep 2010 00:25:48 +0000 (17:25 -0700)
committerdavid-sarah <david-sarah@jacaranda.org>
Sat, 11 Sep 2010 00:25:48 +0000 (17:25 -0700)
docs/frontends/webapi.txt

index 2f6891958f9526879037c934530489bc0b1feef3..52c3c555334cb3093b9076053676b30b29ac4ac2 100644 (file)
@@ -1172,13 +1172,10 @@ POST $URL?t=check
      count-shares-good: the number of good shares that were found
      count-shares-needed: 'k', the number of shares required for recovery
      count-shares-expected: 'N', the number of total shares generated
-     count-good-share-hosts: the number of distinct storage servers with
-                             good shares. If this number is less than
-                             count-shares-good, then some shares are doubled
-                             up, increasing the correlation of failures. This
-                             indicates that one or more shares should be
-                             moved to an otherwise unused server, if one is
-                             available.
+     count-good-share-hosts: this was intended to be the number of distinct
+                             storage servers with good shares. It is currently
+                             (as of Tahoe-LAFS v1.8.0) computed incorrectly;
+                             see ticket #1115.
      count-wrong-shares: for mutable files, the number of shares for
                          versions other than the 'best' one (highest
                          sequence number, highest roothash). These are