[sheepdog] sheepdog replica number question

Ruoyu liangry at ucweb.com
Mon May 5 10:57:06 CEST 2014


On 2014年05月05日 16:51, Liu Yuan wrote:
> On Mon, May 05, 2014 at 02:44:24PM +0800, Ruoyu wrote:
>> I think the user wants to change the existing replica number of
>> cluster or vdi.
>>
>> We also got the requirement and already achieved it. Currently, only
>> changing replica number is permitted. Changing erasure code is not
>> implemented.
>>
>> Some examples are as below.
>>
>> $ dog cluster copies 2
>>      __
>>     ()'`;
>>     /\|`  Caution! Changing the # of replica will affect
>>    /  |   all the VDIs to be created later.
>> (/_)_|_  Are you sure you want to continue? [yes/no]: yes
>> set the cluster's replica success.
> So this doesn't change the copy number of exsiting vdis?
No, 'dog cluster copies' does not change the replica number of existing vdi.
'dog vdi copies' do.
>
>> $ dog cluster info -s
>> Cluster status: running, auto-recovery enabled
>> Cluster store: plain with 2 redundancy policy
>>
>> Cluster created at Mon May  5 14:28:02 2014
>>
>> Epoch Time           Version
>> 2014-05-05 14:28:02      1 [127.0.0.1:7000, 127.0.0.1:7001, 127.0.0.1:7002]
>>
>> $ dog vdi copies test 3
>>      __
>>     ()'`;
>>     /\|`  Caution! Changing the # of replica will affect
>>    /  |   the specified VDI and trigger recovery.
>> (/_)_|_  Are you sure you want to continue? [yes/no]: yes
>> set the vdi's replica success.
>>
>> $ dog vdi list
>>    Name        Id    Size    Used  Shared    Creation time   VDI id
>> Copies  Tag
>>    test         0   12 MB   12 MB  0.0 MB 2014-05-05 14:29 7c2b25      3
>>
>> I think this feature sometimes is useful. If you think it is worth
>> to do it, I am glad to contribute the patch.
>>
> I agree. Feel free to submit the patch the mailing list.
>
> Thanks
> Yuan





More information about the sheepdog mailing list