[
https://issues.apache.org/jira/browse/AMQ-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-4705:
----------------------------
Description:
issue on nsfv4 with a master slave configuration, where both the slave and the
master could obtain a lock.
The following events occurred:
* master locks the file - does no more i/o to it – it's passive wrt the lock
* slave asks every 10 seconds if it can get the lock nfs come back and say no,
someone has it
* nfs dies not nicely
** nfsv4 is stateful - no callback for locks.
** It has a grace period of 30 seconds to let all clients that had locks
reclaim them as locked
* master does not realize it needs to reclaim the lock and continues under the
assumption it has the lock.
* After 30 sec grace period, slave comes in and asks for the lock and it
receives it.
was:
issue on nsfv4 with a master slave configuration, where both the slave and the
master could obtain a lock.
The following events occurred:
* master locks the file - does no more i/o to it – it's passive wrt the lock
* slave asks every 10 seconds if it can get the lock nfs come back and say no,
someone has it
* nfs dies not nicely
** nfsv4 is stateful - no callback for locks. It has a grace period 30 seconds
to let all clients had locks reclaims locked
* master does not realize it needs to reclaim the lock and continues under the
assumption it has the lock.
* After 30 sec grace period, slave comes in and asks for the lock and it
receives it.
> Add keep alive support to shared file locker
> --------------------------------------------
>
> Key: AMQ-4705
> URL: https://issues.apache.org/jira/browse/AMQ-4705
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: kahadb, netapp, nfsv4, shared-file-lock
> Fix For: 5.9.0
>
>
> issue on nsfv4 with a master slave configuration, where both the slave and
> the master could obtain a lock.
> The following events occurred:
> * master locks the file - does no more i/o to it – it's passive wrt the lock
> * slave asks every 10 seconds if it can get the lock nfs come back and say
> no, someone has it
> * nfs dies not nicely
> ** nfsv4 is stateful - no callback for locks.
> ** It has a grace period of 30 seconds to let all clients that had locks
> reclaim them as locked
> * master does not realize it needs to reclaim the lock and continues under
> the assumption it has the lock.
> * After 30 sec grace period, slave comes in and asks for the lock and it
> receives it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
