activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Stanley <dstanl...@gmail.com>
Subject Re: NFS locking issue for Master/Slave
Date Mon, 09 Mar 2009 21:25:57 GMT
Hi Jason,
Have you tried using nfsv4. It may be that you can use that (and tweak the
lease period on the netapp if necessary) to give you the lock expiration
behaviour your looking for.

Hope this helps
/Dave

On Mon, Mar 9, 2009 at 2:16 PM, JasonCzerak <czerakj@jostens.com> wrote:

>
>
>
> JasonCzerak wrote:
> >
> > I'm using the latest ActiveMQ 5.2.0 Release. I have a clustered
> > configuration for the NetApp filters. So my file system store is very HA.
> >
> > I'm using the idea documented here:
> > http://activemq.apache.org/shared-file-system-master-slave.html
> >
> > This process works so long as the master sever never crashes hard.
> (Kernel
> > Panic, or power cable unplug). If I pull the plug, or issue a "echo "c" >
> > /proc/sysrq-trigger" the file system lock is never released "until" the
> > master server comes on line and mounts it's network files sytem, or I
> kill
> > the lock via NetApp's sm_mon command.
> >
> > Any ideas here to correct this?  I'm going to convert the file system to
> > mixed (enable cifs) and see if that helps a little using samba client.
> >
> >
> >
> >
> >
>
>
> bump... anyone? someone had to have tested this configuration by now?!?!
>
>
> --
> View this message in context:
> http://www.nabble.com/NFS-locking-issue-for-Master-Slave-tp22311102p22413944.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message