activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4684) LevelDB on NFS created .nfs files
Date Thu, 15 Aug 2013 21:26:05 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741501#comment-13741501
] 

Timothy Bish commented on AMQ-4684:
-----------------------------------

First thing I would do is try out the most recent 5.9-SNAPSHOT so you have all the LevelDB
fixes that have gone in since the 5.8 release, which is many.  
                
> LevelDB on NFS created .nfs files
> ---------------------------------
>
>                 Key: AMQ-4684
>                 URL: https://issues.apache.org/jira/browse/AMQ-4684
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-leveldb-store
>    Affects Versions: 5.8.0
>         Environment: three linuc machines:
> - one NFS server
> - two activeMQ machines, both a mount on the NFS server for LevelDB
>            Reporter: Christiaan Willemsen
>            Priority: Minor
>
> We are currently testing levelDB on NFS for failover. We did this test with only one
ActiveMQ running.
> We filled one queue with 10.000 messages via the admin console, and then purged the queue.
> After this, the LevelDB directory was filled with .nfsxxxxxx files. These seem to be
old version of the LevelDB log file. They are removed when you stop the ActiceMQ process.
You also appear to be able to remove the files manually.
> From what we can deduce, these files mean that they were still open for io, while they
were removed from the filesystem. A local filesystem will cope with this in the background,
on a NFS share however that can't be done, so these .nfs files are created.
> So it seems that the LevelDB store keeps the old logfiles open after they were deleted.

--
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

Mime
View raw message