[Bugs] [Bug 1457272] New: Old content on last node when using Cascade Geo Replication in a particular case
bugzilla at redhat.com
bugzilla at redhat.com
Wed May 31 12:39:30 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1457272
Bug ID: 1457272
Summary: Old content on last node when using Cascade Geo
Replication in a particular case
Product: GlusterFS
Version: 3.10
Component: geo-replication
Severity: high
Assignee: bugs at gluster.org
Reporter: guillaume.penin at sncf.fr
CC: bugs at gluster.org
Description of problem:
Using a 3 nodes Cascade Geo Replication Setup (node1 => node2 => node3), file
content is never updated on node3 after modification on node1 in this
particular case :
- Use a shell redirection to modify file content
- File size is the same as before
File attributes (modification time for example) are however OK.
Version-Release number of selected component (if applicable):
GlusterFS 3.10.2 on Ubuntu 16.04 LTS x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create a file on node1 (/bin/date "+%s" >
/export/repos/.monitoring_timestamp), it will be correctly replicated on node2
and node3
2. Modify file content with the same command on node1, it will be correctly
replicated on node2 but not on node3.
Actual results:
Node 1 :
Content => 1496233967
ls => 11893925174562343327 -rw-r--r-- 1 root root 11 May 31 14:32
/export/repos/.monitoring_timestamp
Node 2 :
Content => 1496233967
ls = 11893925174562343327 -rw-r--r-- 1 root root 11 May 31 14:32
/export/repos/.monitoring_timestamp
Node 3 :
Content => 1496233801
ls => 11893925174562343327 -rw-r--r-- 1 root root 11 May 31 14:32
/export/repos/.monitoring_timestamp
Expected results:
Node 1 :
Content => 1496233967
ls => 11893925174562343327 -rw-r--r-- 1 root root 11 May 31 14:32
/export/repos/.monitoring_timestamp
Node 2 :
Content => 1496233967
ls = 11893925174562343327 -rw-r--r-- 1 root root 11 May 31 14:32
/export/repos/.monitoring_timestamp
Node 3 :
Content => 1496233967
ls => 11893925174562343327 -rw-r--r-- 1 root root 11 May 31 14:32
/export/repos/.monitoring_timestamp
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list