Abstract: Client data corresponding to a single client can be stored. A decision to proceed with a defragmentation of two or more particular core groups can be determined. A destination core group to receive client data can be identified. At least one additional core group can be initiated to manage interim data write requests from the single client. Each of the two or more particular core groups can be closed to data write requests. A defragmentation of the two or more particular core groups can be performed by merging into the destination core group. The destination core group can be availed to data read and delete requests. The two or more fragmented core groups can be reallocated for other uses. The additional core groups continue to receive read and write requests. The destination core groups further can be merged and defragmented further.

Abstract: Client data corresponding to a single client can be stored. A decision to proceed with a defragmentation of two or more particular core groups can be determined. A destination core group to receive client data can be identified. At least one additional core group can be initiated to manage interim data write requests from the single client. Each of the two or more particular core groups can be closed to data write requests. A defragmentation of the two or more particular core groups can be performed by merging into the destination core group. The destination core group can be availed to data read and delete requests. The two or more fragmented core groups can be reallocated for other uses. The additional core groups continue to receive read and write requests. The destination core groups further can be merged and defragmented further.