Gurpreet created AMQ-7200:
-----------------------------

             Summary: apache-activemq-5.14.3/ level db log files issue
                 Key: AMQ-7200
                 URL: https://issues.apache.org/jira/browse/AMQ-7200
             Project: ActiveMQ
          Issue Type: Bug
          Components: activemq-leveldb-store
    Affects Versions: 5.14.3
            Reporter: Gurpreet


Hi

Need help on one issue. We have apache-activemq-5.14.3/ , level db folder has 
log files which are created when existing one gets to 101 MB. This has created 
many such(101 MB) log files in the level db folder and filesystem relating to 
this level db folder is increasing in size.We have had situations when leveldb 
got to >90% and filesystem getting full and activemq stopped processing 
messages.

Someone check and help in resolving this issue please .

 

These are the log files i can see in the system right now inside leveldb 
folder. ->

[root@mdcgintchaprd01 leveldb]# ls -l
total 360636
-rw-r--r-- 1 activemq activemq 104858544 Apr 23 00:43 0000000000000000.log  >> 
this is old
-rw-r--r-- 1 activemq activemq 104858388 May  1 00:33 00000000064003b0.log> 
this is old
-rw-r--r-- 1 activemq activemq 104857839 May  9 06:48 000000000c8006c4.log>this 
is old
drwxr-xr-x 2 activemq activemq      4096 May  9 06:48 0000000012c007b3.index
-rw-r--r-- 1 activemq activemq 104857600 May 13 10:18 
0000000012c007b3.log>latest one
drwxr-xr-x 2 activemq activemq      4096 May  5 12:21 dirty.index
-rw-r--r-- 1 activemq activemq         8 Apr 15 05:20 lock
drwxr-xr-x 2 activemq activemq      4096 Apr 15 05:20 plist.index
-rw-r--r-- 1 activemq activemq        24 Apr 15 05:20 store-version.txt

 

 

-rw-r--r-- 1 activemq activemq 104857600 May 13 10:18 0000000012c007b3.log is 
the latest log file right now at 51 MB .The other log files are 101 MB in size.

Can we remove those old log files safely without causing any system /broker 
issues ?

Pls help. These old log files should have gotton automatically removed without 
manual intervention.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to