Displaying 2 results from an estimated 2 matches for "halo_min_replicas".
2018 Feb 05
0
halo not work as desired!!!
...r-common.c:4803:find_worst_up_child] 0-test-halo-replicate-0: Found
worst up child (1) @ 140032933708544 ms latency
[2018-02-05 11:42:48.393803] D [MSGID: 0]
[afr-common.c:4903:__afr_handle_child_up_event] 0-test-halo-replicate-0:
Marking child 1 down, doesn't meet halo threshold (10), and >
halo_min_replicas (2)
.
.
.
I think these debug output means:
As the ping time for test-halo-client-1 (brick2) is (0.5ms) and it is not
under halo threshold (10 ms), this false decision for selecting bricks
happen to halo.
I can not set the halo threshold to 0 because:
#gluster vol set test-halo cluster.halo-max-l...
2018 Feb 04
2
halo not work as desired!!!
I have 2 data centers in two different region, each DC have 3 severs, I
have created glusterfs volume with 4 replica, this is glusterfs volume info
output:
Volume Name: test-halo
Type: Replicate
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 4 = 4
Transport-type: tcp
Bricks:
Brick1: 10.0.0.1:/mnt/test1
Brick2: 10.0.0.3:/mnt/test2
Brick3: 10.0.0.5:/mnt/test3
Brick4: 10.0.0.6:/mnt/test4