On 07/07/2014 06:58 PM, Gurdeep Singh
(Guru) wrote:
Hello Pranith,
The version I am using is 3.5.1.1
I did a wireshark capture and from looking at gluster
information found that RPC lookup is being made for random
files.
In other response Niels pointed out how to check for it.
You can also attach the capture file so that we can take a look at
it.
Pranith
Gurdeep.
On 07/06/2014 06:58 PM,
Gurdeep Singh (Guru) wrote:
Hello,
I have setup gluster in replicate type and its
working fine.
I am seeing a constant chatting between the hosts
for lookup call and lookup reply. I am trying to
understand as to why this traffic is being initiated
constantly. Please look at the attached image. This
traffic is using around 200KB/s of constant bandwidth
and is exhausting our allocated monthly bandwidth on
our 2 VPS.
Self-heal-daemon tries to check if there is anything that
needs healing every 10 minutes. Those RPCs are lookups.
Could you check from the tcpdump if it is generating from
self-heal-daemon? Which version of gluster are you using?
I think there is a way to increase this 'time' in latest
versions.
Pranith
The configuration I have for Gluster is:
[guru@srv1 ~]$ sudo gluster volume
info
[sudo] password for guru:
Volume Name: gv0
Type: Replicate
Volume ID:
dc8dc3f2-f5bd-4047-9101-acad04695442
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: srv1:/root/gluster-vol0
Brick2: srv2:/root/gluster-vol0
Options Reconfigured:
cluster.lookup-unhashed: on
performance.cache-refresh-timeout: 60
performance.cache-size: 1GB
storage.health-check-interval: 30
<Mail Attachment.png>
Please suggest how to fine tune the RPC
calls/reply.
Thanks,
Gurdeep.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
