Replication does not replicate the reference node on crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok thank you

On Fri, Nov 6, 2009 at 8:57 AM, Vikas Gorur <vikas at gluster.com> wrote:

> joel vennin wrote:
>
>> Hi ! I'm continuing to test glusterfs,
>>
>> I've a strange problem us replication in fact. My setup is prety easy,
>> i've
>> 3 nodes, and I want to make replication through this 3 nodes
>>
>> Basic configuration:
>>
>> volume mega-replicator
>>       type       cluster/replicate
>>       subvolumes zbrick1 zbrick2 zbrick3
>> end-volume
>>
>> The scenario:
>>
>> 1) I copy data to the gluster mount point: -> Data is copied on the 3
>> nodes
>> [OK]
>> 2) I kill zbrick2 glusterfs, I erase data on zbrick2, I remount glusterfs
>> mount point, do a ls -Rl on the mount point, data is replicated to zbrick2
>> [OK]
>> 3) I do exactly the same thing with zbrick1, when I mount again the
>> zbrick1,
>> I do a ls -Rl on the mount point and there is nothing, the directory is
>> empty.
>>    So I do a ls -Rl on the zbrick2 and on zbrick3, and I get the same
>> result, nothing on the mount point.
>>    Why ?
>>
>>
>>
>>
> This is a known issue for now:
>
> http://gluster.com/community/documentation/index.php/Understanding_AFR_Translator#Self-heal_of_a_file_that_does_not_exist_on_the_first_subvolume
>
> Vikas
>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux