You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Anuj Khandelwal (JIRA)" <ji...@apache.org> on 2014/11/07 09:44:35 UTC
[jira] [Commented] (AMQ-4684) LevelDB on NFS created .nfs files
[ https://issues.apache.org/jira/browse/AMQ-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201800#comment-14201800 ]
Anuj Khandelwal commented on AMQ-4684:
--------------------------------------
Hi,
I have also seen similar issue in my case using ActiveMQ-5.10. When I go to my leveldb directory, I can see those .nfs**** files. I goggled a little bit and find that : If you remove a file that a currently running process still has open, the file isn't really removed. Once the process closes the file, the OS then removes the file handle and frees up the disk blocks.
Below is the snapshot of those files:
--------------------------------------------------------------------------------------
amqtest@kepler19.nyc:/u/amqtest/dev/leveldb> ls -a
.nfs000000000082e7be0000fafe
.nfs0000000000960d1e0000eb46
.nfs00000000010332430000ea15
.nfs0000000000614cf10000eaef
.nfs0000000000960d1a0000ee3e
.nfs00000000010332420000e52d
dirty.index
store-version.txt
.nfs000000000082e7c3000100c5
.nfs0000000000960d1f0000f27f
00000000724ff92c.index
lock
00000000724ff92c.log
plist.index
--------------------------------------------------------------------------------------
amqtest@kepler19.nyc:/u/amqtest/dev/leveldb> du -sh .nfs*
107M .nfs0000000000614cf10000eaef
101M .nfs000000000082e7be0000fafe
101M .nfs000000000082e7c3000100c5
108M .nfs0000000000960d1a0000ee3e
106M .nfs0000000000960d1e0000eb46
104M .nfs0000000000960d1f0000f27f
101M .nfs00000000010332420000e52d
101M .nfs00000000010332430000ea15
---------------------------------------------------------------------------
I think ActiveMQ is directly removing these files rather than closing and removing them,. Please take a look at this.
Thanks,
Anuj
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)