Changes between Version 2 and Version 4 of Ticket #2124


Ignore:
Timestamp:
2013-12-02T11:08:44Z (8 years ago)
Author:
amontero
Comment:

I'm not sure, since I'm unable to completely understand #1382. #1816 is also very interesting at GC time, which is next for my case. Notice that I'm interested in this setup for both upload and not only repair.

However, as #2107 is evolving, it might be what I need, so I'm fine with watching it until it is closed and come back here to see if makes this unnecessary.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2124 – Description

    v2 v4  
    11This feature is a proposed solution to #2107 and #2123.
    22
    3 I discussed some weeks ago a possible feature with Daira and Warner to help me achieve #2107. The solutions looks like easy enough to make for a newbie-coder-task like me. This is a constraint of this approach, but also looks to have its merit also because of its simplicity, IMO.
     3I discussed some weeks ago a possible feature with Daira and Warner to help me achieve #2123. The solutions looks like easy enough to make for a newbie-coder-task like me. This is a constraint of this approach, but also looks to have its merit also because of its simplicity, IMO.
    44
    55The solution would entail adding a "max_shares=n" setting in the "storage" config section of storage nodes (proposed names were checked with Daira and Warner).