[Gluster-devel] issue with server: frame size (131278) > max (83896)

[Raghavendra G]

Hi Chris,
The issue is that maximum allowed blocksize is less than the size of the
transmitted block. Maximum allowed block size can be changed using the
option "limits.transaction-size" on both protocol/client and
protocol/server. Make sure that it can accommodate the size of the largest
block that can be transmitted.

In your case, the issue can be fixed with updating the configuration on the
server having the issue with the following option in protocol/server

option limits.transaction-size 128KB

regards,

On Thu, Oct 23, 2008 at 7:25 AM, chris at velocityservers.com.au <
chris at velocityservers.com.au> wrote:

> HI Guys,
>
> When i try to transfer a file over the glusterfs storage system, i get the
> following log from one of my servers -, the other 2 servers copy the file
> without an issue:
>
> 2008-10-23 05:14:36 E [protocol.c:342:gf_block_unserialize_transport]
> server: frame size (131278) > max (83896)
> 2008-10-23 05:14:36 D [tcp.c:87:tcp_disconnect] server: connection
> disconnected
> 2008-10-23 05:14:36 D [server-protocol.c:6262:server_protocol_cleanup]
> server: cleaned up transport state for client 192.168.1.105:1021
> 2008-10-23 05:14:36 D [tcp-server.c:257:gf_transport_fini] server:
> destroying transport object for 192.168.1.105:1021 (fd=6)
> 2008-10-23 05:14:36 D [tcp-server.c:145:tcp_server_notify] server:
> Registering socket (6) for new transport object of 192.168.1.105
> 2008-10-23 05:14:36 D [ip.c:120:gf_auth] brick: allowed = "*", received ip
> addr = "192.168.1.105"
>
> It seems that the file transfers over with a file size of 0.
>
> Glusterfs-serve.vol :
>
> # file: /etc/glusterfs/glusterfs-server.vol
>
> volume brick
>  type storage/posix
>  option directory /mnt/HD_a2/export
> end-volume
>
> volume server
>  type protocol/server
>  option transport-type tcp/server
>  option auth.ip.brick.allow *
>  subvolumes brick
> end-volume
>
> Glusterfs-client:
>
> volume remote1
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host 192.168.1.104
>  option remote-subvolume brick
> end-volume
>
> volume remote2
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host 192.168.1.106
>  option remote-subvolume brick
> end-volume
>
> volume remote3
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host 192.168.1.10
>  option remote-subvolume brick
> end-volume
>
> volume mirror0
>  type cluster/afr
>  subvolumes remote1 remote2 remote3
> end-volume
>
> Server with issue is 192.168.1.10.
>
> Could anyone tell me what the issue is.
>
> Thanks
>
>
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>



-- 
Raghavendra G
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20081023/bf33c764/attachment-0003.html>