On 1/6/2017 10:09 AM, Webster Homer wrote: > This happened while testing and was not in a production system. So we > just deleted both collections and recreated them after fixing the root > cause. If this had been a production system that would not have been > acceptable. What is the best way to recover from a problem like this? > Stop cdcr and delete the tlog files?
What was the root cause? Need to know that before anyone can tell you whether or not you've run into a bug. If it was the problem you've separately described where CDCR logging filled up your disk ... handling that gracefully in a program is very difficult. It's possible, but there's very little incentive for anyone to attempt it. Lucene and Solr have a general requirement of plenty of free disk space (enough for the index to triple in size temporarily) just for normal operation, so coding for disk space exhaustion isn't likely to happen. Server monitoring should send an alarm when disk space gets low so you can fix it before it causes real problems. Thanks, Shawn
