thr3ads.net - Gluster users - [Gluster-users] Lock error with mysql over gluster [Mar 2010]

If this information is useful, please help other people find it:
Share via:

Martín Eduardo Bradaschia

2010-Mar-12 19:06 UTC

[Gluster-users] Lock error with mysql over gluster

Hi

I have a production environment like this:  Debian Etch (4.0), ext3, 
glusterfs-2.0.9 (built from LATEST src), fuse-2.7.4glfs11, mysql 5.1.

When I restart mysql it fiils the syslog with messages like this:

InnoDB: Unable to lock ./ibdata1, error: 11

I tried next translator variations:

type features/posix-locks
type features/locks
option mandatory-locks on

even with mysql restart gluster

... the same problem once and again

Can anybody help me ? Thanx in advance !

Here my current configuration:

----------- Sever

volume posix1
 type storage/posix
 option directory /media/vol1
 option background-unlink yes       end-volume

volume locks1
 type features/posix-locks
 option mandatory-locks on
 subvolumes posix1
end-volume

volume brick1
 type performance/io-threads
 option thread-count 8            # Default es 16
 subvolumes locks1
end-volume

volume posix2
 type storage/posix
 option directory /media/vol2
 option background-unlink yes       end-volume

volume locks2
 type features/posix-locks
 option mandatory-locks on
 subvolumes posix2
end-volume

volume brick2
 type performance/io-threads
 option thread-count 8            # Default es 16
 subvolumes locks2
end-volume

volume server1
 type protocol/server
 option transport-type tcp
 option transport.socket.bind-address 127.0.0.1
 option transport.socket.listen-port 7001        # Default is 6996
 option auth.addr.brick1.allow *           subvolumes brick1
end-volume


volume server2
 type protocol/server
 option transport-type tcp
 option transport.socket.bind-address 127.0.0.1
 option transport.socket.listen-port 7002        # Default is 6996
 option auth.addr.brick2.allow *           subvolumes brick2
end-volume

----------- Client


volume client1
 type protocol/client
 option transport-type tcp
 option remote-host 127.0.0.1        # El servidor es local
 option remote-port 7001        # Defalut is 6995
 option remote-subvolume brick1    # name of the remote volume
end-volume


volume client2
 type protocol/client
 option transport-type tcp
 option remote-host 127.0.0.1       option remote-port 7002        # 
Defalut is 6995
 option remote-subvolume brick2    # name of the remote volume
end-volume


volume completo
 type cluster/distribute
 option min-free-disk 20%
 subvolumes client1 client2
end-volume


volume writebehind
 type performance/write-behind
 option cache-size 4MB
 subvolumes completo
end-volume

volume iocache
 type performance/io-cache
 option cache-size 64MB
 subvolumes writebehind
end-volume

-- 
Martin Eduardo Bradaschia
Centro de Datos y Comunicaciones
Universidad Nacional del Centro
Paraje Arroyo Seco S/N
02293-43-9500 int 603

Dave Hall

2010-Mar-13 23:31 UTC

head link

[Gluster-users] Lock error with mysql over gluster

Hi Martin,

On Fri, 2010-03-12 at 16:06 -0300, Mart??n Eduardo Bradaschia
wrote:> Hi
> 
> I have a production environment like this:  Debian Etch (4.0), ext3, 
> glusterfs-2.0.9 (built from LATEST src), fuse-2.7.4glfs11, mysql 5.1.
> 
> When I restart mysql it fiils the syslog with messages like this:
> 
> InnoDB: Unable to lock ./ibdata1, error: 11
A bit off topic, but you should consider running mysql with the
innodb_file_per_table option enabled.  MySQL will use disk more
efficiently this way.  You will need to dump all of your databases and
reimport them.

Sorry I don't know how to help with the locking issue.

Cheers

Dave

Martín Eduardo Bradaschia

2010-Mar-24 14:19 UTC

head link

[Gluster-users] Lock error with mysql over gluster

Hi

I have a production environment like this:  Debian Etch (4.0), ext3, 
glusterfs-2.0.9 (built from LATEST src), fuse-2.7.4glfs11, mysql 5.1.

When I restart mysql it fiils the syslog with messages like this:

InnoDB: Unable to lock ./ibdata1, error: 11

I tried next translator variations:

type features/posix-locks
type features/locks
option mandatory-locks on

even with mysql restart gluster

... the same problem once and again

Can anybody help me ? Thanx in advance !

Here my current configuration:

----------- Sever

volume posix1
type storage/posix
option directory /media/vol1
option background-unlink yes       end-volume

volume locks1
type features/posix-locks
option mandatory-locks on
subvolumes posix1
end-volume

volume brick1
type performance/io-threads
option thread-count 8            # Default es 16
subvolumes locks1
end-volume

volume posix2
type storage/posix
option directory /media/vol2
option background-unlink yes       end-volume

volume locks2
type features/posix-locks
option mandatory-locks on
subvolumes posix2
end-volume

volume brick2
type performance/io-threads
option thread-count 8            # Default es 16
subvolumes locks2
end-volume

