bugGluster - Bugs: bug #25470, Glusterfs 2.0.0rc1 - Write-Behind...

 
 

bug #25470: Glusterfs 2.0.0rc1 - Write-Behind not taking aggregate-size setting.

Submitter:  None
Submitted:  Mon 02 Feb 2009 09:47:23 PM UTC
   
 
Category:  GlusterFS Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Improper behaviour
Status:  Fixed Privacy:  Public
Assigned to:  amarts Originator Name:  *
Originator Email:  * -email is unavailable- Open/Closed:  Closed
Release:  2.0.0rc1 Operating System:  GNU/Linux
Reproducibility:  Every Time
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 02 Feb 2009 11:49:41 PM UTC, comment #1: 

Thanks for the report. This is fixed now in 'glusterfs--mainline--3.0--patch-887', should be fixed in 2.0.0rc2 planned next week.

Regards,
Amar

Amar Tumballi <amarts>
Group Member
Mon 02 Feb 2009 09:47:23 PM UTC, original submission:  

Setting the option aggregate-size in the Write-behind translator isn't being taken and defaults back to 0.  Same client configuration on 1.3.12 running in DEBUG mode shows the "using aggregate-size = 131072"

writebehind: using aggregate-size = 0




Version      : glusterfs 2.0.0rc1 built on Feb  2 2009 15:28:25
TLA Revision : glusterfs--mainline--3.0--patch-844
Starting Time: 2009-02-02 15:39:33
Command line : /usr/local/glusterfs-2.0.0rc1-DEBUG/sbin/glusterfs -f /etc/glusterfs/glusterfs-client-test.vol /mnt/glusterfs -L DEBUG -N
given volfile
+-----
  1: volume bricktest
  2:   type protocol/client
  3:   option transport-type tcp/client
  4:   option remote-host 192.168.201.103
  5:   option remote-subvolume bricktest
  6:   option remote-port 6997
  7: end-volume
  8:
  9: volume writebehind
 10:  type performance/write-behind
 11:  option aggregate-size 131072 # default is 0bytes
 12:  subvolumes bricktest
 13: end-volume
+-----
2009-02-02 15:39:33 D [spec.y:187:new_section] parser: New node for 'bricktest'
2009-02-02 15:39:33 D [xlator.c:421:xlator_set_type] xlator: attempt to load file /usr/local/glusterfs-2.0.0rc1-DEBUG/lib/glusterfs/2.0.0rc1/xlator/protocol/client.so
2009-02-02 15:39:33 D [spec.y:213:section_type] parser: Type:bricktest:protocol/client
2009-02-02 15:39:33 D [spec.y:288:section_option] parser: Option:bricktest:transport-type:tcp/client
2009-02-02 15:39:33 D [spec.y:288:section_option] parser: Option:bricktest:remote-host:192.168.201.103
2009-02-02 15:39:33 D [spec.y:288:section_option] parser: Option:bricktest:remote-subvolume:bricktest
2009-02-02 15:39:33 D [spec.y:288:section_option] parser: Option:bricktest:remote-port:6997
2009-02-02 15:39:33 D [spec.y:372:section_end] parser: end:bricktest
2009-02-02 15:39:33 D [spec.y:187:new_section] parser: New node for 'writebehind'
2009-02-02 15:39:33 D [xlator.c:421:xlator_set_type] xlator: attempt to load file /usr/local/glusterfs-2.0.0rc1-DEBUG/lib/glusterfs/2.0.0rc1/xlator/performance/write-behind.so
2009-02-02 15:39:33 D [xlator.c:461:xlator_set_type] xlator: dlsym(notify) on /usr/local/glusterfs-2.0.0rc1-DEBUG/lib/glusterfs/2.0.0rc1/xlator/performance/write-behind.so: undefined symbol: notify -- neglecting
2009-02-02 15:39:33 D [spec.y:213:section_type] parser: Type:writebehind:performance/write-behind
2009-02-02 15:39:33 D [spec.y:288:section_option] parser: Option:writebehind:aggregate-size:131072
2009-02-02 15:39:33 D [spec.y:357:section_sub] parser: child:writebehind->bricktest
2009-02-02 15:39:33 D [spec.y:372:section_end] parser: end:writebehind
2009-02-02 15:39:33 D [xlator.c:421:xlator_set_type] xlator: attempt to load file /usr/local/glusterfs-2.0.0rc1-DEBUG/lib/glusterfs/2.0.0rc1/xlator/mount/fuse.so
2009-02-02 15:39:33 D [glusterfsd.c:1084:main] glusterfs: running in pid 5943
2009-02-02 15:39:33 W [xlator.c:382:validate_xlator_volume_options] writebehind: option 'aggregate-size' is deprecated, preferred is 'block-size', continuing with correction
2009-02-02 15:39:33 D [client-protocol.c:5986:init] bricktest: defaulting transport-timeout to 42
2009-02-02 15:39:33 D [transport.c:141:transport_load] transport: attempt to load file /usr/local/glusterfs-2.0.0rc1-DEBUG/lib/glusterfs/2.0.0rc1/transport/socket.so
2009-02-02 15:39:33 D [xlator.c:152:_volume_option_value_validate] bricktest: no range check required for 'option remote-port 6997'
2009-02-02 15:39:33 D [xlator.c:551:xlator_init_rec] bricktest: Initialization done
2009-02-02 15:39:33 D [write-behind.c:1315:init] writebehind: using aggregate-size = 0
2009-02-02 15:39:33 D [xlator.c:551:xlator_init_rec] writebehind: Initialization done
2009-02-02 15:39:33 D [client-protocol.c:6296:notify] bricktest: got GF_EVENT_PARENT_UP, attempting connect on transport
2009-02-02 15:39:33 D [client-protocol.c:6296:notify] bricktest: got GF_EVENT_PARENT_UP, attempting connect on transport
2009-02-02 15:39:33 D [inode.c:990:inode_table_new] fuse: creating new inode table with lru_limit=0
2009-02-02 15:39:33 D [inode.c:455:__inode_create] fuse/inode: create inode(0)
2009-02-02 15:39:34 D [client-protocol.c:5684:client_protocol_reconnect] bricktest: attempting reconnect
2009-02-02 15:39:34 D [common-utils.c:92:gf_resolve_ip6] resolver: DNS cache not present, freshly probing hostname: 192.168.201.103
2009-02-02 15:39:34 D [common-utils.c:129:gf_resolve_ip6] resolver: returning ip-192.168.201.103 (port-6997) for hostname: 192.168.201.103 and port: 6997
2009-02-02 15:39:34 D [client-protocol.c:6328:notify] bricktest: got GF_EVENT_CHILD_UP
2009-02-02 15:39:34 D [socket.c:924:socket_connect] bricktest: connect () called on transport already connected
2009-02-02 15:39:34 D [client-protocol.c:5625:client_setvolume_cbk] bricktest: SETVOLUME on remote-host succeeded
2009-02-02 15:39:44 D [client-protocol.c:5693:client_protocol_reconnect] bricktest: breaking reconnect chain
2009-02-02 15:39:48 W [fuse-bridge.c:2526:fuse_thread_proc] fuse: unmounting /mnt/glusterfs
2009-02-02 15:39:48 W [glusterfsd.c:775:cleanup_and_exit] glusterfs: shutting down

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by amarts (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-02-02 amarts StatusNone Fixed
        Assigned toNone amarts
        Originator Name
        Originator Email
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code