Hi
I just know someone must have seen this before
Geo-replication on 3.6.1, epel, Centos 6.6
Popen: ssh [2014-12-08 22:57:31.433468] E
[socket.c:2267:socket_connect_finish] 0-glusterfs: connection to
127.0.0.1:24007 failed (Connection refused)
Popen: ssh [2014-12-08 22:57:31.433484] T
Are you referring to something else in your request? Meaning, you want
/myfile, /dir1/myfile and /dir2/dir3/myfile to fall onto the same
bricks/subvolumes and that perchance is what you are looking for?
That is EXACTLY what I am looking for.
What are my chances?
BR
Jan
I think I have it.
Unless I’m totally confused, I can hash ONLY on the filename with:
glusterfs --volfile-server=a_server --volfile-id=a_volume \
--xlator-option a_volume-dht.extra_hash_regex='.*[/]' \
/a/mountpoint
Correct?
Jan
From: Jan H Holtzhausen j...@holtztech.info
Date
Hmm
Then something is wrong,
If I upload 2 identical files, with different paths they only end up on
the same server 1/4 of the time (I have 4 bricks).
I’ll test the regex quickly.
BR
Jan
On 2014/11/25, 7:55 PM, Shyam srang...@redhat.com wrote:
On 11/25/2014 02:28 PM, Jan H Holtzhausen
...@redhat.com wrote:
On 11/25/2014 03:11 PM, Jan H Holtzhausen wrote:
STILL doesn’t work … exact same file ends up on 2 different bricks …
I must be missing something.
All I need is for:
/directory1/subdirectory2/foo
And
/directory2/subdirectoryaaa999/foo
To end up on the same brick
As to the why.
Filesystem cache hits.
Files with the same name tend to be the same files.
Regards
Jan
On 2014/11/25, 8:42 PM, Jan H Holtzhausen j...@holtztech.info wrote:
So in a distributed cluster, the GFID tells all bricks what a files
preceding directory structure looks like?
Where
I could tell you…
But Symantec wouldn’t like it…..
From: Poornima Gurusiddaiah pguru...@redhat.com
Date: Wednesday 26 November 2014 at 7:16 AM
To: Jan H Holtzhausen j...@holtztech.info
Cc: gluster-devel@gluster.org
Subject: Re: [Gluster-devel] EHT / DHT
Out of curiosity, what back end