volume server1
type protocol/server
option transport-type tcp
option transport.socket.bind-address 127.0.0.1
option transport.socket.listen-port 7001        # Default is 6996
option auth.addr.brick1.allow *           subvolumes brick1
end-volume


volume server2
type protocol/server
option transport-type tcp
option transport.socket.bind-address 127.0.0.1
option transport.socket.listen-port 7002        # Default is 6996
option auth.addr.brick2.allow *           subvolumes brick2
end-volume

----------- Client


volume client1
type protocol/client
option transport-type tcp
option remote-host 127.0.0.1        # El servidor es local
option remote-port 7001        # Defalut is 6995
option remote-subvolume brick1    # name of the remote volume
end-volume


volume client2
type protocol/client
option transport-type tcp
option remote-host 127.0.0.1       option remote-port 7002        # 
Defalut is 6995
option remote-subvolume brick2    # name of the remote volume
end-volume


volume completo
type cluster/distribute
option min-free-disk 20%
subvolumes client1 client2
end-volume


volume writebehind
type performance/write-behind
option cache-size 4MB
subvolumes completo
end-volume

volume iocache
type performance/io-cache
option cache-size 64MB
subvolumes writebehind
end-volume

-- 
Martin Eduardo Bradaschia
Intercomgi Argentina

Christopher Hawkins

2010-Mar-24 14:40 UTC

head link

[Gluster-users] Lock error with mysql over gluster

Martin,
I do something similar with version 3.0.2 and do not have locking problems. My
vol file syntax is slightly different:

volume locks1
type features/locks

whereas you have > volume locks1
> type features/posix-locks
Perhaps try 3.x version? Looks like there have been some changes made to
locking. Not sure how 'posix-locks' became 'locks' but clearly
something is updated. I am not using DHT but that probably should not matter for
locks.

Chris

----- "Mart??n Eduardo Bradaschia" <martin.bradaschia at
intercomgi.net> wrote:
> Hi
> 
> I have a production environment like this:  Debian Etch (4.0), ext3, 
> glusterfs-2.0.9 (built from LATEST src), fuse-2.7.4glfs11, mysql 5.1.
> 
> When I restart mysql it fiils the syslog with messages like this:
> 
> InnoDB: Unable to lock ./ibdata1, error: 11
> 
> I tried next translator variations:
> 
> type features/posix-locks
> type features/locks
> option mandatory-locks on
> 
> even with mysql restart gluster
> 
> ... the same problem once and again
> 
> Can anybody help me ? Thanx in advance !
> 
> Here my current configuration:
> 
> ----------- Sever
> 
> volume posix1
> type storage/posix
> option directory /media/vol1
> option background-unlink yes       end-volume
> 
> volume locks1
> type features/posix-locks
> option mandatory-locks on
> subvolumes posix1
> end-volume
> 
> volume brick1
> type performance/io-threads
> option thread-count 8            # Default es 16
> subvolumes locks1
> end-volume
> 
> volume posix2
> type storage/posix
> option directory /media/vol2
> option background-unlink yes       end-volume
> 
> volume locks2
> type features/posix-locks
> option mandatory-locks on
> subvolumes posix2
> end-volume
> 
> volume brick2
> type performance/io-threads
> option thread-count 8            # Default es 16
> subvolumes locks2
> end-volume
> 
> volume server1
> type protocol/server
> option transport-type tcp
> option transport.socket.bind-address 127.0.0.1
> option transport.socket.listen-port 7001        # Default is 6996
> option auth.addr.brick1.allow *           subvolumes brick1
> end-volume
> 
> 
> volume server2
> type protocol/server
> option transport-type tcp
> option transport.socket.bind-address 127.0.0.1
> option transport.socket.listen-port 7002        # Default is 6996
> option auth.addr.brick2.allow *           subvolumes brick2
> end-volume
> 
> ----------- Client
> 
> 
> volume client1
> type protocol/client
> option transport-type tcp
> option remote-host 127.0.0.1        # El servidor es local
> option remote-port 7001        # Defalut is 6995
> option remote-subvolume brick1    # name of the remote volume
> end-volume
> 
> 
> volume client2
> type protocol/client
> option transport-type tcp
> option remote-host 127.0.0.1       option remote-port 7002        # 
> Defalut is 6995
> option remote-subvolume brick2    # name of the remote volume
> end-volume
> 
> 
> volume completo
> type cluster/distribute
> option min-free-disk 20%
> subvolumes client1 client2
> end-volume
> 
> 
> volume writebehind
> type performance/write-behind
> option cache-size 4MB
> subvolumes completo
> end-volume
> 
> volume iocache
> type performance/io-cache
> option cache-size 64MB
> subvolumes writebehind
> end-volume
> 
> -- 
> Martin Eduardo Bradaschia
> Intercomgi Argentina 
>  
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

Gluster users - Mar 2010 - Lock error with mysql over gluster

[Gluster-users] Lock error with mysql over gluster

[Gluster-users] Lock error with mysql over gluster

[Gluster-users] Lock error with mysql over gluster

[Gluster-users] Lock error with mysql over gluster