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/26 06:59:12 UTC

[jira] [Updated] (AMQ-5430) LevelDB on NFS creats .nfs files

     [ https://issues.apache.org/jira/browse/AMQ-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anuj Khandelwal updated AMQ-5430:
---------------------------------
    Priority: Critical  (was: Major)

> LevelDB on NFS creats .nfs files
> --------------------------------
>
>                 Key: AMQ-5430
>                 URL: https://issues.apache.org/jira/browse/AMQ-5430
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-leveldb-store, Broker
>    Affects Versions: 5.10.0
>            Reporter: Anuj Khandelwal
>            Priority: Critical
>
> We are currently testing levelDB on NFS. 
> leveldb creates .log files in leveldb directory to store actual message/data and this files rotates after 100MB size. These .log files gets deleted when all the messages are consumed from a particular file. 
> Issue: After all the messages are consumed I can see that files are getting deleted but internally they are creating .nfs files of same size. 
> we have to restart the process to delete those .nfs files. 
> From my understanding: It seems that the LevelDB store keeps the old logfiles open after they were deleted.
> Below is the snapshot of 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
> Thanks,
> Anuj



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)