Note that those are Info notices (" I "), not Errors (" E ").
3.2.2 has known critical bugs. You should upgrade (at least within the
3.2 branch) asap.
On 02/12/2013 10:19 AM, samuel wrote:
Hi folks,
We're using in an old environment gluster 3.2.2 and we've just started
seeing the following error in /usr/local/var/log/glusterfs/bricks/gfs-log:
[2013-02-12 19:15:05.214430] I
[server3_1-fops.c:1240:server_writev_cbk] 0-cloud-server: 2400444243:
WRITEV 7 (37067) ==> -1 (Cannot allocate memory)
[2013-02-12 19:15:19.463087] I
[server3_1-fops.c:1240:server_writev_cbk] 0-cloud-server: 2249406582:
WRITEV 15 (52493) ==> -1 (Cannot allocate memory)
in a distributed replicated 2-node environment.
Both nodes have enough disk space (1.3T) but looks like used memory is
quite high:
node1:
total used free shared buffers cached
Mem: 4047680 4012700 34980 0 276 3728652
-/+ buffers/cache: 283772 3763908
Swap: 3906244 19916 3886328
node2:
total used free shared buffers cached
Mem: 4047680 4012488 35192 0 1088 3713512
-/+ buffers/cache: 297888 3749792
Swap: 3905532 25244 3880288
could it be a memory issue?
Best regards,
Samuel.
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
