Changes between Version 2 and Version 3 of Ticket #671, comment 26


Ignore:
Timestamp:
2014-09-24T04:40:54Z (10 years ago)
Author:
Lcstyle
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #671, comment 26

    v2 v3  
    44As far as what happens if a node originally given a limit of for example 1TB and actually grows to this size, and afterwards an admin seeks to reduce the limit to 500GB, there should be some functionality that allows shares to be transferred or copied to other servers to accommodate the storage node's request to downsize or shrink.  It might take time to shrink the node, but at least it would provide the capability of a graceful way of resolving the issue.  I don't know if such functionality (or a FR for this functionality) already exists.
    55
    6 I've searched the tickets and so far haven't found any tickets referencing the following keywords : migrating, shrinking, shutting down, removing, disabling, etc.
    7 It would be useful to the grid eco-system to provide a way for storage nodes to gracefully shutdown by transferring their data to other nodes that are not participating already in storing parts of the data the downsized node is looking to migrate.
     6I've searched the tickets and so far haven't found any tickets referencing the following keywords or functionality: migrating, shrinking, shutting down, removing, disabling, etc.
     7
     8It would be useful to a grid to provide ways for storage nodes to shrink or gracefully shutdown by transferring their data to other nodes that are not participating already in storing parts of the data the downsized node is looking to migrate.