Re: [xmlblaster-devel] Slave Database Persistence

["Matthew Sargent" <matt.sargent at cox.net>]

Marcel,

More information on this, we were publishing with a the domain of the master
specified, but when we erased the keys we were not specifying the domain. We
have changed the erase to specify the domain but it does not seem to impact
the cleanup on the slave at all.

Matt (Jonathan's co-worker)

----- Original Message ----- 
From: "Marcel Ruff" <mr at marcelruff.info>
To: <xmlblaster-devel at server.xmlBlaster.org>
Sent: Saturday, February 11, 2006 2:15 PM
Subject: Re: [xmlblaster-devel] Slave Database Persistence


Jonathan Clark wrote:
>
> I am running a master/slave configuration where the messages are
> published to the master. Several clients are connected to the slave and
>
> subscribe to the domain of the master. The clients get the messages
> with out any problem and delete the messages when the keys are
>
> erased. The slave properties file is configured as follows:
>
> StoragePlugin[JDBC][1.0]=${JdbcStorage[postgres]}
>
> StoragePlugin[RAM][1.0]=org.xmlBlaster.engine.msgstore.ram.MapPlugin
>
>
StoragePlugin[CACHE][1.0]=org.xmlBlaster.engine.msgstore.cache.PersistenceCa
chePlugin,persistentQueue=JDBC,transientQueue=RAM
>
> # Choose the plugins
>
> persistence/topicStore/defaultPlugin=CACHE,1.0
>
> persistence/msgUnitStore/defaultPlugin=CACHE,1.0
>
> The problem that I am having is that the number of rows in the
> xb_entries table continues to grow on the slave. It stays at ~800 rows on
>
> the master, but has grown to over 10,000 on the slave. Any idea why
> the entries wouldn’t be deleted from the slave database?
>
I will check this,

thanks for reporting
Marcel
>
> Jonathan Clark
>
> Open Roads Consulting, Inc.
>
> 757-546-3401
>