storj/satellite
Ivan Fraixedes f420b29d35
[V3-1927] Repairer uploads to max threshold instead of success… (#2423)
* pkg/datarepair: Add test to check num upload pieces
  Add a new test for ensuring the number of pieces that the repair process
  upload when a segment is injured.
* satellite/orders: Don't create "put order limits" over total
  Repair must not create "put order limits" more than the total count.
* pkg/datarepair: Update upload repair pieces test
  Update the test which checks the number of pieces which are uploaded
  during a repair for using the same excess over the success threshold
  value than the implementation.
* satellites/orders: Limit repair put order for not being total
  Limit the number of put orders to be used by repair for only uploading
  pieces to a % excess over the successful threshold.
* pkg/datarepair: Change DataRepair test to pass again
  Make some changes in the DataRepair test to make pass again after the
  repair upload repaired pieces only until a % excess over success
  threshold.
  Also update the steps description of the DataRepair test after it has been
  changed, to match on what's now, besides to leave it more generic for
  avoiding having to update it on minimal future refactorings.
* satellite: Make repair excess optimal threshold configurable
  Add a new configuration parameter to the satellite for being able to
  configure the percentage excess over the optimal threshold, used for
  determining how many pieces should be repaired/uploaded, rather than
  having the value hard coded.
* repairer: Add configurable param to segments/repairer
  Add a new parameters to the segment/repairer to calculate the maximum
  number of excess nodes, based on the optimal threshold, that repaired
  pieces can be uploaded.
  This new parameter has been added for not returning more nodes than the
  number of upload orders for data repair satellite service calculate for
  repairing pieces.
* pkg/storage/ec: Update log message in clien.Repair
* satellite: Update configuration lock file
2019-07-12 00:44:47 +02:00
..
attribution internal/testrand: new package for random data (#2282) 2019-06-26 13:38:51 +03:00
console Project Payment methods (#2037) 2019-07-10 23:29:26 +03:00
inspector internal/testrand: new package for random data (#2282) 2019-06-26 13:38:51 +03:00
mailservice Use zap.Stringer instead of zap.String (#2223) 2019-06-18 01:37:43 +02:00
marketingweb satellite/rewards: nicer offers handling (#2390) 2019-07-10 13:12:40 -04:00
metainfo protocol: implement new piece signing and verification (#2525) 2019-07-11 16:51:40 -04:00
nodestats storagenode/nodestats: combine stats into single RPC call (#2455) 2019-07-08 17:33:43 +03:00
orders [V3-1927] Repairer uploads to max threshold instead of success… (#2423) 2019-07-12 00:44:47 +02:00
payments Project Payment methods (#2037) 2019-07-10 23:29:26 +03:00
rewards satellite/rewards: nicer offers handling (#2390) 2019-07-10 13:12:40 -04:00
satellitedb Replace base64 encoding for path segments (#2345) 2019-07-11 13:26:07 -04:00
vouchers Update vouchers to use time.Time instead of timestamp (#2478) 2019-07-08 13:07:30 -04:00
peer.go [V3-1927] Repairer uploads to max threshold instead of success… (#2423) 2019-07-12 00:44:47 +02:00