On Mon, Mar 23, 2009 at 10:00 AM, Erik Drolshammer <erik-...@fjas.no> wrote: > Hi! > We try to set up two brokers according to [1] to get some redundancy in our > solution. The shared filesystem is based on GFS, but it doesn't seem to work > that well. The master node use a lot of cpu, but the throughput is horrible. > > > Can anyone point me to some resources describing the setup? > Any debug tips?
The only setup that's needed for the shared filesystem master/slave is noting the same data directory location for each ActiveMQ instance. That's it. ActiveMQ takes care of the rest based on the filesystem locking. According to the Wikipedia entry for the Google File System (GFS), it is mainly used for data that is 'extremely rarely overwritten, or shrunk; files are usually appended to or read.' http://en.wikipedia.org/wiki/Google_File_System Given this essential fact, I'd say that GFS is probably not a good candidate for use by ActiveMQ since the ActiveMQ data is in almost a constant churn of being written and removed as messages flow through the broker. Could this be the cause of the high CPU usage and poor throughput? Bruce -- perl -e 'print unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.apache.org/ Apache Camel - http://camel.apache.org/ Apache ServiceMix - http://servicemix.apache.org/ Blog: http://bruceblog.org/
