[3.1 Beta] some questions

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

 



Hi Amar,

Thank you for your answering.

On 2010/10/02, at 16:08, Amar Tumballi wrote:

> Hi Tomoaski,
> 
> Answers Inline:
> 
> 1) Can I start/stop volumes from any servers?
> 
> I have 5 servers and a volume 'vol1'on them.
> It seems that 'gluster volume start vol1' returns immediately at
> head-001(10.200.20.1) but does not return at another servers.
> 
> 
> What is the status of command ? Can you see the process list and check if glusterfs processes are running per those bricks?


starting at head-001:

[root at head-001 ~]# gluster volume create vol1 10.200.20.1:/export 10.200.20.2:/export 10.200.20.3:/export 10.200.20.4:/export 10.200.20.5:/export
Creation of volume vol1 has been successful
[root at head-001 ~]# gluster volume info

Volume Name: vol1
Type: Distribute
Status: Created
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: 10.200.20.1:/export
Brick2: 10.200.20.2:/export
Brick3: 10.200.20.3:/export
Brick4: 10.200.20.4:/export
Brick5: 10.200.20.5:/export
[root at head-001 ~]# gluster volume start vol1
Starting volume vol1 has been successful
[root at head-001 ~]# ps ax | grep gluster
 3443 ?        Ssl    0:00 /usr/sbin/glusterd
15587 ?        Ssl    0:00 /usr/sbin/glusterfs --xlator-option vol1-server.listen-port=6971 -s localhost --volfile-id vol1.10.200.20.1.export -p /etc/glusterd/vols/vol1/run/10.200.20.1-export.pid --brick-name /export --brick-port 6971 -l /etc/glusterd/logs/bricks/export.log
15591 ?        Ssl    0:00 /usr/sbin/glusterfs -f /etc/glusterd/nfs/nfs-server.vol -p /etc/glusterd/nfs/run/nfs.pid -l /etc/glusterd/logs/nfs.log
15599 pts/3    S+     0:00 grep gluster
[root at head-001 ~]# gluster volume stop vol1
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume vol1 has been successful
[root at head-001 ~]# !ps
ps ax | grep gluster
 3443 ?        Ssl    0:00 /usr/sbin/glusterd
15609 pts/3    S+     0:00 grep gluster
[root at head-001 ~]# 

starting at head-002:

[root at head-002 ~]# ps ax | grep gluster
12915 ?        Ssl    0:00 /usr/sbin/glusterd
23008 pts/2    S+     0:00 grep gluster
[root at head-002 ~]# gluster volume info

Volume Name: vol1
Type: Distribute
Status: Stopped
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: 10.200.20.1:/export
Brick2: 10.200.20.2:/export
Brick3: 10.200.20.3:/export
Brick4: 10.200.20.4:/export
Brick5: 10.200.20.5:/export
[root at head-002 ~]# gluster volume start vol1
[root at head-002 ~]# !ps
ps ax | grep gluster
12915 ?        Ssl    0:00 /usr/sbin/glusterd
23098 pts/2    S+     0:00 grep gluster
[root at head-002 ~]# gluster volume info

Volume Name: vol1
Type: Distribute
Status: Stopped
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: 10.200.20.1:/export
Brick2: 10.200.20.2:/export
Brick3: 10.200.20.3:/export
Brick4: 10.200.20.4:/export
Brick5: 10.200.20.5:/export
[root at head-002 ~]# gluster volume start vol1
Starting volume vol1 has been unsuccessful

[root at head-002 ~]# !ps
ps ax | grep gluster
12915 ?        Ssl    0:00 /usr/sbin/glusterd
23116 pts/2    S+     0:00 grep gluster
[root at head-002 ~]# gluster volume info

Volume Name: vol1
Type: Distribute
Status: Stopped
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: 10.200.20.1:/export
Brick2: 10.200.20.2:/export
Brick3: 10.200.20.3:/export
Brick4: 10.200.20.4:/export
Brick5: 10.200.20.5:/export
[root at head-002 ~]# 


>  
> 
> 2) Can I expect same or higher I/O performance lower cpu usage compare to 3.0.5 ?
> 
> 
> Yes, but in few cases it may be reduced. With 3.1.0 our goal is mainly to bring in 'ease of use', more easier diagnosis, correctness and stability.. Performance of 'replicate' volumes are looked into as of now.

I see.
New user interface seems very good to me.
Since I have replicated block devices (cluster RAID-1 volumes), I don't specify replica option at 'gluster create' times.

>  
> 
> 3) When and what keys should I change the value? and how should I review the current values ?
> 
> volume set <VOLNAME> <KEY> <VALUE> - set options for volume <VOLNAME>
> 
> 
> http://www.gluster.com/community/documentation/index.php/GlusterFS_3.1beta#Volume_Set
> 
> We have made few more fixes after beta.. consider upgrading to our new QA releases from 
> 
> http://ftp.gluster.com/pub/gluster/glusterfs/qa-releases

I will try latests. 

> 
> Thanks for trying out 3.1 and reporting issues. We appreciate your feedbacks.
> 
> Regards,
> Amar

Best,

Tomo Sato


[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