Moving db*.log files as /data partition 100% full

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Moving db*.log files as /data partition 100% full

rajbrinder
Hi

I am bit novice in Active MQ domain and would like some expert advice.

Problem is

APP Servers ----> Queuing Servers ------> Database

Our APP servers (producers) write data into Active MQ on Queuing servers, There is process called Infostore which consumes the message from MQ and puts the message into the database.

Because of the slow write speed between Queuing server and Infostore, there is a huge backlog created on Queuing server (this server has Active MQ ). And this has caused the /data partition filled up to 100%.

As the partition is filled up, MQ process has stopped and as a result Infostore has stopped consuming data hence all system has come to halt.

There is directory called kahadb which has around 4800 , db-******.log files and db.redo & db. datat files.

Can I

1. move the latest *.log files to some other partition, so I can free few GB space on /data partition

2. start the MQ ,

3. ensure that the VO servers arent sending more data to Active MQ,

4. infostore process would start consuming data

5. stop MQ

6. put the *.log files back in time so that the sequence doesnt break when MQ picks the respective *.log file


Could you please advise whether the above is feasible , I have already started the backup of kahadb directory. Also note that I cannot afford to loose any data.

Regards

start MQ
Reply | Threaded
Open this post in threaded view
|

Re: Moving db*.log files as /data partition 100% full

Matt Pavlovich-2
Yes, you can move the location of those KahaDB files while ActiveMQ is not running.  

http://activemq.apache.org/kahadb.html


<broker brokerName="broker" ... >
   <persistenceAdapter>
     <kahaDB directory=“/some/other/folder/activemq-data" journalMaxFileLength="32mb"/>
   </persistenceAdapter>
   ...
</broker>

Also, if you have one really big queue that has the slow consumer, and other queues that just have small messages, you can run into a situation where the kahaDB log files may only have a few messages in them to work around this, use the muli-file persistence adapter.

<broker brokerName="broker" ... >
 <persistenceAdapter>
  <mKahaDB directory="${activemq.base}/data/kahadb">
    <filteredPersistenceAdapters>
      <!-- kahaDB per destinations -->
      <filteredKahaDB perDestination="true" >
        <persistenceAdapter>
          <kahaDB journalMaxFileLength="32mb" />
        </persistenceAdapter>
      </filteredKahaDB>
    </filteredPersistenceAdapters>
  </mKahaDB>
 </persistenceAdapter>
...
</broker>



On Aug 8, 2014, at 12:59 PM, rajbrinder <[hidden email]> wrote:

> Hi
>
> I am bit novice in Active MQ domain and would like some expert advice.
>
> Problem is
>
> APP Servers ----> Queuing Servers ------> Database
>
> Our APP servers (producers) write data into Active MQ on Queuing servers,
> There is process called Infostore which consumes the message from MQ and
> puts the message into the database.
>
> Because of the slow write speed between Queuing server and Infostore, there
> is a huge backlog created on Queuing server (this server has Active MQ ).
> And this has caused the /data partition filled up to 100%.
>
> As the partition is filled up, MQ process has stopped and as a result
> Infostore has stopped consuming data hence all system has come to halt.
>
> There is directory called kahadb which has around 4800 , db-******.log files
> and db.redo & db. datat files.
>
> Can I
>
> 1. move the latest *.log files to some other partition, so I can free few GB
> space on /data partition
>
> 2. start the MQ ,
>
> 3. ensure that the VO servers arent sending more data to Active MQ,
>
> 4. infostore process would start consuming data
>
> 5. stop MQ
>
> 6. put the *.log files back in time so that the sequence doesnt break when
> MQ picks the respective *.log file
>
>
> Could you please advise whether the above is feasible , I have already
> started the backup of kahadb directory. Also note that I cannot afford to
> loose any data.
>
> Regards
>
> start MQ
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Moving-db-log-files-as-data-partition-100-full-tp4684330.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.