glad to hear you found your solution! I have been combing over this post and others on this discussion board many times and have tried so many tweaks to configuration, order of steps, etc, all with absolutely no success in getting the Source cluster tlogs to delete. So incredibly frustrating. If anyone has other pearls of wisdom I'd love some advice. Quick hits on what I've tried:
- solrconfig exactly like Sean's (target and source respectively) expect no autoSoftCommit - I am also calling cdcr?action=DISABLEBUFFER (on source as well as on target) explicitly before starting since the config setting of defaultState=disabled doesn't seem to work - when I create the collection on source first, I get the warning "The log reader for target collection {collection name} is not initialised". When I reverse the order (create the collection on target first), no such warning - tlogs replicate as expected, hard commits on both target and source cause tlogs to rollover, etc - all of that works as expected - action=QUEUES on source reflects the queueSize accurately. Also *always* shows updateLogSynchronizer state as "stopped" - action=LASTPROCESSEDVERSION on both source and target always seems correct (I don't see the -1 that Sean mentioned). - I'm creating new collections every time and running full data imports that take 5-10 minutes. Again, all data replication, log rollover, and autocommit activity seems to work as expected, and logs on target are deleted. It's just those pesky source tlogs I can't get to delete. -- View this message in context: http://lucene.472066.n3.nabble.com/CDCR-how-to-deal-with-the-transaction-log-files-tp4345062p4345715.html Sent from the Solr - User mailing list archive at Nabble.com.